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
When using the pkcs8 certificate, I found that the encryption algorithm 3DES of the certificate is not secure. Then I used the V2 parameter to generate the certificate, the command is as follows
But logstash gives an error when applying this certificate:
It looks like the encryption method of the certificate is not recognized!
After researching, I found that the input-beats plugin uses netty's SslContext. When using openssl to generate a certificate to specify an algorithm such as aes256, when using encryptedPrivateKeyInfo.getAlgName() to get the algorithm name, the result is: 1.2.840.113549.1.5.13, netty Don't know the name at all.
After a long exploration experiment, I found not-yet-commons-ssl-0.3.17.jar to be a good solution to try and modify using its ideas. Or support certificate formats other than pkcs8.
When using the pkcs8 certificate, I found that the encryption algorithm 3DES of the certificate is not secure. Then I used the V2 parameter to generate the certificate, the command is as follows
But logstash gives an error when applying this certificate:
It looks like the encryption method of the certificate is not recognized!
After researching, I found that the input-beats plugin uses netty's SslContext. When using openssl to generate a certificate to specify an algorithm such as aes256, when using encryptedPrivateKeyInfo.getAlgName() to get the algorithm name, the result is: 1.2.840.113549.1.5.13, netty Don't know the name at all.
After a long exploration experiment, I found not-yet-commons-ssl-0.3.17.jar to be a good solution to try and modify using its ideas. Or support certificate formats other than pkcs8.
#372
The text was updated successfully, but these errors were encountered: