Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better debug output if access/secret keys don't have correct permissions #12

Closed
jhiemstrawisc opened this issue Feb 13, 2024 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@jhiemstrawisc
Copy link
Member

While setting up an S3 origin in Pelican, I mistakenly set the permissions to a set of access/secret keys owned by root to 600. The plugin, running under user xrootd, did not make any noticeable errors that alerted me to the fact it couldn't read the keys.

@rw2 rw2 self-assigned this Feb 14, 2024
@jhiemstrawisc jhiemstrawisc added the bug Something isn't working label Mar 27, 2024
@rw2
Copy link
Collaborator

rw2 commented May 3, 2024

Fixed in: #34

@rw2 rw2 closed this as completed May 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants