Re: [stunnel-users]

Geoff Thorpe wrote:
> FWIW, one possible problem is that engines are usually nothing more than
> conversion-glue to a vendor-provided library. So if the stack-abuse is
> occurring within the vendor code, you're hosed.

Please bear in mind that stunnel's GPL license exception only covers
OpenSSL and not any other GPL-incompatible code:
http://www.gnu.org/licenses/gpl-faq....compatibleLibs

I have just updated the license to clarify this issue:
"Linking stunnel statically or dynamically with other modules is making a
combined work based on stunnel. Thus, the terms and conditions of the GNU
General Public License cover the whole combination."

> Or is stunnel doing some kind of direct hacking for thread-setup?
> If so, I guess it would make sense for this to be modifiable at
> run-time (via environment variable or otherwise).

I'll add a configuration (stunnel.conf) option for this.

Best regards,
Mike

_______________________________________________
stunnel-users mailing list
stunnel-users@mirt.net
http://stunnel.mirt.net/mailman/listinfo/stunnel-users