Bug 437070 - Samba patch
Summary: Samba patch
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: samba
Version: 5.1
Hardware: i386
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Simo Sorce
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-03-12 02:51 UTC by Dane Butler
Modified: 2009-05-22 02:18 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-05-22 02:18:54 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Dane Butler 2008-03-12 02:51:27 UTC 
Description of problem: After applying a samba patch on serveral RHEL5 
installations, samba could no longer reckonise Active Directory usernames 
and/or passwords. 

Version-Release number of selected component (if applicable):
3.0.25b-1.el4_6.2

How reproducible: Every tested installation so far


Steps to Reproduce:
1. Have a RHEL installation that includes Samba, connected to an AD domain
2. Patchc Samba
3. Attempt to connect using AD username and password
  
Actual results:
Authentication refused

Expected results:
Logs in with AD authentication (mapping AD users to local UNIX users)

Additional info:
Preformed rollback and problem was no longer present
Comment 1 Simo Sorce 2008-03-17 12:59:58 UTC 
The latest package for RHEL4 is samba-3.0.25b-1.el4_6.4 and includes several
fixes for a regression in a security update.
Can you check the probelm does not occur with this package ?
Comment 2 Dane Butler 2008-03-24 22:14:28 UTC 
I havent recieved 6.4 yet in my update list. Will test when arrived. Boxes 
grabbed the latest patches yesterday (24/3) and no sign of this package.
Comment 3 Simo Sorce 2009-05-21 20:43:31 UTC 
Any news on this bug?
It would be nice to know if you still can reproduce it with latest RHEL packages.
Comment 4 Dane Butler 2009-05-21 22:27:06 UTC 
No it looks like this issue has been rectified, thank you for your help
Note You need to log in before you can comment on or make changes to this bug.