You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is the option to protect private keys with a password (passed to the constructor of EvseSecurity).
The result is a PEM file that starts "-----BEGIN ENCRYPTED PRIVATE KEY-----"
When there is no password the following would be expected: "-----BEGIN PRIVATE KEY-----"
(TPM keys start with other strings)
At the moment when there is no password specified an empty password is used and the resulting file is still "-----BEGIN ENCRYPTED PRIVATE KEY-----".
I was hoping to use a generated key for mosquitto TLS and mosquitto doesn't support encrypted private key files.
My work around is to use OpenSSL to remove the encryption:
There is the option to protect private keys with a password (passed to the constructor of EvseSecurity).
The result is a PEM file that starts "-----BEGIN ENCRYPTED PRIVATE KEY-----"
When there is no password the following would be expected: "-----BEGIN PRIVATE KEY-----"
(TPM keys start with other strings)
At the moment when there is no password specified an empty password is used and the resulting file is still "-----BEGIN ENCRYPTED PRIVATE KEY-----".
I was hoping to use a generated key for mosquitto TLS and mosquitto doesn't support encrypted private key files.
My work around is to use OpenSSL to remove the encryption:
Perhaps EvseSecurity should be updated to generate unencrypted key files when no password is specified (which would match expectation).
The text was updated successfully, but these errors were encountered: