Bug 443898 - PAM can not authenticate against blowfish hashes FutureFeature
Summary: PAM can not authenticate against blowfish hashes FutureFeature
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: pam
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Tomas Mraz
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-04-23 22:11 UTC by hoffer53
Modified: 2008-04-23 22:24 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-04-23 22:24:29 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description hoffer53 2008-04-23 22:11:14 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.14) Gecko/20080404 Firefox/2.0.0.14

Description of problem:
FutureFeature
It would be nice to include SUSE's pam_unix2 and libxcrypt into the Fedora distro in order to allow for easier transition from *BSD and also to allow for stronger password hashes.  The pam_unix2 plugin is backwards compatible with md5 and DES password hashes, so integration into a future version should not be too difficult.

The packages can be found in the current source distro of SUSE as well as here:
ftp://ftp.suse.com/pub/people/kukuk/libxcrypt/
ftp://ftp.suse.com/pub/people/kukuk/pam/pam_unix2
Make and install libxcrypt, then make and install pam_unix2.
Change all pam_unix.so occurrences in /etc/pam.d/* to read pam_unix2.so.

Version-Release number of selected component (if applicable):


How reproducible:
Always


Steps to Reproduce:
This is an enhancement.

Actual Results:


Expected Results:


Additional info:

Comment 1 Tomas Mraz 2008-04-23 22:24:29 UTC
We have already support for SHA256 and SHA512 password hashes which are strong
enough and I do not see any serious reason for having pam_unix2 in Fedora. Also
new packages get into Fedora this way:
http://fedoraproject.org/wiki/PackageMaintainers



Note You need to log in before you can comment on or make changes to this bug.