Closed uuonda closed 6 months ago
Maybe it's also why I needed to update sample certificate to test TLS?
Maybe. I'm not testing TLS. Why would I use test.pkcs12
when I have CA issued certificates?
It quick test some TLS things without bothering to issue openssl
commands or using actual CA during the development. For example, to connect to wss://127.0.0.1
from a https://
site in browser (by temporarily approving the test certificate). ws://127.0.0.1
won't work, you need some TLS.
Right. It's just that on many systems openssl command from the docs or embedded help produces a pkcs12 archive incompatible with websocat. And the error message is not exactly descriptive.
Anyway, whoever else might have this problem should be able to find this solution on the issues page.
I'll probably adjust the sample command line in the help and the document.
On OpenSSL 1.x.x this command from the docs generates pkcs12 file incompatible with websocat.
The error message is not printed until after first incoming connection.
This happens because OpenSSL 1.x.x uses "legacy" RC2-40 algorithm. The fix is
Hopefully that will save some time for someone.