Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > alt.comp.software.seamonkey > #8762
| From | Richmond <dnomhcir@gmx.com> |
|---|---|
| Newsgroups | alt.comp.software.seamonkey |
| Subject | Re: eMudhra Intermediate CA Compromise - Action required on Linux |
| Date | 2026-10-28 13:31 +0000 |
| Organization | Frantic |
| Message-ID | <824ie6lzo5.fsf@example.com> (permalink) |
| References | <827bj42gpa.fsf@example.com> <11booqc$12q96$1@dont-email.me> |
"David E. Ross" <nobody@nowhere.invalid> 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.
Back to alt.comp.software.seamonkey | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
eMudhra Intermediate CA Compromise - Action required on Linux Richmond <dnomhcir@gmx.com> - 2026-10-26 23:19 +0000
Re: eMudhra Intermediate CA Compromise - Action required on Linux "David E. Ross" <nobody@nowhere.invalid> - 2026-10-26 16:47 -0700
Re: eMudhra Intermediate CA Compromise - Action required on Linux Richmond <dnomhcir@gmx.com> - 2026-10-28 13:31 +0000
Re: eMudhra Intermediate CA Compromise - Action required on Linux Nuno Silva <nunojsilva@invalid.invalid> - 2026-10-31 10:41 +0000
Re: eMudhra Intermediate CA Compromise - Action required on Linux Barryedwin1 <mrbarryedw.20@aussiebroadband.com.au> - 2026-10-27 07:56 +0800
Re: eMudhra Intermediate CA Compromise - Action required on Linux frg <frgrahl@gmx.net> - 2026-10-27 01:03 +0100
Re: eMudhra Intermediate CA Compromise - Action required on Linux Barryedwin1 <mrbarryedw.20@aussiebroadband.com.au> - 2026-10-27 08:56 +0800
Re: eMudhra Intermediate CA Compromise - Action required on Linux frg <frgrahl@gmx.net> - 2026-10-27 12:14 +0100
Re: eMudhra Intermediate CA Compromise - Action required on Linux Dirk Fieldhouse <surname@gmx.net.plusremovethisandtherest.invalid> - 2026-10-27 15:21 +0000
Re: eMudhra Intermediate CA Compromise - Action required on Linux Nuno Silva <nunojsilva@invalid.invalid> - 2026-10-31 10:43 +0000
Re: eMudhra Intermediate CA Compromise - Action required on Linux Dirk Fieldhouse <surname@gmx.net.plusremovethisandtherest.invalid> - 2026-10-31 10:51 +0000
Re: eMudhra Intermediate CA Compromise - Action required on Linux Nuno Silva <nunojsilva@invalid.invalid> - 2026-10-31 11:13 +0000
Re: eMudhra Intermediate CA Compromise - Action required on Linux R Daneel Olivaw <desonbalon@mail.com> - 2026-10-31 21:18 +0100
Re: eMudhra Intermediate CA Compromise - Action required on Linux R Daneel Olivaw <desonbalon@mail.com> - 2026-11-06 16:06 +0100
csiph-web