Split the attribues to the client and server areas #150

Merged
merged 2 commits into from Dec 23, 2016

Conversation

Projects
None yet
3 participants
@artem-sidorenko
Member

artem-sidorenko commented Dec 22, 2016

Fixes GH-53

artem-sidorenko added some commits Dec 22, 2016

Cleanup the attribute handling in templates
and have it the same way:
 - only crypto related parameters are passed as template var
 - all other attributes are referenced directly via node obj from template
@coveralls

This comment has been minimized.

Show comment
Hide comment
@coveralls

coveralls Dec 22, 2016

Coverage Status

Coverage remained the same at 100.0% when pulling 6d929fd on artem-sidorenko:subnamespace into c1fbf18 on dev-sec:master.

Coverage Status

Coverage remained the same at 100.0% when pulling 6d929fd on artem-sidorenko:subnamespace into c1fbf18 on dev-sec:master.

@chris-rock

Awesome work @artem-sidorenko

@chris-rock chris-rock merged commit 04e0374 into dev-sec:master Dec 23, 2016

2 checks passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details
coverage/coveralls Coverage remained the same at 100.0%
Details

@artem-sidorenko artem-sidorenko deleted the artem-forks:subnamespace branch Dec 23, 2016

artem-sidorenko added a commit to artem-forks/chef-ssh-hardening that referenced this pull request Dec 23, 2016

Fix the broken master
Due to the parallel merge of GH-151 and GH-150

artem-sidorenko added a commit to artem-forks/chef-ssh-hardening that referenced this pull request Dec 23, 2016

Fix the broken master
Due to the parallel merge of GH-151 and GH-150

artem-sidorenko added a commit to artem-forks/chef-ssh-hardening that referenced this pull request Dec 23, 2016

Reflect changes of GH-150 and update the descriptions
in order to provide a better overview on defaults

artem-sidorenko added a commit to artem-forks/chef-ssh-hardening that referenced this pull request Dec 23, 2016

Reflect changes of GH-150 and update the descriptions
in order to provide a better overview on defaults
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment