Patch info for sessid_bri

Author Comments

Stunnels up to version 3.8 failed to properly attempt to
select an SSL session ID before making the SSL connection,
thus no session ID reuse was possible.  This patch forces
stunnel in client mode to offer the most recent SSL session
ID (presumably the most recent used is the most valid) to
the remote SSL server in hopes that they can speed up the
SSL handshake.

Again, since an Stunnel client can only connect to one
SSL server, it always uses the most recently added SSL
session ID, which is the one most likely to still be
accepted (not timed out, etc) by the server.

This website makes patches available for use by the Internet community. However it does not endorse any of the patches contained herein. They could be work perfectly, or totally foul up everything. We don't know. Contact the authors if you have any questions. Use at your own risk.

The Stunnel software package does not contain any cryptography itself, however please remember that import and/or export of cryptographic software, code providing hooks to cryptographic algorithms, and discussion about cryptography is illegal in some countries. It is imperative for you to know your local laws governing cryptography. We're not liable for anything you do that violates your local laws.