 |
 |
Linking the client with OpenSSL 1.1 also lets it connect to the Alma9 server, so I am considering updating the spec file to do that from next release onwards.
(This may be more of a conversation for the ticket, not the PR but...)
If we're going to have to support OpenSSL 1.0.2, I think it's better to ship against 1.0.2. I'd worry about downstream folks who link against OpenSSL 1.0.2 on RHEL7: what's the implication of having both OpenSSL 1.0.2 and 1.1.1 inside the same process?
Therefore, I would propose we drop support for OpenSSL 1.0.2 for XRootD 6 and change to OpenSSL 1.1.1 then (even on RHEL7). Seems quite strange to have a major change in OpenSSL versions in a minor or patch release. At a major release boundary, I don't mind making the downstream plugins review their linking.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
Use REPLY-ALL to reply to list
To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1