-
Notifications
You must be signed in to change notification settings - Fork 49
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
UNPROTECTED PRIVATE KEY FILE! #67
Comments
This has really nothing todo with pac manager. If you set the correct permissions that ssh expects from the beginning Pac manager would not encounter this (this goes for any application using ssh with keys on the system. I don't think its a good idea that pac manager starts modifying permissions of files. |
An unprotected private key file should be considered compromised if there are more people on the machine that could have read the file. |
I created a new ssh connection with a pem private key file
I got error messages every time I tried to connect which did not specify the nature of the problem
Later I used ssh on my terminal and got this message:
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: UNPROTECTED PRIVATE KEY FILE! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
Permissions 0777 for 'Instance.pem' are too open.
It is required that your private key files are NOT accessible by others.
This private key will be ignored.
Load key "Instance.pem": bad permissions
Permission denied (publickey).
I ran 'chmod 400' on the file and the problem was solved, both on the terminal and in PAC manager
Maybe you should handle this case within the manager itself
The text was updated successfully, but these errors were encountered: