[SCM] Samba Shared Repository - branch master updated

Karolin Seeger kseeger at samba.org
Fri Jul 16 02:03:23 MDT 2010


The branch, master has been updated
       via  8b1980c... WHATSNEW: Start 3.6.0pre1 release notes.
      from  5f8678f... libcli/netlogon: re-enable debugging.

http://gitweb.samba.org/?p=samba.git;a=shortlog;h=master


- Log -----------------------------------------------------------------
commit 8b1980c22cd68f19ae47dee844963ae74b896e00
Author: Karolin Seeger <kseeger at samba.org>
Date:   Fri Jul 16 10:02:39 2010 +0200

    WHATSNEW: Start 3.6.0pre1 release notes.
    
    Karolin

-----------------------------------------------------------------------

Summary of changes:
 WHATSNEW.txt |   59 +++++++++++++++++++++++++++++++++++----------------------
 1 files changed, 36 insertions(+), 23 deletions(-)


Changeset truncated at 500 lines:

diff --git a/WHATSNEW.txt b/WHATSNEW.txt
index 066f718..ea134d0 100644
--- a/WHATSNEW.txt
+++ b/WHATSNEW.txt
@@ -1,36 +1,49 @@
                    =================================
-                   Release Notes for Samba 3.4.0pre1
-
+                   Release Notes for Samba 3.6.0pre1
+			     July 28, 2010
                    =================================
 
-This is the first preview release of Samba 3.4.  This is *not*
+
+This is the first preview release of Samba 3.6.  This is *not*
 intended for production environments and is designed for testing
 purposes only.  Please report any defects via the Samba bug reporting
 system at https://bugzilla.samba.org/.
 
-Major enhancements in Samba 3.4.0 include:
 
-Authentication Changes:
-o Changed the way smbd handles untrusted domain names given during user
-  authentication
+Major enhancements in Samba 3.6.0 include:
+
+
+SMB2 support
+------------
+
+
+Internal Winbind passdb changes
+-------------------------------
+
+Winbind has been changed to use the internal samr and lsa rpc pipe to get
+local user and group information instead of calling passdb functions. The
+reason is to use more of our infrastructure and test this infrastructure by
+using it. With this approach more code in Winbind is shared.
+
+
+######################################################################
+Changes
+#######
+
+smb.conf changes
+----------------
 
-Authentication Changes
-======================
+   Parameter Name                      Description     Default
+   --------------                      -----------     -------
 
-Previously, when Samba was a domain member and a client was connecting using an
-untrusted domain name, such as BOGUS\user smbd would remap the untrusted
-domain to the primary domain smbd was a member of and attempt authentication
-using that DOMAIN\user name.  This differed from how a Windows member server
-would behave.  Now, smbd will replace the BOGUS name with it's SAM name.  In
-the case where smbd is acting as a PDC this will be DOMAIN\user.  In the case
-where smbd is acting as a domain member server this will be WORKSTATION\user.
-Thus, smbd will never assume that an incoming user name which is not qualified
-with the same primary domain, is part of smbd's primary domain.
+   log writeable files on exit	       New	       No
+   ctdb locktime warn threshold	       New	       0
+   smb2 max read		       New	       1048576
+   smb2 max write		       New	       1048576
+   smb2 max trans		       New	       1048576
+   username map cache time	       New	       0
+   async smb echo handler	       New	       No
 
-While this behavior matches Windows, it may break some workflows which depended
-on smbd to always pass through bogus names to the DC for verification.  A new
-parameter "map untrusted to domain" can be enabled to revert to the legacy
-behavior.
 
 ######################################################################
 Reporting bugs & Development Discussion
@@ -42,7 +55,7 @@ joining the #samba-technical IRC channel on irc.freenode.net.
 If you do report problems then please try to send high quality
 feedback. If you don't provide vital information to help us track down
 the problem then you will probably be ignored.  All bug reports should
-be filed under the Samba 3.4 product in the project's Bugzilla
+be filed under the Samba 3.6 product in the project's Bugzilla
 database (https://bugzilla.samba.org/).
 
 


-- 
Samba Shared Repository


More information about the samba-cvs mailing list