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

UNPROTECTED PRIVATE KEY FILE! #67

Open
pantos27 opened this issue Nov 22, 2017 · 2 comments
Open

UNPROTECTED PRIVATE KEY FILE! #67

pantos27 opened this issue Nov 22, 2017 · 2 comments

Comments

@pantos27
Copy link

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

@telefax
Copy link

telefax commented Jan 21, 2018

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.

@pinacoelho
Copy link

An unprotected private key file should be considered compromised if there are more people on the machine that could have read the file.
PAC should do nothing about it, so that you are forced to deal with it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants