Red Hat Bugzilla – Full Text Bug Listing
|Summary:||SSHD Cannot authenticate YubiKey (SELinux prevents name_connect)|
|Product:||[Fedora] Fedora||Reporter:||Paul DeStefano <paul.destefano-redhat>|
|Component:||pam_yubico||Assignee:||Maxim Burgerhout <maxim>|
|Status:||CLOSED ERRATA||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Version:||17||CC:||dennis, maxim, nb|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2012-10-15 06:46:00 EDT||Type:||Bug|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
Description Paul DeStefano 2012-07-19 17:37:38 EDT
Description of problem: SSHD cannot authenticate YubiKeys. When SSHD tries pam_yubico.so, it fails (seemingly) due to SELinux preveting name_connect socket connection. (I think SELinux has denied this particular action by SSHD before, however, so it must be new in pam_yubico that this action is required because it worked fine in F15/F16, perhaps earlier.) Version-Release number of selected component (if applicable): pam_yubico-2.11-1.fc17.x86_64 How reproducible: Always. I cannot find a configuration that works. Steps to Reproduce: 1. Install pam_yubico.so 2. Configure /etc/pam.d/sshd 3. Try to login via ssh Actual results: Login fails, permission denied. /var/log/messages: ... setroubleshoot: SELinux is preventing /usr/sbin/sshd from name_connect access on the tcp_socket . For complete SELinux messages.... Expected results: Login should succeed according to PAM rules. Additional info:
Comment 1 Paul DeStefano 2012-08-21 12:37:47 EDT
Is there anything I can do to assist here?
Comment 2 Paul DeStefano 2012-09-06 23:06:59 EDT
Can someone at least tell me if this is an SSHD problem or a pam_yubico problem?
Comment 3 Maxim Burgerhout 2012-09-07 04:18:43 EDT
Sorry for the late response. The problem you describe is not with sshd or with pam_yubico, but with SELinux denying sshd to connect to the Yubico authentication servers. sshd is not usually allowed to initiate network connections. If you build this policy module, you get an SELinux boolean called ssh_can_network, that you can toggle to make things work again. You can download it from my fedorapeople site. The .te file is the source code for the module, the .pp file is a compiled, loadable module that you can use directly. I'll try to check with the SELinux people whether we can include this in the policy permanently, but that might take some time. The module I wrote is crude and overly simple, but it gets the job done for now.  http://fedorapeople.org/~wzzrd/841693/
Comment 4 Paul DeStefano 2012-09-08 19:26:35 EDT
No problem. You're policy looks like a great solution. Thank you for posting the module source. I'm using a nearly identical one, myself. I can understand if it takes some time to get this module added to the permanent policy; but I like the boolean option and I assume that makes it easier to get approved. Please post here if there are objections to the policy as I am interested in what security holes may be opened by this solution.
Comment 5 Maxim Burgerhout 2012-10-05 03:07:08 EDT
Status update This is fixed in Fedora's selinux-policy by this commit. This commit will create a 'authlogin_yubikey' boolean, that can be used to allow or disallow sshd_t (and several other types, like login_t) to name_connect to http_port_t. Big thanks to Dan Walsh. A new release of selinux-policy for Fedora 18 will be out soon. Fix expected in selinux-policy-3.11.1-33.fc18.noarch.  http://git.fedorahosted.org/cgit/selinux-policy.git/patch/?id=944db72223a1d4137ad8470a4ded38441f97ac24
Comment 6 Maxim Burgerhout 2012-10-15 06:46:00 EDT
The boolean 'authlogin_yubikey' was added to the SELinux policy for Fedora 18. Flip it to 'on' to enjoy Yubikey logins. I'm closing this bug now. Please reopen is problem reoccurs or persists.
Comment 7 Paul DeStefano 2012-10-15 12:25:59 EDT
This is great. I didn't expect this solution and I'm anxious to try it. But, can't this be released for F17?
Comment 8 Maxim Burgerhout 2012-10-15 13:54:40 EDT
I'm afraid not: implementing the boolean was quite a significant change in the SELinux policy. Backporting this to the policy for F17 would be a lot of work. I don't think that is going to happen, especially since there is a viable workaround. But then again, it's not up to me. I only co-maintain pam_yubico, not the SELinux policy :)
Comment 9 Paul DeStefano 2012-10-15 14:27:22 EDT
What's the workaround? Is there another bug where I can comment to the policy maintainers? This bug was introduced by the F17 policy pkg, so it seems clear that pkg needs to be updated with this patch. This was working in F15 and F16.