Print

Print

It is the responsibility of the application to verify that the admin has kept the file secure.

The application is limited to only seeing the owner and mode of the file on the local filesystem, which is a small subset of all that encompasses keeping the keytab secure. In our environment the mode 0440 root:daemon is correct and secure.
How can we indicate this to xrootd and prevent it from making incorrect assumptions about the environment it is operating it? Perhaps a non-default command-line option could be implemented, to change the error to a warning and not terminate?

—
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/1982/1490988961@github.com>

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