This repository was archived by the owner on Jan 22, 2020. It is now read-only.
Open
Conversation
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
Like i was saying here in #1, it'd be nice if we could tighten up security somehow of the dockercloud nodes. AuthorizedKeys is nice, but it doesn't solve any of the security concerns with running nodes on dockercloud.
Whether we handle it here, or somewhere else?
Ideally we want to:
PasswordAuthentication no, would ban passwords for all users)PermitRootLogin no(The devops user can change to root when required after tunnelling.)What are your thoughts @fermayo? This may be out of the scope of
authorizedkeys, but these security issues regarding nodes are a concern to me when using tutum and dockercloud.