XRootD prudently refuses to load insecure secrets. E.g. https://github.com/xrootd/xrootd/blob/1f80cbb0d1a5efc55b19215b72972e668616d6de/src/XrdSecztn/XrdSecProtocolztn.cc#L486-L488 But in containers, permission and ownership of files often does not follow the best practices for a standalone system, while still being (relatively) secure. Working around this requires additional plumbing: cronjobs and startup scripts to copy files and set permissions. Would you consider including an option (envvar?) to allow clients and servers to ignore strict permissions checks? -- Reply to this email directly or view it on GitHub: https://github.com/xrootd/xrootd/issues/1858 You are receiving this because you are subscribed to this thread. Message ID: <[log in to unmask]> ######################################################################## 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