kareem-wolfssl

Hello @PaulMartinsen , Thank you for your contribution. I have had a separate customer request for absolute URN support, and I need it in our upcoming release, so I've integrated...

Hi @wlallemand , We do support this, but we strongly recommend against using it in production as the SSL key log file allows an attacker to compromise security. We only...

Hi @wlallemand , My colleague douzzer is working on resolving your first point in https://github.com/wolfSSL/wolfssl/pull/6861. With this PR, you will be able to build with --enable-keylog-export and not run into...

Hello @wlallemand, The PR I mentioned in my previous message was merged. wolfSSL now has a TLS 1.3 secret logging callback function built in called SessionSecret_callback_Tls13 which will be automatically...

Apologies, you are correct. I will work on fixing this in the near future.

Hi @llmlla , 4.2.0 is extremely outdated and no longer supported, please upgrade to 5.6.0, our latest release, and retry. Your root certs appear to have valid date formats, we...

Hi @yangyangliuli , To enable these cipher suites, you need to build wolfSSL with: `--enable-tls13 --enable-aesccm`

Contributor agreement approved.

Hi @mcr , As you've already found, we do install a wolfssl.pc file in your prefix under pkgconfig, by default this is in /usr/local/lib/pkgconfig/wolfssl.pc. Did you have any further questions...

Our build settings are stored in either options.h, or user_settings.h depending on how wolfSSL was built. These headers should be installed in /include/wolfssl. If you're building an application with wolfSSL,...