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
The problem with passing a file name is that a client application that ships with a certificate (e.g. as an embedded QT resource file) would have to save the certificate on disk before it can be used with libhv/openssl. This allows a user of the application to tamper with the certificate which would render server verification useless.
My suggestion is to add more fields to hssl_ctx_opt_t to allow using an in-memory certificate (byte buffer).
Verifying the websocket server's certificate requires a filename:
There does not seem to be an option to pass an in-memory certificate:
https://github.com/ithewei/libhv/blob/8c67e056f63c6cb4f9476d5904bef5ef9f350f12/ssl/hssl.h#L39C1-L46C41
The problem with passing a file name is that a client application that ships with a certificate (e.g. as an embedded QT resource file) would have to save the certificate on disk before it can be used with libhv/openssl. This allows a user of the application to tamper with the certificate which would render server verification useless.
My suggestion is to add more fields to
hssl_ctx_opt_t
to allow using an in-memory certificate (byte buffer).Similar issue: https://stackoverflow.com/questions/5052563
The text was updated successfully, but these errors were encountered: