openssl-engine | 易学教程

CURLINFO_SSL_ENGINES don't list openssl engine

阅读更多关于 CURLINFO_SSL_ENGINES don't list openssl engine

问题 I try to use engine pkcs11 with curl. Firstly, I add my engine pkcs11 to openssl. int initEngine() { ENGINE_load_builtin_engines(); ENGINE *e; display_engine_list(); e = ENGINE_by_id("dynamic"); if(!e) { return -1; } if(!ENGINE_ctrl_cmd_string(e, "SO_PATH", ENGINE_SO_PATH, 0)) { return -2; } if(!ENGINE_ctrl_cmd_string(e, "ID", "pkcs11", 0)) { return -3; } if(!ENGINE_ctrl_cmd_string(e, "LIST_ADD", "1", 0)) { return -4; } if(!ENGINE_ctrl_cmd_string(e, "LOAD", NULL, 1)) { return -5; } if(!ENGINE

OpenSSL can't establish SSL connection because unsupported protocol

阅读更多关于 OpenSSL can't establish SSL connection because unsupported protocol

来源： https://stackoverflow.com/questions/62357205/openssl-cant-establish-ssl-connection-because-unsupported-protocol

javax.net.ssl.SSLException - the trustAnchors parameter must be non-empty [duplicate]

阅读更多关于 javax.net.ssl.SSLException - the trustAnchors parameter must be non-empty [duplicate]

问题 This question already has answers here : Error - trustAnchors parameter must be non-empty (40 answers) Closed last year . When I try to run ./gradlew run I keep getting: Downloading https://services.gradle.org/distributions/gradle-4.4.1-bin.zip Exception in thread "main" javax.net.ssl.SSLException: java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty Tried curl -v https://services.gradle.org/distributions

Attach an ENGINE context to a SSL_CTX

阅读更多关于 Attach an ENGINE context to a SSL_CTX

问题 I am wondering if there is a possibility to attach an ENGINE* implementation to a SSL_CTX* and/or SSL* structures. What I want to achieve is to have a SSL_CTX* that will be set with the default cryptographic operations builtin in OpenSSL and another SSL_CTX* that will use a dedicated HSM as the crypto layer. Is a way that I can achieve this? From what I've read one could register and set to default some cryptographic operations(random, ciphers, md, etc...) but those that have been set will be

Attach an ENGINE context to a SSL_CTX

阅读更多关于 Attach an ENGINE context to a SSL_CTX

I am wondering if there is a possibility to attach an ENGINE* implementation to a SSL_CTX* and/or SSL* structures. What I want to achieve is to have a SSL_CTX* that will be set with the default cryptographic operations builtin in OpenSSL and another SSL_CTX* that will use a dedicated HSM as the crypto layer. Is a way that I can achieve this? From what I've read one could register and set to default some cryptographic operations(random, ciphers, md, etc...) but those that have been set will be used and not the builtin ones. e.g. EVP_CipherInit_ex has its third parameter an ENGINE* . Encryption