Live data from Hacker News

Microsoft failed to rotate certificates for winget CDN on time

cdn.winget.microsoft.com

61–69 of 69 posts

Re: Microsoft failed to rotate certificates for winget CDN on time

#61

Why would anyone standardize on winget when there's chocolatey and it works everywhere you can run Windows software? Recently I decided to install Windows Server on one of my PC instead of Windows 10/11. I thought, why not attempt to use winget and/or the Windows App Store to install basic software to see how far that takes me. Immediate dead end. Apparently there's no access from the App Store on Windows Server. You…

because winget is built-in

Re: Microsoft failed to rotate certificates for winget CDN on time

#62
post #47
post #20

Earlier quoted context omitted.

> But there's enough places that can't set up automated processes Why can't they be automated? And anyway, this is the exact problem that short expiration times avoid! Systems that aren't set up for automation, and rely on someone once a year remembering some creaky, error prone process to get a new cert. Much better to force short expiration times so manual cert renewal is a thing of the past.

The people installing the certs aren't necessarily the people buying the certs. I can't do anything to automate the cert purchases at my current workplace; that's a separate team that I have no control or influence over. Shorter expiration times just mean they send me an email with the new .pfx every 4 months instead of every 12.

If they had to do that every 2 months instead of every 12, they might get tired enough of it to fix their broken process.

Re: Microsoft failed to rotate certificates for winget CDN on time

#63
post #33

If only there was a cloud based solution by a large company for managing certificates automatically! (Azure Front Door)

The certificate was renewed, but it wasn't deployed correctly. We're looking into the root cause.

I'm just thankful we switched to afd and never have to think about certs (neither issuing nor deploying) again. You should check it out!

Re: Microsoft failed to rotate certificates for winget CDN on time

#64
post #46

Earlier quoted context omitted.

Google made quite a few questionable changes in Chrome (with the rest feeling forced to follow the fashion set by Chrome) and not displaying EV info. Many big organisations use tens of domain some of which look very suspicious. Information in a EV/OV cert is often the only way to establish that a domain operated by the legitimate company (and not by a phisher who registered a similarly looking domain).

Google and Firefox made the change roughly at the same time -- because there was a lot of evidence that EV indicators simply don't work. Users don't pay attention to them, and even if they did, the idea that company names are unique - even within a jurisdiction - is simply incorrect. The only upside of EV certificates is that the PKI companies can seek a higher rent.

Even if a higher price is the only EV difference (which not exactly the case) it would be enough make sites with EV certs much less likely to be used in phishing - threat actors want to keep their cost down because they frequently register a lot of domains (much more than most legit companies). And even company names are not unique good luck with registering PayPal Inc or Bank of America Corporation to get an EV cert for your phishing site.

Re: Microsoft failed to rotate certificates for winget CDN on time

#65

Why would anyone standardize on winget when there's chocolatey and it works everywhere you can run Windows software? Recently I decided to install Windows Server on one of my PC instead of Windows 10/11. I thought, why not attempt to use winget and/or the Windows App Store to install basic software to see how far that takes me. Immediate dead end. Apparently there's no access from the App Store on Windows Server. You…

Not sure why you'd be trying to run Server on a workstation?

Re: Microsoft failed to rotate certificates for winget CDN on time

#66

Earlier quoted context omitted.

Advantage of certbot: a systemd timer that runs every other week is very easy to write, because "certbot renew" doesn't need any user interactions. So it's literally < 10 lines of systemd unit file to automate it.

Or one line of cron.

> Or one line of cron.

For each distro, with each having their own format and own crond implementation, at each different file paths.

Re: Microsoft failed to rotate certificates for winget CDN on time

#67
Microsoft's certificate management skills have gone down the drain anyway, so this doesn't surprise me. I have a long standing support case open with them about how they ship one of their more obscure tools signed with the wrong code signing certificate (one signed by their PKI for Azure INTERNAL usage, which should have everyone a tiny bit worried), and I've pretty much given up on trying to get the quite-obviously-on-an-H1B developer (which I mention only to explain that this PROBABLY leads to a perverse incentive to sweep things under the rug), or any of the Indian support agents involved to comprehend that this isn't just inconvenient when one has AppLocker in place, but also that it violates Microsoft's internal policies (which I know for a fact that it does), and MSRC ignored my email about it, too, so… par for the course. ¯\_(ツ)_/¯

Re: Microsoft failed to rotate certificates for winget CDN on time

#68
post #46

Earlier quoted context omitted.

Google and Firefox made the change roughly at the same time -- because there was a lot of evidence that EV indicators simply don't work. Users don't pay attention to them, and even if they did, the idea that company names are unique - even within a jurisdiction - is simply incorrect. The only upside of EV certificates is that the PKI companies can seek a higher rent.

Even if a higher price is the only EV difference (which not exactly the case) it would be enough make sites with EV certs much less likely to be used in phishing - threat actors want to keep their cost down because they frequently register a lot of domains (much more than most legit companies). And even company names are not unique good luck with registering PayPal Inc or Bank of America Corporation to get an EV cert…

I don’t understand. Why would phishing attacks bother getting EV certificates? Users can’t tell the difference in modern browsers.

Re: Microsoft failed to rotate certificates for winget CDN on time

#69
post #68

Earlier quoted context omitted.

Even if a higher price is the only EV difference (which not exactly the case) it would be enough make sites with EV certs much less likely to be used in phishing - threat actors want to keep their cost down because they frequently register a lot of domains (much more than most legit companies). And even company names are not unique good luck with registering PayPal Inc or Bank of America Corporation to get an EV cert…

I don’t understand. Why would phishing attacks bother getting EV certificates? Users can’t tell the difference in modern browsers.

Depends on who user is. I hope a typical HN user can find a way to view certificate information even in a modern browser.

The problem is - in modern internet it is very hard to find out who is behind a particular domain: NS/A often point to a CDN or a cloud, info in whois is hidden and all you can see is 'Private'. OV/EV cert is often the only way to know that a domain like acmecorp-invoices.com is used by the same company as acmecorp.com and not phishing (registering a domain similar to the main company's domain is a bad but not uncommon practice).

One of a reasons to get OV/EV cert is to avoid you domain being listed as phishing - if would give a security expect no hints that your suspiciously looking domain is a legit one and not impersonation there is a risk that it would be blocked.

Phisher practically never use OV/EV certs on other hand (probably because they know there are little to no changes they'll get a cert with the target company's name in organizationName).

Post reply on HN