Hello All,
It appears that stunnel still requires openssl and cannot use libressl.
Have the developers considered this patch: https://github.com/sabotage-linux/sabotage/commit/9b47cbbf3ce903dee042c45c81...
This is from stunnel 5.02 days but are there any issues with applying this with 5.14?
On 28 March 2015 at 16:54, jungle Boogie jungleboogie0@gmail.com wrote:
Have the developers considered this patch: https://github.com/sabotage-linux/sabotage/commit/9b47cbbf3ce903dee042c45c81...
Here's a patch for tlswrap with RAND_edg: https://github.com/Sp1l/ports/blob/master/security/tlswrap/files/patch-tls.c
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
jungle Boogie wrote:
On 28 March 2015 at 16:54, jungle Boogie jungleboogie0@gmail.com wrote:
Have the developers considered this patch: https://github.com/sabotage-linux/sabotage/commit/9b47cbbf3ce903dee042c45c81...
Here's a patch for tlswrap with RAND_edg: https://github.com/Sp1l/ports/blob/master/security/tlswrap/files/patch-tls.c
The
GPL 2.0 section 3 allows stunnel to be linked against GPL-incompatible libraries included with the operating system. This is the case for LibreSSL on the FreeBSD operating system.
Nevertheless, I don't support LibreSSL nor extend the OpenSSL GPL exception to allow distributing stunnel linked against LibreSSL for other operating systems.
Mike
-
jungle Boogie -
Michal Trojnara