Bug 608875

Summary: rebase to latest samba bugfix release (currently 3.5.4)
Product: Red Hat Enterprise Linux 6 Reporter: Guenther Deschner <gdeschner>
Component: sambaAssignee: Guenther Deschner <gdeschner>
Status: CLOSED CURRENTRELEASE QA Contact: Ales Zelinka <azelinka>
Severity: medium Docs Contact:
Priority: low    
Version: 6.0CC: atodorov, azelinka, dpal, gdeschner, syeghiay
Target Milestone: rcKeywords: Rebase
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: samba-3.5.4-65.el6 Doc Type: Rebase: Bug Fixes and Enhancements
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-11-10 16:33:20 EST Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Guenther Deschner 2010-06-28 15:47:23 EDT
Description of problem:

There are a couple of important fixes (and bugfixes for regressions) contained in the latest samba bugfix release.

Currently in RHEL6 is 3.5.2
3.5.4 brings the following important fixes:

- support for ntlmv2 authentication when using the kernel cifs client
- support for MS-DFS server side
- various printing related fixes

A more detailed list can be found here:
http://samba.org/samba/history/samba-3.5.3.html
http://samba.org/samba/history/samba-3.5.4.html
Comment 1 RHEL Product and Program Management 2010-06-28 16:03:01 EDT
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.
Comment 5 Alexander Todorov 2010-08-25 10:30:48 EDT
samba-3.5.4-66.el6 is in snap #12. Moving to VERIFIED.
Comment 7 releng-rhel@redhat.com 2010-11-10 16:33:20 EST
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.