Bug 872903

Summary: Request update to 2.12 (Released 2012-06-15)
Product: [Fedora] Fedora EPEL Reporter: Steven Haigh <netwiz>
Component: pam_yubicoAssignee: Dennis Gilmore <dennis>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: el6CC: dennis, maxim, nb
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-11-04 06:13:40 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Steven Haigh 2012-11-04 06:10:50 UTC 
Requesting an update of pam_yubico from 2.10 to 2.12.

Changes include:
* Version 2.12 (released 2012-06-15)

** Only use libyubikey when --with-cr is used.

** Set correct permissions on tempfile.

** YubiKey 2.2 contains a bug in challenge-response that makes it output the
same response to all challenges unless HMAC_LT64 is set. Add warnings to
ykpamcfg and a warning through conversate in the pam module. Keys programmed
like this should be reprogrammed with the HMAC_LT64 flag set.

* Version 2.11 (released 2012-02-10)

** Fix crash-bug with challenge-response mode when button press is required,
but button is never pressed. Reported and fixed by
Lingzhu Xiang <xianglingzhu>.

** Fix a memset() with wrong size as reported by clang, as well as some
other problems/warnings when building on Mac OS X, thanks to
Clemens Lang <neverpanic>.

** Add prefix-matching of LDAP fetched values, so you can store the
token-to-user mapping in a multi-value attribute with values like
"yubikey:publicid", "other-token:something" etc. Patch by
Remi Mollon <remi.mollon>. 


Source URL: http://code.google.com/p/yubico-pam/downloads/detail?name=pam_yubico-2.12.tar.gz
Comment 1 Steven Haigh 2012-11-04 06:13:40 UTC 
Error submitting to bugzilla caused this to go in twice. closing this as a dupe.

*** This bug has been marked as a duplicate of bug 872902 ***