Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

HTTPS on Stack Overflow: The End of a Long Road

nickcraver.com

Post reply on HN
Print view View original

161–170 of 183 posts

Re: HTTPS on Stack Overflow: The End of a Long Road

#161

Post by tvanantwerp »

mcherm wrote: post #160
techolic wrote: post #131

Earlier quoted context omitted.

Many banks have very strict IT policies on posting things on internet, and they have valid business reasons for that. Not saying you meant that, but it's not like they're some dark, silly workplaces that people should get away from asap.

> Many banks have very strict IT policies on posting things on internet Yes, they do. And I really love it. Because it means that MY bank eats their lunch, because the bank I work for actually UNDERSTANDS how to use technology, while still keeping (very!) strict controls.

Would be curious which bank you work for. Most do not seem to value technology--which is odd, since most "cash" only exists as data in a computer somewhere. I'd much prefer to patronize a bank that understands and takes seriously their tech.

Re: HTTPS on Stack Overflow: The End of a Long Road

#162

Post by _fizz_buzz_ »

linkregister wrote: post #124
astrodust wrote: post #90

Earlier quoted context omitted.

I don't know how you'd get anything done since there are answers on Stack Overflow that solve problems that otherwise would involve hours to days of fussing to come up with the same non-intuitive solution. All roads lead to Stack Overflow these days for progrmaming problems.

For every answered question, there are probably 20 unanswered ones. Almost none of my embedded programming questions got answered. Edit: my estimate is wildly off. It's basically the opposite of what I said.

I have had the same experience with embedded programming questions. I suppose they depend too much on the hardware. I do quite a bit of programming with the beaglebone blacks (or at least the same processor). And it seems the best resource is the mailing list.

Re: HTTPS on Stack Overflow: The End of a Long Road

#163

Post by noway421 »

brianpan wrote: post #150
z3t4 wrote: post #76

Earlier quoted context omitted.

browsers use domains for everything from connection limits to data storage. if you use folders everything will be shared.

Note to self: Use subdomains, not subdirectories in the future Wait...

The real LPT here is using different domain altogether..

But wait, in that case browser will make another DNS fetch and open up a separate http connection!

Re: HTTPS on Stack Overflow: The End of a Long Road

#164

Post by poizan42 »

eridius wrote: post #38
baby wrote: post #8

Earlier 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?

There's a long StackExchange answer about this: https://security.stackexchange.com/a/158164 But it boils down to there being no practical way for Let's Encrypt to automatically validate that a wildcard certificate is safe to issue.

It's a long answer that completely fails to address the possibility of validating ownership of the domain itself by e.g. adding a TXT record, which the ACME protocol already supports.

Re: HTTPS on Stack Overflow: The End of a Long Road

#165

Post by shaunrussell »

dzdt wrote: post #49

Stack 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.

If the architecture and code quality is good you should be able to open source your code and not have any security vulnerabilities.

You need to find a new job.

Re: HTTPS on Stack Overflow: The End of a Long Road

#166

Post by mikegerwitz »

y4mi wrote: post #45
mattmanser wrote: post #39

Earlier quoted context omitted.

I know it's hindsight and all that, but why didn't you check your website analytics first? Seems a fairly massive assumption that should have taken 10 seconds to check.

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

The important part is whether the data are anonymous.

You might be interested in the EFF's Best Practices for Online Service Providers:

https://www.eff.org/wp/osp

Re: HTTPS on Stack Overflow: The End of a Long Road

#167

Post by z3t4 »

jfroma wrote: post #111
mrunkel wrote: post #7

At $previous_job we once turned on HTTPS for our entire customer website and online store, only to have our customer support team be bombarded by phone calls claiming that our "website was down." After much teeth gnashing and research, we determined that a large segment of our user base was still using WinXP and the encryption protocols we offered weren't available to them. We didn't think this would be a problem bec…

The other problem with Windows XP and https is SNI. You cant serve more than one domain with different ssl certificates from the same IP address, you either use SANs or different IP addresses. This does not only affect IE on XP but every browser.

im suprised there are any non sni visitors to SO. i expect most of them are bots eg. old versions of wget etc.

Re: HTTPS on Stack Overflow: The End of a Long Road

#168

Post by ygra »

tallanvor wrote: post #155
Nick-Craver wrote: post #126

Earlier quoted context omitted.

12,095,709 questions have an answer, 7,506,004 of those have an accepted answer, and 1,813,270 aren't yet answered. I'd say your 1:20 ratio is just a little bit off :)

Just out of curiosity, do those 7.5+ million accepted answers include those closed as duplicates? Because by far my biggest complaint is finding the exact question I have was closed as a duplicate and links to a question that is useless at answering my question.

In that case you can vote to re-open and perhaps even post a bounty. Although bounties tend to invite lots of low-quality, low-effort answers just on the off chance that they might be the top-voted one once the bounty runs out.
Post reply on HN