Skip to content

Key permissions are too open: Set correct permissions - #6

Open
jantrienes wants to merge 1 commit into
debitoor:masterfrom
jantrienes:master
Open

Key permissions are too open: Set correct permissions#6
jantrienes wants to merge 1 commit into
debitoor:masterfrom
jantrienes:master

Conversation

@jantrienes

Copy link
Copy Markdown

I was trying to use the buildpack on scalingo, which also uses the same buildpack technology as Heroku. However, the application container has a different default umask than the containers on Heroku have.

Heroku:

> heroku run bash
~ $ umask   
0077

Scalingo:

> scalingo run bash
[11:19] Scalingo ~ $ umask
0022

Therefore, the permissions of the private ssh key file ~/.ssh/id_rsa are too open resulting into the following error during build:

       @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
       @         WARNING: UNPROTECTED PRIVATE KEY FILE!          @
       @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
       Permissions 0664 for '/app/.ssh/id_rsa' are too open.
       It is required that your private key files are NOT accessible by others.
       This private key will be ignored.
       bad permissions: ignore key: /app/.ssh/id_rsa

Fix:
Change the permissions of the ~/.ssh/id_rsa file after creation to 0600.

@thomasfedb

Copy link
Copy Markdown

This also affects Flynn. Could this be merged @debitoor?

@kbuilds

kbuilds commented Nov 13, 2017

Copy link
Copy Markdown

This also affects Dokku

@zyv

zyv commented Nov 26, 2017

Copy link
Copy Markdown

+1

@MistyBlunch

Copy link
Copy Markdown

try with this, it's worked for me:
chmod 400 ~/.ssh/grace_rsa
and then try yout connection

@Abhayy13

Copy link
Copy Markdown

its not working
same showing not accessible by others

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

Successfully merging this pull request may close these issues.

6 participants