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

Harmonize API #53

Closed
chris-rock opened this Issue Oct 14, 2014 · 1 comment

Comments

Projects
None yet
3 participants
@chris-rock
Member

chris-rock commented Oct 14, 2014

#49 introduced the separation of client and server config. this is not consistent across all configurations. We need to harmonize the interface while supporting a simple client and server config

@bkw

This comment has been minimized.

Show comment
Hide comment
@bkw

bkw Oct 14, 2014

Contributor

Do you mean moving all attributes that only affect the server into the ssh/server namespace?

Also: Does is make sense to split the ipv6-support into two as well? That seems to be the only attribute left that affects both client and server configs, but it also is shared with other hardening cookbooks, so splitting that might be a bit tricky..

Contributor

bkw commented Oct 14, 2014

Do you mean moving all attributes that only affect the server into the ssh/server namespace?

Also: Does is make sense to split the ipv6-support into two as well? That seems to be the only attribute left that affects both client and server configs, but it also is shared with other hardening cookbooks, so splitting that might be a bit tricky..

@artem-sidorenko artem-sidorenko added this to the v2.0.0 milestone Nov 8, 2016

artem-sidorenko added a commit to artem-forks/chef-ssh-hardening that referenced this issue Dec 22, 2016

@artem-sidorenko artem-sidorenko self-assigned this Dec 22, 2016

@chris-rock chris-rock closed this in #150 Dec 23, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment