Instead of getting another node you could run two instances on the same node and use a different port number. That should work.

Indeed, that also reproduces the issue :-).
Here's what I get with 5.0.1 using -d:3 for GSI:

200901 17:32:47 3034423 cryptossl_X509::CertType: certificate has 3 extensions
200901 17:32:47 3034423 cryptossl_X509::CertType: Found RFC 382{0,1}compliant proxyCertInfo extension
200901 17:32:47 3034423 crypto_X509Chain::EECname: EEC not found in chain

I'll install 4.12.4-RCx on the test node next and see if the issue also appears there.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/issues/1276#issuecomment-684943834", "url": "https://github.com/xrootd/xrootd/issues/1276#issuecomment-684943834", "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