From 5003f3974d2b57985cd453e0f8547ac495a6305d Mon Sep 17 00:00:00 2001 From: Andy Neff Date: Wed, 15 Nov 2017 15:46:46 -0500 Subject: [PATCH] Update Yubikey_and_SELinux_on_Fedora_18_and_up.adoc Added a quick explanation for what to do when you are using your own server that uses a custom port --- doc/Yubikey_and_SELinux_on_Fedora_18_and_up.adoc | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/doc/Yubikey_and_SELinux_on_Fedora_18_and_up.adoc b/doc/Yubikey_and_SELinux_on_Fedora_18_and_up.adoc index 7a277d6..ff3be7f 100644 --- a/doc/Yubikey_and_SELinux_on_Fedora_18_and_up.adoc +++ b/doc/Yubikey_and_SELinux_on_Fedora_18_and_up.adoc @@ -5,3 +5,7 @@ Based on a https://bugzilla.redhat.com/show_bug.cgi?id=841693[bugreport] in Red To make a long story short, if you want to use a Yubikey on a system running Fedora 18 or higher (and probably RHEL7, eventually), you'll need to toggle the 'authlogin_yubikey' SELinux boolean, like so: setsebool -P authlogin_yubikey 1 + +If you are using your own server via `urllist`/`url` in the pam conf file and using a non-standard http port, you will need to add that port to the `http_port_t` port list. For example, port `12345`: + + semanage port -a -t http_port_t -p tcp 12345