-
Notifications
You must be signed in to change notification settings - Fork 70
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
Protocol 1 options while SSH 2 is hard coded #57
Comments
|
@rmoriz Good point, you found some skeletons in our closet ;) We'll remove it + update. Thank you! 👍 |
arlimus
added a commit
that referenced
this issue
Oct 27, 2014
In reference to feedback here: #57 Signed-off-by: Dominik Richter <[email protected]>
arlimus
added a commit
to dev-sec/puppet-ssh-hardening
that referenced
this issue
Oct 27, 2014
In reference to feedback here: dev-sec/chef-ssh-hardening#57 Signed-off-by: Dominik Richter <[email protected]>
arlimus
added a commit
to dev-sec/ssh-baseline
that referenced
this issue
Oct 27, 2014
In reference to feedback here: dev-sec/chef-ssh-hardening#57 Signed-off-by: Dominik Richter <[email protected]>
arlimus
added a commit
to dev-sec/ssh-baseline
that referenced
this issue
Oct 15, 2015
In reference to feedback here: dev-sec/chef-ssh-hardening#57 Signed-off-by: Dominik Richter <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
do we still need https://github.com/TelekomLabs/chef-ssh-hardening/blob/master/templates/default/opensshd.conf.erb#L84 ? Aren't they obsolete because sshd is by default configured to only accept protocol 2 connections?
The text was updated successfully, but these errors were encountered: