#31 bump stunnel to 5.60 (or newer)
Closed: Completed 6 months ago by asvetter. Opened 2 years ago by asvetter.

New features according to website:
5.60 New features:
- New 'sessionResume' service-level option to allow
or disallow session resumption
- Added support for the new SSL_set_options() values.
- Download fresh ca-certs.pem for each new release.
5.59 New features:
- Client-side "protocol = ldap" support (thx to Bart Dopheide and Seth Grover).
5.58 New features:
- New 'protocolHeader' service-level option to insert custom 'connect' protocol negotiation headers. This feature can be used to impersonate other software (e.g. web browsers).
- 'protocolHost' can also be used to control the client SMTP protocol negotiation HELO/EHLO value.
- Initial FIPS 3.0 support.

stunnel is only required by uucp. So a version bump should not be very risky.


Metadata Update from @lkocman:
- Issue assigned to lkocman
- Issue tagged with: SLE

2 years ago

Metadata Update from @lkocman:
- Custom field SUSE Jira adjusted to https://jira.suse.com/browse/OPENSUSE-51

2 years ago

Is it possible to change this issue to "bump to stunnel 5.60+"? Or how is the intended use of the issues?
I just submitted 5.60 to factory.

5.60 accepted to Factory. Should I submit to Leap, or will this be done by SUSE, if approved?

So somebody needs to do the submission. If you have capacity to do so, then please do. You should reference jsc#SLE-20679 which is the internal jira id.

We're have opened a request to avoid internal references, however it will take some time until it's implemented.

5.62 ended up in Leap 15.4

Metadata Update from @asvetter:
- Issue close_status updated to: Completed
- Issue status updated to: Closed (was: Open)

6 months ago

Login to comment on this ticket.

Metadata