Key permissions are too open: Set correct permissions - #6
Open
jantrienes wants to merge 1 commit into
Open
Conversation
|
This also affects Flynn. Could this be merged @debitoor? |
|
This also affects Dokku |
|
+1 |
|
try with this, it's worked for me: |
|
its not working |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
umaskthan the containers on Heroku have.Heroku:
Scalingo:
Therefore, the permissions of the private ssh key file
~/.ssh/id_rsaare too open resulting into the following error during build:Fix:
Change the permissions of the
~/.ssh/id_rsafile after creation to 0600.