📣 Help shape Firefox by joining our Test Days event on July 21–27 to test the Firefox Semantic History Search in Firefox Beta 142

Emboyke pytyvõha apovai. Ndorojeruremo’ãi ehenói térã eñe’ẽmondóvo pumbyrýpe ha emoherakuãvo marandu nemba’etéva. Emombe’u tembiapo imarãkuaáva ko “Marandu iñañáva” rupive.

Kuaave

about:config -> security.pki.certificate_transparency.disable_for_spki_hashes not working as expected

  • 11 Mbohovái
  • 0 oguereko ko apañuãi
  • 28 Hecha
  • Mbohovái ipaháva tomas.jetel

Hello community :)

hope everybody is doing well. I´m coming here with with asking for a help.

I´m managing browsers (Google Chrome, MS Edge and Firefox) in my company via GPOs. What we´ve been dealing with since 135 version came up is having the "Did Not Connect: Potential Security Issue error page , Error insufficient cert transparency" while visiting our internal resources.

Despite of having the security.pki.certificate_transparency.disable_for_spki_hashes set up -> main three certificate hashes are correctly added, basically copying the setup from Chromium browsers , where everything works as expected , Firefox is not.

The only way how to make it work is via security.pki.certificate_transparency.disable_for_hosts , which is , of course, not desirable , because of the security risks.

Does anyone face the same issues ?

Thank you very much ya´ll

Hello community :) hope everybody is doing well. I´m coming here with with asking for a help. I´m managing browsers (Google Chrome, MS Edge and Firefox) in my company via GPOs. What we´ve been dealing with since 135 version came up is having the "Did Not Connect: Potential Security Issue error page , Error insufficient cert transparency" while visiting our internal resources. Despite of having the security.pki.certificate_transparency.disable_for_spki_hashes set up -> main three certificate hashes are correctly added, basically copying the setup from Chromium browsers , where everything works as expected , Firefox is not. The only way how to make it work is via security.pki.certificate_transparency.disable_for_hosts , which is , of course, not desirable , because of the security risks. Does anyone face the same issues ? Thank you very much ya´ll

Ñemoĩporã poravopyre

Are you including the sha256/ at the beginning? Our implementation doesn't support that.

Emoñe’ẽ ko mbohavái ejeregua reheve 👍 1

Opaite Mbohovái (11)

Are you comma separating the hashes with no spaces?

¿Imba’eporãva?

Yes indeed. no spaces, just comma separated

¿Imba’eporãva?

One more question (I'm also asking the team).

I assume you're setting via the Preferences policy.

Does everything look correct in about:policies?

When you go to about:config and search on security.pki.certificate_transparency.disable_for_spki_hashes, is it set correctly?

And is it bold, italics, regular?

¿Imba’eporãva?

everything is correct , as far as im aware.. we havent read there should be set anything else that ties to ct transparency.

it is regular . As far as i recall, bold would be manually added value

KR Tomas

¿Imba’eporãva?

Ñemoĩporã poravopyre

Are you including the sha256/ at the beginning? Our implementation doesn't support that.

¿Imba’eporãva?

Oh .. yea , we do have sha256/ at the beginning :(

So it has to be removed ? have i missed some article where this info is present ?

Thank you !!

¿Imba’eporãva?

> So it has to be removed ? have i missed some article where this info is present ?

Yes, it does. I'm checking to see if we published that info anywhere.

¿Imba’eporãva?

Please do let me know if you can find any article with this information. In meantime, we will test it out :)

Thank you very much Tomas

¿Imba’eporãva?

So I was pointed to this page:

https://wiki.mozilla.org/SecurityEngineering/Certificate_Transparency#Enterprise_Policies

Which says:

Each entry must be the base64-encoded sha-256 hash of a certificate's DER-encoded subject public key info. This is intended to be similar to the Chrome enterprise policy CertificateTransparencyEnforcementDisabledForCas.

But I don't think that's clear :).

I'm going to update.

¿Imba’eporãva?

(I added - but the sha256/ prefix is not included.)

¿Imba’eporãva?

It is not indeed :) nevertheless, thank you very much for your help :) we have tested it and everything is working :)

¿Imba’eporãva?

Eporandumína

Nde eikéke nde mba’etepe embohovái hag̃ua ñe’ẽmondo. Ikatúpa, emoñepyrũ peteĩ porandu, ndereguerekói gueteriramo nemba’ete.