Eheka Pytyvõha

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.

Learn More

New Windows Security pop up with Thunderbird 91

  • 2 Mbohovái
  • 1 oguereko ko apañuái
  • 1 Hecha
  • Mbohovái ipaháva christ1

more options

With the update to TB 91, we are seeing the attached pop up when composing a signed or encrypted email. I find this a little surprising because we are storing our email certificates directly in TB rather than in the windows certificate store. Could anyone shed more light on the changes to the way TB is dealing with signing certificates? Thanks.

With the update to TB 91, we are seeing the attached pop up when composing a signed or encrypted email. I find this a little surprising because we are storing our email certificates directly in TB rather than in the windows certificate store. Could anyone shed more light on the changes to the way TB is dealing with signing certificates? Thanks.
Mba’erechaha japyhypyre oñondivegua

Opaite Mbohovái (2)

more options

Also, it seems like TB will try to make use of a smartcard if one is present even when configured to use a local TB cert for encryption.

more options

Try to set the pref security.enterprise_roots.enabled to false. For more information see https://bugzilla.mozilla.org/show_bug.cgi?id=1726442

Also, it seems like TB will try to make use of a smartcard if one is present even when configured to use a local TB cert for encryption.

If the private key is on the smartcard only, there's no way around that. The private key is needed to sign messages, and to read encrypted messages. If the private key is also present in the Thunderbird certificate store, then what is the point of using a smartcard at all?