| @@ -23,7 +23,4 @@ If that is the case your are fine and your fixing has worked as expected. | |||
| 23 | 23 | ## links | |
| 24 | 24 | ||
| 25 | 25 | * Website for the bug: [https://emudhra.we-have-a-problem.com/](https://emudhra.we-have-a-problem.com/) | |
| 26 | - | * [HackerNews article about the Vulnerability](https://thehackernews.com/2026/10/eight-emudhra-ca-keys-compromised.html) | |
| 27 | - | ||
| 28 | - | ||
| 29 | - | ||
| 26 | + | * [HackerNews article about the Vulnerability](https://thehackernews.com/2026/10/eight-emudhra-ca-keys-compromised.html) | |
scusi / fixing eMudhra CA Keys Compromise in FreeBSD
Last active 2 weeks ago
describes how to fix the issue in FreeBSD
| @@ -0,0 +1,29 @@ | |||
| 1 | + | # fixing eMudhra CA Keys Compromise in FreeBSD | |
| 2 | + | ||
| 3 | + | fixing the issue on FreeBSD ist literaly 3 commands: | |
| 4 | + | ||
| 5 | + | ``` | |
| 6 | + | sudo cp /etc/ssl/certs/14bc7599.0 /usr/share/certs/untrusted/14bc7599.pem | |
| 7 | + | sudo cp /etc/ssl/certs/eed8c118.0 /usr/share/certs/untrusted/eed8c118.pem | |
| 8 | + | sudo certctl rehash | |
| 9 | + | ``` | |
| 10 | + | ||
| 11 | + | ## verify the fix | |
| 12 | + | ||
| 13 | + | With the follwoing two commands you can check if you fixed the issue. | |
| 14 | + | ||
| 15 | + | ``` | |
| 16 | + | fetch https://dv-g3b-emudhra.we-have-a-problem.com/ | |
| 17 | + | fetch https://dv-g3b-aaa-emudhra.we-have-a-problem.com/ | |
| 18 | + | ``` | |
| 19 | + | ||
| 20 | + | Both above fetchcommands are expectedto fail with a `Certificate verification failed` error. | |
| 21 | + | If that is the case your are fine and your fixing has worked as expected. | |
| 22 | + | ||
| 23 | + | ## links | |
| 24 | + | ||
| 25 | + | * Website for the bug: [https://emudhra.we-have-a-problem.com/](https://emudhra.we-have-a-problem.com/) | |
| 26 | + | * [HackerNews article about the Vulnerability](https://thehackernews.com/2026/10/eight-emudhra-ca-keys-compromised.html) | |
| 27 | + | ||
| 28 | + | ||
| 29 | + | ||