Print

Print

We have an identical situation in xrootd. TLS can be required (i.e., STRICT) or optional (in xrootd it's required or optional by request category so a bit more complicated). The same issue arose when TLS was not required. We solved it by making TLS required the moment you enable any security protocol that requires the use of TLS; in this case ztn. Then, as you have noted, making it required avoids the whole issue.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <xrootd/xrootd/issues/1903/1424769929@github.com>

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/issues/1903#issuecomment-1424769929", "url": "https://github.com/xrootd/xrootd/issues/1903#issuecomment-1424769929", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

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