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
Secrets not accessible with correct permissions, only via root #391
Comments
Does it work if you don't nest the secret?
vs the old permission:
|
Did it not nested via:
The path was a little different (3 instead of 1):
So basically the same permissions as before:
This yields the same result btw, files are inaccessible. |
I feel like this is probably the same thing I was reporting here in #381 ? |
Could it be the ownership/perms of your I'm also managing SSH keys with sops-nix. My issue today was that Does sops-nix allow to change ownership/perms of the chain of parent folders of a secret? I'm guessing no. Would a sensible default be "same as secret"? Cheers. |
Yeah, that's the case and exactly what the issue referenced above reported as well. |
Hey!
I'm currently having a very weird issue which causes some secrets to be impossible to read for my user. Particularly, I'm using
sops-nix
to provide my SSH private key. This used to work perfectly fine until some time ago, now I frequently can't authenticate with it due to being inaccessible.The solution has been to delete the symlink, copy the key from
/run/secrets/
viasudo
and then chowning it to my user.The given permissions in both
~/.ssh
and/run/secrets/
look just fine, so I'm not sure what is going on here:Another example:
The expression I use to provide the secret:
And the full flake, in case it helps. Thanks!
The text was updated successfully, but these errors were encountered: