Skip to content
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

Add support for GSSAPIAuthentication #81

Open
bbigras opened this issue Jan 31, 2017 · 5 comments
Open

Add support for GSSAPIAuthentication #81

bbigras opened this issue Jan 31, 2017 · 5 comments

Comments

@bbigras
Copy link

bbigras commented Jan 31, 2017

No description provided.

@artem-sidorenko
Copy link
Member

@BrunoQC thanks for raising an issue, can you maybe explain it a bit deeper?

@bbigras
Copy link
Author

bbigras commented Feb 2, 2017

I use GSSAPIAuthentication for password-less logins from computers on an Active Directory domain using Kerberos tokens.

@artem-sidorenko
Copy link
Member

artem-sidorenko commented Feb 2, 2017

@BrunoQC Hm, I still can not understand what should be done :\

ssh-baseline repo (this repo) contains the tests and test profile for ssh testing. Is some test for GSSAPIAuthentication missing?

@bbigras
Copy link
Author

bbigras commented Feb 2, 2017

I'm not sure if I'm in the right place.

I used https://galaxy.ansible.com/dev-sec/ssh-hardening/ , it replaces my ssh config and I don't know how to leave GSSAPIAuthentication yes in my config file.

I thought about asking on https://github.com/dev-sec/ansible-ssh-hardening but I was thinking that it may also be useful for chef and puppet.

@chris-rock
Copy link
Member

@BrunoQC Thank you for asking. This baseline is providing the recommendation. In this case: no as defined in https://github.com/dev-sec/ssh-baseline/blob/master/controls/sshd_spec.rb#L330-L337. Therefore the implementations in Chef/Ansible/Puppet set the default to no. In your case https://github.com/dev-sec/ansible-ssh-hardening Nevertheless all attributes should be adaptable. This is an issue for the ansible implementation, since the value is fixed in our ansible template. See https://github.com/dev-sec/ansible-ssh-hardening/blob/1f63b3522ac510fc0d2fadca0cc30a76de445ef3/templates/openssh.conf.j2#L122-L123
I recommend to open an issue or add a PR at https://github.com/dev-sec/ansible-ssh-hardening to provide the flexibility you're asking.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants