Path: csiph.com!weretis.net!feeder8.news.weretis.net!reader5.news.weretis.net!news.solani.org!.POSTED!not-for-mail From: Richmond Newsgroups: alt.comp.software.seamonkey Subject: Re: eMudhra Intermediate CA Compromise - Action required on Linux Date: Wed, 28 Oct 2026 13:31:22 +0000 Organization: Frantic Message-ID: <824ie6lzo5.fsf@example.com> References: <827bj42gpa.fsf@example.com> <11booqc$12q96$1@dont-email.me> MIME-Version: 1.0 Content-Type: text/plain Injection-Info: solani.org; logging-data="586800"; mail-complaints-to="abuse@news.solani.org" User-Agent: Gnus/5.13 (Gnus v5.13) Cancel-Lock: sha1:WvHyrEGgdz/Chpin7u1nF/nP6kc= sha1:jO9AMzCQBCkAzneelIabgC2vao8= X-User-ID: eJwFwQkBwDAIA0BLfIFWDmPEv4TewVNzKhIZIDibLIEcqu/cdeLf7zAgYdYZ0xCYDke2+j4llxFd Xref: csiph.com alt.comp.software.seamonkey:8762 "David E. Ross" writes: > On 10/26/2026 4:19 PM, Richmond wrote: >> I tested Seamonkey and found it vulnerable. I am on Linux. I tested >> it here: >> >> https://emudhra.we-have-a-problem.com/#check >> >> And then I went into certificate management and disabled the Emudhra >> certificates so it now passes the test. >> >> I don't know the situation on Windows, but maybe it uses the Windows >> store certificate store? >> >> https://getrff.com/blog/emudhra-compromise-linux-servers/ >> > > SeaMonkey and Firefox have an internal set of root certificates. > > For SeaMonkey 2.53.24, go to [Edit > Preferences > Privacy & Security > > Certificates > Manage Certificates]. The list is sorted > alphabetically by authority name. > > For Firefox 115.43.1 esr, select the hamburger at the right of the > menu bar. Select [Settings > Privacy & Security]. Scroll down to > Security. Under Certificates, select the View Certificates button. > Here too, the list is sorted alphabetically by authority name. > > To suppress the use of certificates in both SeaMonkey and Firefox, > select "Edit Trust" for each certificate, one at a time. Do not > select "Delete or Distrust", which apparently is not effective on root > certificates. According to https://blog.mozilla.org/security/2026/10/20/protecting-firefox-users-following-the-compromise-of-emudhra-intermediate-certificates/ linked from one of the pages above, Firefox was fixed without the need for an update back on October 17th using certificate revocation. I am using Beta and it was fixed somehow without me doing anything.