Yes, come to think of it ... this is probably OpenSSL layer, so the client may not have control over this. Sorry for the noise. Al ________________________________________________ Albert L. Rossi Senior Software Developer Scientific Computing Division, Scientific Data Services, Distributed Data Development WH 566 Fermi National Accelerator Laboratory Batavia, IL 60510 (630) 840-3023 ________________________________ From: [log in to unmask] <[log in to unmask]> on behalf of Albert Rossi <[log in to unmask]> Sent: Monday, February 20, 2023 12:19 PM To: Oliver Freyermuth <[log in to unmask]>; Bockjoo Kim <[log in to unmask]>; Yujun Wu <[log in to unmask]>; Yujun Wu <[log in to unmask]>; xrootd-l <[log in to unmask]> Cc: David A Mason <[log in to unmask]>; Chih-Hao Huang <[log in to unmask]> Subject: Re: Help with hostname not in SAN extension TLS error Note that XrdSecGSITRUSTDNS is of course completely unrelated to host SANs. Yes, my idea was to bypass the SAN problem altogether. May not work though. -Al ________________________________ Use REPLY-ALL to reply to list To unsubscribe from the XROOTD-L list, click the following link: https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-L&A=1<https://urldefense.proofpoint.com/v2/url?u=https-3A__listserv.slac.stanford.edu_cgi-2Dbin_wa-3FSUBED1-3DXROOTD-2DL-26A-3D1&d=DwMFAw&c=gRgGjJ3BkIsb5y6s49QqsA&r=60rQ0HHqHmEY1P6VSdyuTQ&m=iNSk6gVcr4kH7mHJgWN9lSct9SAfRMtH20hbjHsRJkadvsGXHanc27Q0ZUwpB6ma&s=8IGlqRo1lLgdL9yKAkN9Yz1jj8elEalCWImqNK6PNlE&e=> ######################################################################## Use REPLY-ALL to reply to list To unsubscribe from the XROOTD-L list, click the following link: https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-L&A=1