-
-
Notifications
You must be signed in to change notification settings - Fork 606
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use more secure sshd defaults #744
Merged
Conversation
This file contains 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
This was referenced Jan 30, 2017
This looks good to go. Needs changelog entry as well 👍 |
The TCP keepalive option enabled by TCPKeepAlive is spoofable.
Major thanks to @RiFi2k and @swalkinshaw for a ton of work and review! |
@fullyint thanks to you for getting it where it needed to be, I know you put in some hours on this. |
6 tasks
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.
Background
A discourse thread prompted #561, a call to create more secure sshd defaults. @RiFi2k implemented these improvements in #702 in a
ssh-hardening
branch that @fullyint augmented and PR-ed tomaster
in #716. Discussion in #716 determined that we should further modify our adaptation of the dev-sec/ansible-ssh-hardening role to match Trellis coding conventions. Many thanks to @RiFi2k and @swalkinshaw for their work preparing these modifications.In the end, whittling and modifying the dev-sec role ended up being more work and code change than if we'd simply adjusted our existing sshd role. In addition, the final modification of the dev-sec role still struck me as somewhat inorganic to the rest of Trellis (example of nearly final modification here).
This PR
This PR starts over with just our original sshd role, eliminates parts we don't need, then adds the minimum needed to achieve great security and excellent README guidance for users. It strikes me as more streamlined and suitable than #716.
This PR takes one logical step per commit, for easier review. Commits could be squashed on merge.
Sorry @RiFi2k that this didn't directly use and credit all your incredible work. I hope it's ok that I cherry-picked and added your "Remove insecure lines from moduli file" commit (with you as author).
Comparing with #716
Comments in #716 offered a diff of configs before vs. after #716. Here is how the final config of this PR differs from the final config of #716: