1
0
mirror of https://github.com/Yubico/yubico-pam.git synced 2025-02-20 21:54:16 +01:00

Explain how to generate an OTP.

This wasn't obvious to me and so I suspect others may be confused too.
This commit provides the documentation to close Issue 44, but is NOT
identical to the patch provided on that report.

http://code.google.com/p/yubico-pam/issues/detail?id=44
This commit is contained in:
Karl Goetz 2012-10-03 12:28:30 +10:00
parent d259f94dec
commit bb91c37b05

31
README
View File

@ -284,6 +284,37 @@ Enter your Yubikey OTP and convert it, your Yubikey token ID is 12 digits and li
Modhex encoded: XXXXXXX
Not sure what that last bit meant? Here is how to get a copy of your OTP.
Fast way
========
* Open a terminal
* Press yubikey button
It will output an OTP into the shell:
------
$ cccccccgklgcvnkcvnnegrnhgrjkhlkfhdkclfncvlgj
bash: cccccccgklgcvnkcvnnegrnhgrjkhlkfhdkclfncvlgj: command not found
------
This can be pasted into the Modhex_Calculator page.
Harder way
==========
This requires you to have the pam module enabled with 'debug' turned on. When
prompted for the yubikey press the button. The pam module will print out debug
information including the OTP and ID of your token to the shell - copy the ID
into your config file and you should be up and going.
------
Yubikey for `youruser':
[pam_yubico.c:pam_sm_authenticate(867)] conv returned 44 bytes
[pam_yubico.c:pam_sm_authenticate(885)] Skipping first 0 bytes. Length is 44, token_id set to 12 and token OTP always 32.
[pam_yubico.c:pam_sm_authenticate(892)] OTP: ccccccclabcabkhbdncicglfltnukadfoifadfhhhhfe ID: cccccclabcab
------
Yubico PAM module and SELinux.
------------------------------
Users with SELinux in enforcing mode (the default on Fedora 17+) may experience