Permissions Are Too Open - Private Key Ignored

Follow

When Tunneling into and trying to log in on a remote host, you may get “Permissions are too open.” Setting permissions normally fixes that.

The problem is, that the private key you are using must remain private. If you permit others to read it, it's dangerous.  That condition must be satisfied before you can move forward.

After inputting:  ssh -L 8545:127.0.0.1:8545 -i blockdaemon.key blockdaemon@35.185.29.40

You will see something like this:

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: UNPROTECTED PRIVATE KEY FILE! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
Permissions 0644 for 'blockdaemon.key' are too open.
It is recommended that your private key files are NOT accessible by others.
This private key will be ignored.

 

The command:

ls -la blockdaemon.key 

will show that your key is accessible/readable by others.

-rw-r--r--

You'll need to change the permissions so only the owner can read and write the private key:

Chmod 600 blockdaemon.key

 Should do that for you. View again to check.

ls -la blockdaemon.key
-rw----

You're now ready to connect.

0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.