 |
 |
@abh3, would make sense announce this issue to a broader xrootd audience that people spread the message to their respective certification authorities? Basically everybody who tries to renew root CAs might run into similar "non-obvious mistake" and those using older clients than `v4.9.x` will suffer. Not sure what is turnaround this year about who is renewing root CA (can't rely just on info from certificate list we can parse as root CAs may change anytime if CA authorities decide) but surely it would be a longish run until CMSSW switch everything into `v4.9.x` series of xrootd client. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/xrootd/xrootd/issues/1110#issuecomment-576799641 ######################################################################## 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