-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Load multiple CA certificates from a path instead of a file #3276
Comments
libwebsockets doesn't provide an option to provide a `capath`, ie a directory that contains multiple certificates. ( warmcat/libwebsockets#3276 ) To avoid confusion, explicitly state that it's not supported for websockets in the doc for mosquitto.conf, and add a warning if option is provided while `capath` is not provided.
Hm... it's not true 'there is no code path...'. When openssl is built, it has a default, platform-specific path decided at build-time, it will check for its trust store (appended PEMs). You can look with strace while openssl is starting on your process to see the path it tries on your platform. The other way is lws will call your protocol with
There's also a client version, ckeck lws-callbacks.h. |
Thanks @lws-team , that's a great point, I had missed these code paths. I'll try to use |
libwebsockets doesn't provide an option to provide a `capath`, ie a directory that contains multiple certificates. ( warmcat/libwebsockets#3276 ) To avoid confusion, explicitly state that it's not supported for websockets in the doc for mosquitto.conf, and add a warning if option is provided while `capath` is not provided.
ssl_ca_filepath
needs to be set to a file, which results in a call toSSL_CTX_load_verify_file
.This appears to be the case both on client & server side.
There is no code path that makes it possible to use
SSL_CTX_load_verify_dir
to load multiple certificates from a directory.Multiple certificates can still be loaded through
ssl_ca_filepath
asSSL_CTX_load_verify_file
accepts a file that contains multiple certificates.The text was updated successfully, but these errors were encountered: