151 points keks24 2 hours ago 36 comments
keks24 2 hours ago | parent
# emerge --sync
# emerge --ask --oneshot --verbose ">=app-misc/ca-certificates-20260816.3.125"
To check via "curl": $ curl --url="https://dv-g3b-emudhra.we-have-a-problem.com/"
$ curl --url="https://dv-g3b-aaa-emudhra.we-have-a-problem.com/"
They should return: curl: (60) SSL certificate OpenSSL verify result: unable to get local issuer certificate (20)
More details here: https://curl.se/docs/sslcerts.html
curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the webpage mentioned above.
---* GLSA 202610-01: https://security.gentoo.org/glsa/202610-01
asqueella 2 hours ago | parent
philipwhiuk 1 hour ago | parent
The problem is Golang has it's own trust store. So you don't benefit from OS patching.
sspiff 47 minutes ago | parent
This CVE is literally just "versions of the Go deny list don't contain the eMuhdra revokation yet". Older versions of Go will still deny certs signed through the compromised certificate if the system store already has the update.
It's an or situation, not and.
zkmon 2 hours ago | parent
colinmarc 2 hours ago | parent
prodigycorp 50 minutes ago | parent
cedilla 1 hour ago | parent
If you think "that's weird to see such a small number in key generation" than you're one step ahead of whoever generated that key.
Unfortunately, unlike with RSA, small primes are not apparent in elliptic cryptography.
RazorX 1 hour ago | parent
palata 55 minutes ago | parent
What a weird comparison...
galadran 2 hours ago | parent
colinmarc 2 hours ago | parent
The very urgent uv/certifi/etc releases (and yet-to-be-done bun release) are about removing the compromised CAs as described here:
https://emudhra.we-have-a-problem.com/
In other words, that software bundled the compromised certs into the binary, so upgrading it is the only way to remove them.
This is about Go proactively blocking intermediates. Which shouldn't strictly be necessary as long as your OS has removed or distrusted the CAs (on my laptop, macOS has done that, although it seems like it did so in a way not all tools have access to; for example, rustls-platform-verifier respects it, but rustls-webpki still loads the bad CAs from the system trust store).
edit: forgot I can't use code blocks on HN
darkwater 1 hour ago | parent
ale42 1 hour ago | parent
colinmarc 1 hour ago | parent
darkwater 1 hour ago | parent
alt227 1 hour ago | parent
grey-area 1 hour ago | parent
Here is the original story: https://news.ycombinator.com/item?id=50166579
alt227 38 minutes ago | parent
contingencies 43 minutes ago | parent
export CURL_CA_BUNDLE="$(brew --prefix)/etc/ca-certificates/cert.pem"
To verify, log in to a new shell and run curl https://dv-g3b-emudhra.we-have-a-problem.com/