Re: [libmicrohttpd] using other TLS libraries

[Denis Dowling]

Hi Gauthier,

 

Nice work! I think this would be a great addition to libmicrohttpd. From an embedded perspective it would be great to be able to link to openssl or perhaps wolfssl (https://www.wolfssl.com/products/wolfssl/) to have a single SSL implementation on the platform. I like the way the TLS API cleanly defines the features that MHD needs from an SSL library.

 

Found a small typo:

diff --git a/src/microhttpd/tls_openssl.c b/src/microhttpd/tls_openssl.c

index fee4917..67d9162 100644

--- a/src/microhttpd/tls_openssl.c

+++ b/src/microhttpd/tls_openssl.c

@@ -906,8 +906,8 @@ MHD_TLS_openssl_session_write (struct MHD_TLS_Session * session,

 const struct MHD_TLS_Engine tls_engine_openssl =

{

-  "GnuTLS",

-  MHD_TLS_ENGINE_TYPE_GNUTLS,

+  "OpenSSL",

+  MHD_TLS_ENGINE_TYPE_OPENSSL,

   MHD_TLS_openssl_has_feature,

   MHD_TLS_openssl_init_context,

 

 

Regards,

Denis

From: libmicrohttpd [mailto:libmicrohttpd-bounces+address@hidden On Behalf Of Gauthier Haderer
Sent: Thursday, 19 October 2017 1:02 AM
To: address@hidden
Subject: [libmicrohttpd] using other TLS libraries

 

Hello,

 

I recently made changes to abstract the TLS API needed by MHD. And I added support for OpenSSL. Could someone review my changes and tell me if this is something that could be part of an official version?

 

You will find more information here: https://gnunet.org/bugs/view.php?id=4917#c12475

 

Thank you,

 

 

Gauthier

---

The information contained in this message and any attachments is strictly confidential and intended solely for the use of the intended recipient(s). The copyright in this communication belongs to (HSD). This message and any attachments are confidential and may be subject to legal or other professional privilege. Any confidentiality or privilege is not waived or lost because this e-mail has been sent to you by mistake. If you have received this transmission in error, please notify HSD on +61 3 9875 5900 immediately and destroy all copies of this e-mail. The contents of this email message may not be quoted, copied, reproduced or published in part or in whole, without the written authorisation of HSD.