Bug 175581 – pam_abl is completely busted on x86_64

Bug 175581 - pam_abl is completely busted on x86_64

Summary:	pam_abl is completely busted on x86_64

Status:	CLOSED INSUFFICIENT_DATA

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	pam_abl (Show other bugs)
Sub Component:
Version:	4
Hardware:	x86_64 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Alexander Dalloz
QA Contact:	Fedora Extras Quality Assurance
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2005-12-12 18:51 EST by Dan Hollis
Modified:	2008-03-09 21:31 EDT (History)
CC List:	2 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2008-03-09 21:31:49 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Dan Hollis 2005-12-12 18:51:20 EST

Description of problem:
pam_abl is completely busted on x86_64

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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
this is not a fedora bug, it's a pam_abl bug.
http://sourceforge.net/tracker/index.php?func=detail&aid=1325837&group_id=148927&atid=773100

i'm filing this in fedora so anyone wondering why pam_abl doesnt work on x86_64
will find the answer easily here.

maybe someone will read this bug and decide to fix it :)

Comment 1 Alexander Dalloz 2006-07-16 15:50:00 EDT

I would state WORKSFORME as testing on c86_64 did not give me a problem. As for
the referenced upstream report I leave the bug open as NEEDINFO.

Comment 2 petrosyan 2008-03-09 21:31:49 EDT

Fedora Core 4 is no longer maintained.

Setting status to "INSUFFICIENT_DATA". If you can reproduce this bug in the
current Fedora release, please reopen this bug and assign it to the
corresponding Fedora version.

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