Bug 836620 – Don't use cached_login with pam_winbind for password stack

Bug 836620 - Don't use cached_login with pam_winbind for password stack

Summary:	Don't use cached_login with pam_winbind for password stack

Status:	CLOSED RAWHIDE

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	authconfig (Show other bugs)
Sub Component:
Version:	rawhide
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified
Target Milestone:	---
Target Release:	---
Assigned To:	Tomas Mraz
QA Contact:	Fedora Extras Quality Assurance
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2012-06-29 12:33 EDT by Stef Walter
Modified:	2012-08-15 10:47 EDT (History)
CC List:	1 user (show)

See Also:
Fixed In Version:	authconfig-6.2.3-1.fc18
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2012-08-15 08:02:34 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Patch which fixes the problem (458 bytes, patch) 2012-06-29 12:33 EDT, Stef Walter	no flags	Details \| Diff
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Stef Walter 2012-06-29 12:33:13 EDT

Created attachment 595337 [details]
Patch which fixes the problem

Description of problem:

authconfig adds 'cached_login' to the pam password stack. We shouldn't be using offline cached passwords when changing an AD password.

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

Latest hg

How reproducible:

Every time.

Steps to Reproduce:
1. authconfig --updateall --enablewinbind --enablewinbindauth
  
Actual results:

  password    sufficient    pam_winbind.so cached_login use_auth_tok

Expected results:

  password    sufficient    pam_winbind.so use_auth_tok

Comment 1 Stef Walter 2012-08-15 10:47:57 EDT

Confirmed that this fixed with authconfig-6.2.3

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