This has been fixed in R5 but likely not the way you wanted. The client will now report the keyname and keyid that it used and the server will then search for the matching combination in its keytab. Mind you you have to select that option in the server-side config file using the --keyname option. We needed to do that because some sites came up with creative solutions so that the new way of resolving keyids might not work as expected. Yeah, it sort of sucks but backward compatibility, even when bad, is still the king.

—
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/590#issuecomment-606441237", "url": "https://github.com/xrootd/xrootd/issues/590#issuecomment-606441237", "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