3 ms·
I would have liked the world where AIA chasing happened in servers. Today several browsers which don't have Mozilla's list of intermediates instead (if they do
by tialaramex 5y ago
I would have liked the world where AIA chasing happened in servers.
Today several browsers which don't have Mozilla's list of intermediates instead (if they don't have a satisfactory chain offered to them) do AIA chasing, meaning that the browser consults the Authority Information Access fields in the X.509 certificate, finds a URL in there and fetches that URL hoping to get a certificate it trusts, often it iterates several times before giving up or reaching a dead end. AIA chasing in browsers is a (small) privacy risk and a (non-trivial) performance cost, plus it can just fail if you don't have as much Internet access, perhaps because you need to talk to a server, whose certificate you are trying to validate, before getting access; or of course it can just fail because temporarily some server is down somewhere.
If server software did AIA chasing (e.g. nginx, or your SMTP server) it would see during startup that you configured a bare certificate, and do the same AIA chasing that browsers do today but only once for the lifetime of the service and with the privilege of being a server (likely better Internet access, and more likely somebody technical sees the error output if there are problems) and it could have retry/fallback behaviour and if it doesn't work well the server can tell its administrator to fix the problem, whereas the browser doesn't have a way to contact that admin.
But Mozilla's choice here was pragmatic. We get the world we deserve.
- jcims 5y agoYour suggestion would definitely be more efficient. I’d split the difference and just say the server could just abort startup if it can’t validate its own cert. Letting servers indiscriminately connect to the internet isn’t great security practice, something that was substantially reinforced with the recent log4j issue.
- ayende 5y agoI hate this idea. What happens if the server starts at a point in time when it cannot do the AIA chasing? That means that you have a (silent) dependency that you are absolutely unaware of. When this fails, your service is down. Far better to have it setup so the service fails if the certificate is not configured with the whole chain.
- tialaramex 5y agoWhat I propose (AIA chasing in servers) can be dropped into existing servers and it won't make anything worse, in most cases it will make things better. What you propose either can't be dropped in (so it's an interesting experiment for a new web server, are you writing one? No? Then it's of no value) or if it's dropped in it breaks working systems, making you a nuisance. If you have a time machine so you can go back to the mid-1990s and ensure all web servers work your way your idea is better or at least good. But you don't have a time machine, we must work with what exists today.
- patmorgan23 5y agoIf the AIA fails it could just continue as normal.