Print

Print

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, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <xrootd/xrootd/issues/1858@github.com>

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