Earlier quoted context omitted.
What sort of company do you work at? Why can't everyone just be told not to post code?
What sort of company do you work at where every employee obeys every directive?
HTTPS on Stack Overflow: The End of a Long Road
81–90 of 183 posts
Re: HTTPS on Stack Overflow: The End of a Long Road
#82Note to self: Use subdirectories, not subdomains in the future
TLS kills this kind of "cool" features which is kind of sad :( Unless you can afford wildcard certs. What's the argument behind LetsEncrypt not doing that? Extended Validation stuff?
Re: HTTPS on Stack Overflow: The End of a Long Road
#83> The password to our data center is pickles. I didn’t think anyone would read this far and it seemed like a good place to store it. You ought to have more confidence in your writing. BRB stealing all your servers.
Only if you get there first. And it may in fact be pickles2.
Re: HTTPS on Stack Overflow: The End of a Long Road
#84Earlier quoted context omitted.
TLS kills this kind of "cool" features which is kind of sad :( Unless you can afford wildcard certs. What's the argument behind LetsEncrypt not doing that? Extended Validation stuff?
How would they prove that you own every subdomain?
Re: HTTPS on Stack Overflow: The End of a Long Road
#85Re: HTTPS on Stack Overflow: The End of a Long Road
#86Earlier quoted context omitted.
TLS kills this kind of "cool" features which is kind of sad :( Unless you can afford wildcard certs. What's the argument behind LetsEncrypt not doing that? Extended Validation stuff?
Subdomains were killed by SEO a long time ago (afaik, Google does not transfer domain PageRank credit to subdomains), so this is not limited solely by the cost of wildcard certs.
Re: HTTPS on Stack Overflow: The End of a Long Road
#87Earlier quoted context omitted.
TLS kills this kind of "cool" features which is kind of sad :( Unless you can afford wildcard certs. What's the argument behind LetsEncrypt not doing that? Extended Validation stuff?
Subdomains were killed by SEO a long time ago (afaik, Google does not transfer domain PageRank credit to subdomains), so this is not limited solely by the cost of wildcard certs.
Re: HTTPS on Stack Overflow: The End of a Long Road
#88Re: HTTPS on Stack Overflow: The End of a Long Road
#89Earlier quoted context omitted.
Some people don't spy on their customers and don't have these kinds of information available for analyses They're admittedly few though and their moral high ground is debatable considering that there are self hosted FOSS alternatives around nowadays
Calling aggregate anonymous analytics "spying on your customers" is absurd nonsense.
Re: HTTPS on Stack Overflow: The End of a Long Road
#90Stack Exchange is no longer available from my workplace due to this change. We have a strict no-posting-code-fragments policy, and SE was viewed as too risky to allow without some restriction in place to make it read only. Before HTTPS, the IT department had worked out such a read-only restriction by blocking the SE login with firewall rules. But with HTTPS that kludge is no longer possible, so the site is blocked.
Same thing happened to me at a workplace once. They blocked StackOverflow, GitHub, Bitbucket, Sourceforge, CodePlex and Google Code. I told them all estimates go up by 2 years since we would need to reimplement everything. It ended up being unblocked a week later.
All roads lead to Stack Overflow these days for progrmaming problems.