Like: https://www.data.gov
"Due to a lapse in government funding all Data.gov websites will be unavailable until further notice."
Which is pretty odd, because putting up these blocker pages probably costs more than just letting the sites run unattended.
Security maintenance, keeping databases up, monitoring the various systems, risk of DDoS, answering to users' inquires, bandwidth... - it requires real money to keep any production site live.
Given that these folks are basically working without pay, I don't blame them for wanting to put a cover page saying "Sorry, we're down", and call it a day.
The census site seems to be a decent middle ground. Banner at the top says "NOTICE: Due to a lapse in federal funding portions of this website are not being updated." Still functional, but if something's not updated, you know why.
That is precisely what it does. Serving an invalid certificate and requiring user click-through allows for a man in the middle attacker to inject their own certificate without further error and will therefore be able to intercept login credentials.
From the original article[1]: "One such example is https://ows2.usdoj.gov, a U.S. Department of Justice website which uses a certificate that expired in the week leading up the shutdown. The certificate has been signed by a trusted certificate authority, GoDaddy, but it has not been renewed since it expired on 17 December 2018."
It was probably already renewed, there's just no sysadmin to import the fresh cert. =]
[1] - https://news.netcraft.com/archives/2019/01/10/gov-security-f...
It's also pretty irresponsible to let certs get this close to expiration. Why weren't they renewed 60 days ago?
I handed this for one of the major beverage brands recently it was flagged when GA showed a massive decline - luckily it was one of the smaller noncore brands.
By contrast, for most projects, I have standard cert/le automatically updating every 2-3 months. LE was just becoming a thing a couple years ago, and they'd never heard of it. I'm not saying they should all use LE, but the initial time investment of providing an automated process to renew and update via API would pay dividends in the long run (but the people that feel that the most don't have the clout/power to lobby for such things, usually).
Not surprising to me to see this is the case for local and federal govt too.
> This article is overly hyperbolic. Some obscure subdomains of government websites are serving expired x509 certificates. They're not down and this definitely doesn't compromise the encryption that protects any login credentials. Anyway, it is embarassing to see certificate renewal is not automated - it's something any good sysadmin would have set up.
https://www.reddit.com/r/technology/comments/aeps41/governme...