-
Notifications
You must be signed in to change notification settings - Fork 50
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
Create private key files with umask 177 #222
Comments
I suggest to update |
Looking at the issue, I noticed that the intention is
which means file permissions 600 and umask 177 (umask unsets the bits). |
You are absolutely right, @sechkova! Thanks for pointing this out. :) |
Fixed in #231 |
Description of issue or feature request:
Transfer of theupdateframework/python-tuf#279.
According to common practice (see e.g. ssh utilities) private key files should be created with read and write permissions for the user only (umask 177). Securesystemslib's
interface.generate_and_write_{rsa, ed25519, ecdsa}_keypair
functions should adopt that behavior.Current behavior:
Private key files are created with the OS' default umask.
Expected behavior:
Private keys files are created with umask 177.
The text was updated successfully, but these errors were encountered: