rooty/yubico-pam
1
0
Fork 0
mirror of https://github.com/Yubico/yubico-pam.git synced 2025-01-20 01:52:17 +01:00
Code Issues Projects Releases Wiki Activity

Update Yubikey_and_SELinux_on_Fedora_18_and_up.adoc

Browse Source 
Added a quick explanation for what to do when you are using your own server that uses a custom port
This commit is contained in:
Andy Neff 2017-11-15 15:46:46 -05:00 committed by GitHub
parent 9a674273e4
commit 5003f3974d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/Yubikey_and_SELinux_on_Fedora_18_and_up.adoc
View File

@ -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: 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 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