home tags events about login
one honk maybe more

benjojo posted 29 Dec 2023 13:38 +0000

The recording of my "Browsers biggest TLS Mistake" lightning talk at #37C3:

snowfox@tech.lgbt replied 29 Dec 2023 14:43 +0000
in reply to: https://mastodon.sandwich.net/users/coffee/statuses/111664079380705900

@coffee @benjojo The argument is probably something like “AIA makes SSL errors go away (and a better internet experience means more ad money for us), isn’t a big privacy issue, and is highly cacheable and” vs. “OCSP is bad for privacy and doesn’t help for most leaf revocations”. Or just https://www.imperialviolet.org/2014/04/29/revocationagain.html

ISTR Internet Explorer (Windows) filling in incomplete chains in the XP days, so it’s an old issue.

dana@tech.lgbt replied 29 Dec 2023 16:19 +0000
in reply to: https://benjojo.co.uk/u/benjojo/h/bTCbN86pJz6hXWNJ13

@benjojo it gets worse, unfortunately. Firefox's first technique to deal with this was to cache intermediates from successful connections in case they'd ever be useful when a different server sent an incomplete chain. That leads to the same kind of inconsistent results you mentioned in Chrome.

gross as it is, though, all that matters to the user is that the site loads, so... 🤷‍♀️

waldoj@mastodon.soci.. replied 29 Dec 2023 17:09 +0000
in reply to: https://mastodon.social/users/jamiemccarthy/statuses/111664789426331566

@jamiemccarthy @benjojo I worked a little bit on this ~5 years ago. GSA had recently started scanning all of .gov every day, looking for (among other things) TLS implementation failures, and providing a public record of the results. Regrettably, that was later made private and transferred to CISA along with control of the .gov TLD. IDK what CISA is doing now to communicate to .gov domain owners about that.

benjojo replied 31 Dec 2023 15:35 +0000
in reply to: https://is-a.cat/users/madargon/statuses/111675562871753123

@madargon Uhhh, if you are using your own CA then that can be quite a hard question to answer.

If you have your certs directly signed by the CA, then you have no issue, you can serve the direct certificate and call it a day.

IF you have a intermediate then you also need to provide the intermediate in the "full chain" that you provide to TLS servers, otherwise you are praying that Chrome (FireFox's logic wont save you here) will fix it for you (Not even sure it will), There are some extra caveats for AIA, but that quickly gets into a huge can of worms

madargon@is-a.cat replied 08 Jan 2024 08:43 +0000
in reply to: https://toot.mirbsd.org/users/mirabilos/statuses/01HK090X93TZZQGXXPMBB9DPK8

@mirabilos @benjojo Update: Because my main server cert expired two days ago, I had to update it anyway. So this time I put only server cert and intermediate in the file for nginx. And was scared as hell something would stop working when root cert wouldn't be there. But everything seems to work correctly, my friends using my Matrix server didn't notice anything crashing