Reply to thread

Message

<blockquote data-quote="RejZoR" data-source="post: 754748" data-attributes="member: 57233">I just found out the reason. If I export the certificate and encrypt it using AES256, it&#039;ll be failing to import through all browsers. If I export it using only TripleDES encryption, it works fine. Why the hell is it offering me AES256 during exporting if it&#039;s apparently some exotic unsupported encryption for .pfx file? The hell!?If that happens, you need to import .pfx file into Windows Certificate Store by double clicking it and it will accept even AES256 encrypted .pfx file. Then you export it via Opera which uses same store to parse the certificates, then export it and make sure you DON&#039;T use AES256 encryption. Use TripleDES. Then it&#039;ll work in all browsers again. Bizarre. Like usual with anything I do... One would expect AES256 for certificates to be widely supported given how standard this encryption is opposed to TripleDES which has been replaced by AES256 ages ago afaik. Hm.</blockquote>

[QUOTE="RejZoR, post: 754748, member: 57233"] I just found out the reason. If I export the certificate and encrypt it using AES256, it'll be failing to import through all browsers. If I export it using only TripleDES encryption, it works fine. Why the hell is it offering me AES256 during exporting if it's apparently some exotic unsupported encryption for .pfx file? The hell!? If that happens, you need to import .pfx file into Windows Certificate Store by double clicking it and it will accept even AES256 encrypted .pfx file. Then you export it via Opera which uses same store to parse the certificates, then export it and make sure you DON'T use AES256 encryption. Use TripleDES. Then it'll work in all browsers again. Bizarre. Like usual with anything I do... One would expect AES256 for certificates to be widely supported given how standard this encryption is opposed to TripleDES which has been replaced by AES256 ages ago afaik. Hm. [/QUOTE]

Verification