Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > alt.comp.software.seamonkey > #8753 > unrolled thread
| Started by | Richmond <dnomhcir@gmx.com> |
|---|---|
| First post | 2026-10-26 23:19 +0000 |
| Last post | 2026-11-06 16:06 +0100 |
| Articles | 14 — 7 participants |
Back to article view | Back to alt.comp.software.seamonkey
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
| From | Richmond <dnomhcir@gmx.com> |
|---|---|
| Date | 2026-10-26 23:19 +0000 |
| Subject | eMudhra Intermediate CA Compromise - Action required on Linux |
| Message-ID | <827bj42gpa.fsf@example.com> |
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/
[toc] | [next] | [standalone]
| From | "David E. Ross" <nobody@nowhere.invalid> |
|---|---|
| Date | 2026-10-26 16:47 -0700 |
| Message-ID | <11booqc$12q96$1@dont-email.me> |
| In reply to | #8753 |
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. -- David E. Ross <http://www.rossde.com> NO, not everyone has a smart phone. My wife and I have "dumb cell phones" and a land-line. Neither of us can handle QR codes, reply to text messages, or have any kind of phone-based Internet connections. We have no APS on any phone. We can send and receive photos only through our desktop PCs.
[toc] | [prev] | [next] | [standalone]
| From | Richmond <dnomhcir@gmx.com> |
|---|---|
| Date | 2026-10-28 13:31 +0000 |
| Message-ID | <824ie6lzo5.fsf@example.com> |
| In reply to | #8754 |
"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.
[toc] | [prev] | [next] | [standalone]
| From | Nuno Silva <nunojsilva@invalid.invalid> |
|---|---|
| Date | 2026-10-31 10:41 +0000 |
| Message-ID | <11c4gko$1025g$3@dont-email.me> |
| In reply to | #8754 |
On 2026-10-26, David E. Ross wrote: > 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. (You can select more than one in that list, but expect as many prompts for the trust change as certificates you've selected.) -- Nuno Silva
[toc] | [prev] | [next] | [standalone]
| From | Barryedwin1 <mrbarryedw.20@aussiebroadband.com.au> |
|---|---|
| Date | 2026-10-27 07:56 +0800 |
| Message-ID | <11bopb9$12t4o$1@dont-email.me> |
| In reply to | #8753 |
Richmond wrote on 27/10/26 7:19 am: > 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/ > Much appreciated Richmond. The linked instructions worked a treat.
[toc] | [prev] | [next] | [standalone]
| From | frg <frgrahl@gmx.net> |
|---|---|
| Date | 2026-10-27 01:03 +0100 |
| Message-ID | <nka82hFeaemU1@mid.individual.net> |
| In reply to | #8755 |
Barryedwin1 wrote: > Richmond wrote on 27/10/26 7:19 am: >> 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/ >> > Much appreciated Richmond. The linked instructions worked a treat. > It is already fixed in the nightlies and will be fixed in the upcoming 2.53.25 beta. frg
[toc] | [prev] | [next] | [standalone]
| From | Barryedwin1 <mrbarryedw.20@aussiebroadband.com.au> |
|---|---|
| Date | 2026-10-27 08:56 +0800 |
| Message-ID | <11bosr7$140es$1@dont-email.me> |
| In reply to | #8756 |
frg wrote on 27/10/26 8:03 am: > Barryedwin1 wrote: >> Richmond wrote on 27/10/26 7:19 am: >>> 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/ >>> >> Much appreciated Richmond. The linked instructions worked a treat. >> > > It is already fixed in the nightlies and will be fixed in the upcoming > 2.53.25 beta. > > frg Much appreciated Frank. My 20261024213249 is a bit behind. Will get to it right now. Barry.
[toc] | [prev] | [next] | [standalone]
| From | frg <frgrahl@gmx.net> |
|---|---|
| Date | 2026-10-27 12:14 +0100 |
| Message-ID | <nkbfc9Fk6tuU1@mid.individual.net> |
| In reply to | #8757 |
Barryedwin1 wrote: > frg wrote on 27/10/26 8:03 am: >> Barryedwin1 wrote: >>> Richmond wrote on 27/10/26 7:19 am: >>>> 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/ >>>> >>> Much appreciated Richmond. The linked instructions worked a treat. >>> >> >> It is already fixed in the nightlies and will be fixed in the upcoming >> 2.53.25 beta. >> >> frg > Much appreciated Frank. My 20261024213249 is a bit behind. Will get to it > right now. Barry. Not much in 10/25. Just a few more backports from Fireofx esr. frg
[toc] | [prev] | [next] | [standalone]
| From | Dirk Fieldhouse <surname@gmx.net.plusremovethisandtherest.invalid> |
|---|---|
| Date | 2026-10-27 15:21 +0000 |
| Message-ID | <11bqfhr$ghl4$1@solani.org> |
| In reply to | #8758 |
Just removing the G3 root certificate for the problem issuer causes the up-thread linked we-have-a-problem check to pass. /df -- London UK
[toc] | [prev] | [next] | [standalone]
| From | Nuno Silva <nunojsilva@invalid.invalid> |
|---|---|
| Date | 2026-10-31 10:43 +0000 |
| Message-ID | <11c4gp7$1025g$4@dont-email.me> |
| In reply to | #8760 |
On 2026-10-27, Dirk Fieldhouse wrote: > Just removing the G3 root certificate for the problem issuer causes the > up-thread linked we-have-a-problem check to pass. Including the bottom half ones that are rooted on Comodo/Sectigo? -- Nuno Silva
[toc] | [prev] | [next] | [standalone]
| From | Dirk Fieldhouse <surname@gmx.net.plusremovethisandtherest.invalid> |
|---|---|
| Date | 2026-10-31 10:51 +0000 |
| Message-ID | <11c4h86$ma6n$1@solani.org> |
| In reply to | #8767 |
On 31/10/2026 10:43, Nuno Silva wrote: > On 2026-10-27, Dirk Fieldhouse wrote: > >> Just removing the G3 root certificate for the problem issuer causes the >> up-thread linked we-have-a-problem check to pass. > > Including the bottom half ones that are rooted on Comodo/Sectigo? The site lists compromised intermediate certs with half chaining to "emSign Root TLS CA - G3" and half to "AAA Certificate Services". Result: > Your browser trusted 0 of 14 compromised certificate chains. /df -- London UK
[toc] | [prev] | [next] | [standalone]
| From | Nuno Silva <nunojsilva@invalid.invalid> |
|---|---|
| Date | 2026-10-31 11:13 +0000 |
| Message-ID | <11c4igv$1025g$6@dont-email.me> |
| In reply to | #8768 |
On 2026-10-31, Dirk Fieldhouse wrote:
> On 31/10/2026 10:43, Nuno Silva wrote:
>> On 2026-10-27, Dirk Fieldhouse wrote:
>>
>>> Just removing the G3 root certificate for the problem issuer causes the
>>> up-thread linked we-have-a-problem check to pass.
>>
>> Including the bottom half ones that are rooted on Comodo/Sectigo?
>
> The site lists compromised intermediate certs with half chaining to
> "emSign Root TLS CA - G3" and half to "AAA Certificate Services".
>
> Result:
>> Your browser trusted 0 of 14 compromised certificate chains.
Ah, then that was indeed enough!
("AAA Certificate Services" is from Comodo/Sectigo.)
--
Nuno Silva
[toc] | [prev] | [next] | [standalone]
| From | R Daneel Olivaw <desonbalon@mail.com> |
|---|---|
| Date | 2026-10-31 21:18 +0100 |
| Message-ID | <11c5if1$ng0t$1@paganini.bofh.team> |
| In reply to | #8760 |
Dirk Fieldhouse wrote: > Just removing the G3 root certificate for the problem issuer causes the > up-thread linked we-have-a-problem check to pass. > > /df > I use openSUSE (an older version, now unmaintained) and tried the appropriate method detailed in https://emudhra.we-have-a-problem.com/#check Firefox gives me "Did not connect" for all 14 chains, Seamonkey gives me "X Insecure" for the lot.
[toc] | [prev] | [next] | [standalone]
| From | R Daneel Olivaw <desonbalon@mail.com> |
|---|---|
| Date | 2026-11-06 16:06 +0100 |
| Message-ID | <11ckqd0$2t5ad$1@paganini.bofh.team> |
| In reply to | #8753 |
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/ > I'm still running OpenSUSE Leap 15.6 - including its Mozilla Test repository - and after having applied some updates today, all of the 14 certificates are suffering from an absence of trust. Definitely a good thing. (or have they expired naturally?)
[toc] | [prev] | [standalone]
Back to top | Article view | alt.comp.software.seamonkey
csiph-web