Bug 11085

Summary:	pam_mount's documentation still mentions invalid "use_first_pass" option
Product:	Mageia	Reporter:	Samuel Verschelde <stormi-mageia>
Component:	RPM Packages	Assignee:	Chris Denice <eatdirt>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	normal
Priority:	Normal
Version:	Cauldron
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Source RPM:	pam_mount	CVE:
Status comment:

Description Samuel Verschelde 2013-08-27 10:30:15 CEST

use_first_pass is no longer a valid option, see for example https://bugs.launchpad.net/ubuntu/+source/libpam-mount/+bug/332833

But our package still mentions it in the documentation:

$ ack use_first_pass -a
SOURCES/pam_mount-2.13/doc/faq.txt
42:        auth    sufficient  pam_ldap.so use_first_pass
57:    the first password entered by using the use_first_pass option.
59:    "use_first_pass", so be sure to check their documentation.

SOURCES/pam_mount-2.13/doc/pam_mount.txt
87:              auth    sufficient  pam_ldap.so use_first_pass
88:              auth    required    pam_unix.so use_first_pass
109:              auth [success=1 default=ignore] pam_ldap.so use_first_pass

SOURCES/pam_mount-2.13/doc/changelog.txt
360:- doc: remove old use_first_pass from doc

SOURCES/pam_mount-2.13/doc/pam_mount.8.in
85:auth    sufficient  pam_ldap.so use_first_pass
86:auth    required    pam_unix.so use_first_pass
108:auth [success=1 default=ignore] pam_ldap.so use_first_pass
[samuel.verschelde@tech009 pam_mount]$ vim SPECS/pam_mount.spec


Reproducible: 

Steps to Reproduce:

Comment 1 Chris Denice 2013-08-28 00:20:04 CEST

reported upstream:

https://sourceforge.net/p/pam-mount/bugs/110/

Comment 2 Samuel Verschelde 2013-09-02 15:40:21 CEST

I think my bug report (and so yours :)) might be invalid: use_first_pass is maybe still valid for pam_ldap.so and pam_unix.so, which are not part of pam_mount.

Comment 3 Chris Denice 2013-09-02 15:44:39 CEST

Possibly.
But based on the fact that all this has been triggered by very confusing docs and error messages in the output of pam_mount, I guess it was still deserving to be pointed.

Status: NEW => RESOLVED
Resolution: (none) => FIXED

Comment 4 Chris Denice 2013-09-02 15:45:29 CEST

oops, I ripped on the bug button, I propose WONTFIX instead and see what will happen upstream.

Resolution: FIXED => WONTFIX