On Jul 7, 2024, at 12:33, Enrique Artal <enriquear...@gmail.com> wrote: > I made other tries, and using certutil to get the key, this program > complained about an obsolete rc2-40-cbc something; adding the option -legacy > was successful and bringing back the certificate to pk12 I was able to import > it in google-chrome (still not in firefox).
You can check your current cryptography policy by running: update-crypto-policy --show It should return DEFAULT If you set it to LEGACY (update-crypto-policy --set LEGACY) does it work? If this is the case, most likely the encryption type is simply not supported in the default configuration. Is it possible that whoever issued the cert has created a new one with an algorithm that isn’t rather old and falling out of support? -- Jonathan Billings -- _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
