-
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
CI, Harmonization of tests, Testing of Chef 13 and Chef 12 #176
Conversation
Red tests of opensuse leap should be fixed by dev-sec/ssh-baseline#88 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@artem-sidorenko i am fine with this.
@chris-rock your opinion?
.kitchen.dokken.yml
Outdated
- recipe[ssh-hardening] | ||
verifier: | ||
inspec_tests: | ||
- https://github.com/dev-sec/tests-ssh-hardening |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can you change the link to https://github.com/dev-sec/ssh-baseline
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
good catch, thanks! :)
.kitchen.yml
Outdated
@@ -78,3 +32,27 @@ suites: | |||
verifier: | |||
inspec_tests: | |||
- https://github.com/dev-sec/tests-ssh-hardening |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can you change the link to https://github.com/dev-sec/ssh-baseline
.kitchen.yml
Outdated
use_pam: false | ||
verifier: | ||
inspec_tests: | ||
- https://github.com/dev-sec/tests-ssh-hardening |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can you change the link to https://github.com/dev-sec/ssh-baseline
- Using vagrant for kitchen tests per default - Using dokken in the CI - Same travis configuration structure - Switch the tests to the latest available chef version Signed-off-by: Artem Sidorenko <artem@posteo.de>
Signed-off-by: Artem Sidorenko <artem@posteo.de>
Signed-off-by: Artem Sidorenko <artem@posteo.de>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you @artem-sidorenko for this improvement
@chris-rock @atomic111 I took a similar approach like in os-hardening,
.kitchen.yml
contains now vagrant setup and some parameters,.kitchen.dokken.yml
contains configs for dokken/docker.I had some problems with dokken: because of systemd thing, privileged container and some error the systemd of my host was influenced by the container process and broke. Since then I'm only using the vagrant way. I do not know your setups, but I hope this change is Okay. If not, let us discuss the alternatives
Fixes #174, #177