- This topic has 3 replies, 3 voices, and was last updated 2 days, 5 hours ago by .
Viewing 4 posts - 1 through 4 (of 4 total)
Viewing 4 posts - 1 through 4 (of 4 total)
- You must be logged in to reply to this topic.
Home › Forums › FABRIC General Questions and Discussion › permission for Bastion Key “too open”
Hello I had to create a new bastion key. I generated one and downloaded it. When I try to remote access into one of the VMs in my newly created slice I get the following error.
Permissions 0644 for ‘/home/fabric/work/fabric_config/Nirmala’ are too open.
It is required that your private key files are NOT accessible by others.
This private key will be ignored.
Load key “/home/fabric/work/fabric_config/Nirmala”: bad permissions
nxsvks_0000031803@bastion.fabric-testbed.net: Permission denied (publickey,gssapi-keyex,gssapi-with-mic).
kex_exchange_identification: Connection closed by remote host
Connection closed by UNKNOWN port 65535
thanks
Nirmala
Hello Nirmala,
The permission has to be 600 for ssh private keys.
chmod 600 /home/fabric/work/fabric_config/Nirmala
Hi Nirmala,
Could you please change the permissions of the key as indicated in the error message using the command below via terminal in your JH container? This shall fix the issue.
chmod 600 /home/fabric/work/fabric_config/Nirmala
Thanks,
Komal
Thanks – that worked!