SAMBA digest 1926

[Thomas Grossenbacher]

samba at samba.org schrieb:

>                             SAMBA Digest 1926
>
> For information on unsubscribing see http://samba.org/listproc/
> Topics covered in this issue include:
>
>   1) Three problems with Windows NT
>         by terminus at backinthe.ussr.net (Jeremy Malcolm)
>   2) Re: Encrypted passwords and OS2/Win95/Win98
>         by Benjamin Scott <bscott at hamptonsys.com>
>   3) Re: Encrypted passwords and OS2/Win95/Win98
>         by "Florian G. Pflug" <fgp at fgp.priv.at>
>   4) Samba 2.0.0 Beta5 released.
>         by Jeremy Allison <jallison at cthulhu.engr.sgi.com>
>
> ----------------------------------------------------------------------
>
> Date: Wed, 30 Dec 1998 16:57:13 +0800 (WST)
> From: terminus at backinthe.ussr.net (Jeremy Malcolm)
> To: samba at samba.org
> Subject: Three problems with Windows NT
> Message-ID: <m0zvHRJ-002LTQC at backinthe.ussr.net>
>
> I've just installed Samba with Red Hat Linux 5.2 and Windows NT Server 4.0
> (just a two-machine home network) and I've encountered three problems which
> I can't find answers to in the documentation or mailing list archive.
> Problems #1 and #3 are the biggies:
>
> 1. I copied two important files onto my NT box from my Linux box, then
>    deleted them from Linux.  Now as soon as I try to access them from NT,
>    NT tells me "Access to [filename] was denied".  Looking at the files,
>    they seem perfectly ordinary: permissions and attributes under NT are
>    all as normal.  It seems the files are corrupted when I copy them over
>    to the NT drive via Samba.  It is an NTFS drive, and I'm using file
>    compression.
>
> 2. Whenever I log on to my Windows NT box, it prompts me for the password
>    for the shares I have created to directories on the Linux box, even
>    though the username and password that I am logging on to in NT are the
>    same as those in Linux (admittedly I did have to change the password in
>    Linux for this to be the case).  The NT user is "Administrator", however
>    I've translated this to "root" on the Linux box.
>
> 3. Some of my Windows NT directories appear empty, even though they are not.
>    This is not just because they are invalid DOS names, because some of them
>    are valid DOS names, and similarly there are other directories that are
>    invalid DOS names that I can use with no problems.  For example when I
>    mount the c:/temp directory as /mnt/temp, I can't traverse below /temp
>    into its various subdirectories - they all wrongly appear to be empty.
>
> HELP!!!
>
> Thanks.
>
> --
> [ JEREMY MALCOLM  <Jeremy at Malcolm.ml.org>  http://www.malcolm.ml.org ]
> SIG of the day: [ ] Contact  [ ] Web  [x] PGP  [ ] Taglines #1  [ ] #2
> PGP key ID: 0xC3D89001 | Bits: 768 | Date: 1995/12/31 | Algorithm: RSA
> Fingerprint: 528643F595149476A9F310B13C471C25 | DSS key ID: 0xD2AB2220
> Obtain via finger, Web, or email with subject "Send RSA" or "Send DSS"
>
> ------------------------------
>
> Date: Wed, 30 Dec 1998 10:01:27 -0500 (EST)
> From: Benjamin Scott <bscott at hamptonsys.com>
> To: Steve Snyder <ssnyder at indy.net>
> Subject: Re: Encrypted passwords and OS2/Win95/Win98
> Message-ID: <Pine.LNX.4.05.9812300950170.2068-100000 at benden.hamptonsys.com>
>
> On Tue, 29 Dec 1998, Steve Snyder wrote:
> > If I reconfigure Samba to use encrypted passwords, won't that effectively
> > disabling logging into the shares from Win95 and OS/2?
>
>   I am not sure (have not tried), but I believe clients that do not support
> encrypted passwords will still connect to Samba without problems.  Problems
> occur with clients which insist on using encrypted passwords.
>
> > Is there a way to force Win98 to use plain-text passwords?
>
>   Yes.  In fact, somewhere on the Win98 CD, there is a registry patch (.REG
> file) that does just that.  It is buried under "Resource Kit" or something
> like that.
>
> > Is there a way to force Win95 and OS/2 to use encrypted passwords?
>
>   I do not believe the OS/2 client supports encrypted passwords at all.  I
> think some (maybe all) versions of Win95 do.  See ENCRYPTION.txt in the Samba
> docs directory for the gory details.  :)
>
> ----------------------------------------------------------------------
> Benjamin Scott <bscott at hamptonsys.com>          Phone: (603)431-7315
> Hampton Systems Group, Inc.                     Fax  : (603)431-0822
> http://www.hamptonsys.com                       DSN  : 852-3581
> ======================================================================
>
> ------------------------------
>
> Date: Wed, 30 Dec 1998 20:37:59 +0100
> From: "Florian G. Pflug" <fgp at fgp.priv.at>
> To: bscott at hamptonsys.com, Multiple recipients of list <samba at samba.org>
> Subject: Re: Encrypted passwords and OS2/Win95/Win98
> Message-ID: <19981230203759.A220 at fgp.priv.at>
>
> >   I am not sure (have not tried), but I believe clients that do not support
> > encrypted passwords will still connect to Samba without problems.  Problems
> > occur with clients which insist on using encrypted passwords.
> Hi .. I think, samba checks clear-text logins against /etc/passwd , and
> encrypted logins agains smbpasswd. It should be possible to have both at the
> same time, but your have to be carefull not to get your passwords out of
> sync (passswd chat, sync password, .. should help)
>
> >   I do not believe the OS/2 client supports encrypted passwords at all.  I
> > think some (maybe all) versions of Win95 do.  See ENCRYPTION.txt in the Samba
> > docs directory for the gory details.  :)
> win95(all versions), wfw3.11, nt(all version i think) support encrypted
> passwords - I'm not sure about os/s
>
>                                          greetings, Florian
>
> ------------------------------
>
> Date: Wed, 30 Dec 1998 18:01:48 -0800
> From: Jeremy Allison <jallison at cthulhu.engr.sgi.com>
> To: "samba-announce at samba.anu.edu.au" <samba-announce at samba.anu.edu.au>, "samba at samba.anu.edu.au" <samba at samba.anu.edu.au>,
> Subject: Samba 2.0.0 Beta5 released.
> Message-ID: <368ADB0C.4C7E2933 at engr.sgi.com>
>
> The Samba Team is pleased to announce Samba 2.0.0 Beta5
>
> This is the fifth of (hopefully) a short series of Beta
> releases of the 2.0.0 code and incorporates bug fixes and
> changes from feedback gained from the earlier betas.
>
> Show-stopper bugs notwithstanding, this is expected to be
> the last beta release before the official ship of the
> stable Samba 2.0.0 release, so it is very important for
> people to send feedback and patches for configuring and
> building Samba 2.0.0 on unusual platforms. We made this
> same announcement for Beta4, but due to the number of
> autoconf (and other) problems fixed since the release
> of Beta4 we thought it safer to release another Beta.
>
> We are relasing these Betas to enable the Samba Team to gain
> wider testing of the new autoconf mechanism and fix any
> bugs before the first ship of the new stable version of
> Samba - Samba 2.0.0.
>
> Samba 2.0.0 Beta5 is available in source form from
> samba.org and all of our mirror sites. Please go
> to your nearest mirror site from samba.org and
> click on the link under the "Samba News" announcement
> to download this code.
>
> Please try this code and give us feedback.
>
> If you have problems, or think you have found a bug please email
> a report to :
>
> samba-bugs at samba.org
>
> The WHATSNEW.txt file follows.
>
> As always, any bugs are our responsibility,
>
> Regards,
>
>         The Samba Team.
>
> -----------------------------------------------------------
>           Issues fixed between Beta4 and Beta5
>           ------------------------------------
>
> 1). Recuse directory bug with NT and smbtar fixed. smbtar now
>     recurses through all directories correctly.
> 2). Subtle bug fixed with the SIGCLD eating process status values
>     in cases where they are needed.
> 3). Fixed autoconf detection and handling of the different
>     setresuid/seteuid/setuid calls on different UNIXs.
> 4). Wrapped readdir64 for large file support.
> 5). Fixed --with-nisplus compile for Solaris.
> 6). Fixed wildcard bug with 16 bit clients. Also got closer
>     to NT wildcard semantics.
> 7). Allowed seek fails with EPIPE when doing client seeks to
>     allow Windows clients to communicate with UNIX processes via
>     fifo's (worked on 1.9.18, was broken in 2.0.0beta1-4).
> 8). Fixed compile bug with slow share mode code.
> 9). Fixes for QNX compiles.
> 10). Fixed recursion bug in nmbd if WINS server returns an
>      error at a bad time :-).
> 11). Log AFS auth fail.
> 12). Fixed Digital UNIX enhanced security problem with SWAT.
> 13). Updated SID generation code to produce NT compatible SIDs.
> 14). Fixed bug with ENOSPC on close() calls. This should now
>      be detected and returned to the client.
> 15). NT transact parameters weren't being zeroed out before use.
> 16). Fixed lockread bug where it was asking for a read-only
>      lock. It should be using a write lock (however strange this
>      seems :-).
> 17). Many SWAT printer fixes from Herb Lewis.
> 18). SWAT parameters now grouped in a more logical way.
> 19). Changed main smbd select loop to 60 seconds, smb.conf checks
>      to every 120 seconds to reduce load on large servers.
>
> -----------------------------------------------------------
>           Issues fixed between Beta3 and Beta4
>           ------------------------------------
>
> 1). More sanity checks in testparm code to help diagnose smb.conf
>     problems.
> 2). Ensure log header not written before log rotated.
> 3). Fix getrlimit number of file descriptors problem with AIX.
>     AIX supports the call but always returns infinity. This was
>     causing smbd to try and allocate a large amount of memory.
> 4). Fixed name lookup in lmhosts to match the documentation for
>     name type lookup.
> 5). Removed need to link password database code into nmbd.
> 6). Stop nmbd sending broadcast name refresh requests, use
>     permanent TTL on broadcast interfaces.
> 7). Flag "PRINTER" and "SHARE" parameters so SWAT can display
>     them correctly.
> 8). Fix SWAT so that it can display auto-generated printer list.
> 9). Added AFS and DCE auth includes back.
> 10). Added workaround to Windows NT redirector bug where it sends
>      64 bit lock requests to systems that don't support 64 bit offsets
>      (eg. Linux).
> 11). Fixed name mangling cache bug.
> 12). Fix smbpasswd bug where a missmatched password could be mis-interpreted
>      when adding a user.
> 13). Updates to SWAT to display "commit" button if user has write
>      access to smb.conf.
> 14). Fixed to autoconf for HPUX systems to work around broken
>      HPUX shadow.h include file.
>
> -----------------------------------------------------------
>           Issues fixed between Beta2 and Beta3
>           ------------------------------------
>
> 1). New parameters added :
>     "add user script"
>     "delete user script"
>     Designed to allow Samba servers to be set up with
>     no UNIX users and to allow them to create the needed
>     UNIX users on the fly. See the smb.conf documentation
>     for more details.
> 2). Autoconf issues including fixes for large file support for
>     Solaris and SINIX, and stat64 tests on SVR4 systems.
> 3). Code dealing with dos pathnames and native pathnames split
>     to be explicit about when Samba is accessing which type of
>     name.
> 4). Fix for missing PRINTCAP define under HPUX.
> 5). Added Samba specific strtoul().
> 6). Fix for reverse filename mapping with ISO8859-5 filenames.
> 7). Fix for nmbd not starting correctly sometimes due to pid
>     locking file.
> 8). Check for error returns in file descriptor limit checking code.
> 9). Kernel oplock code bugfix.
> 10). Restored client retarget code.
> 11). Fix for potential stack overflow in Digital UNIX crypt check.
> 12). Explicitly test for negative uids in smbpasswd file.
> 13). Fix for NT username in Domain logon code.
> 14). Patch from Scott Moomaw <scott at bridgewater.edu> to correctly
>      return "Invalid Info level" to Win95 printer clients.
> 15). Fix to allow NT printer clients to add printers (as 1.9.18
>      code would allow).
> 16). Fix to prevent ".." being used in servicename.
> 17). New SWAT icons.
>
> -----------------------------------------------------------
>
>           Issues fixed between Beta1 and Beta2
>           ------------------------------------
>
> 1). Many autoconf issues (too many to list here).
> 2). Correctly set default printing for AIX.
> 3). Attempt to fix struct rtentry not being defined problem.
> 4). Convert all open() style calls to wrappers for 64 bit systems.
> 5). Get more 'const' correct.
> 6). Fix bug with O_EXCL not being set on exlusive open requests.
> 7). Fix string_sub() problem with LinPopup.
> 8). Fix lmhosts bug causing only 3 character names to be looked up.
> 9). Fixed bug with NetBIOS pointers in scope names.
> 10). Removed code that was preventing NT3.51 PDC logons from working.
> 11). Fixed crash bug when processing DELETE_ON_CLOSE directive from MS Office.
> 12). Fixed NT4.x problems adding printer.
> 13). Stop multiple logs of NT ACL's not supported messages.
> 14). Changed 'security=server' mode to use *SMBSERVER name if
>      initial connect refused.
> 15). Fixed NT4.x problem with modify times not being preserved
>      on explorer file copy.
> 16). 'Silent' switch for testparm.
> 17). Added 'hosts allow/deny' checks to SWAT.
>
> -----------------------------------------------------------
>           WHATS NEW IN Samba 2.0.0 beta5
>           ==============================
>
> This is a MAJOR new release of Samba, the UNIX based SMB/CIFS file
> and print server for Windows systems.
>
> There have been many changes in Samba since the last major release,
> 1.9.18.  These have mainly been in the areas of performance and
> SMB protocol correctness.  In addition, a Web based GUI interface
> for configuring Samba has been added.
>
> In addition, Samba has been re-written to help portability to
> other POSIX-based systems, based on the GNU autoconf tool.
>
> Major changes in Samba 2.0
> --------------------------
>
> There are many major changes in Samba for version 2.0.  Here are
> some of them:
>
> =====================================================================
>
> 1). Speed
> ---------
>
> Samba has been benchmarked on high-end UNIX hardware as out-performing
> all other SMB/CIFS servers using the Ziff-Davis NetBench benchmark.
> Many changes to the code to optimise high-end performance have been made.
>
> 2). Correctness
> ---------------
>
> Samba now supports the Windows NT specific SMB requests.  This
> means that on platforms that are capable Samba now presents a
> 64 bit view of the filesystem to Windows NT clients and is
> capable of handling very large files.
>
> 3). Portability
> ---------------
>
> Samba is now self-configuring using GNU autoconf, removing
> the need for people installing Samba to have to hand configure
> Makefiles, as was needed in previous versions.
>
> You now configure Samba by running "./configure" then "make".  See
> docs/textdocs/UNIX_INSTALL.txt for details.
>
> 4). Web based GUI configuration
> -------------------------------
>
> Samba now comes with SWAT, a web based GUI config system.  See
> the swat man page for details on how to set it up.
>
> 5). Cross protocol data integrity
> ---------------------------------
>
> An open function interface has been defined to allow
> "opportunistic locks" (oplocks for short) granted by Samba
> to be seen by other UNIX processes.  This allows complete
> cross protocol (NFS and SMB) data integrety using Samba
> with platforms that support this feature.
>
> 6). Domain client capability
> ----------------------------
>
> Samba is now capable of using a Windows NT PDC for user
> authentication in exactly the same way that a Windows NT
> workstation does, i.e. it can be a member of a Domain.  See
> docs/textdocs/DOMAIN_MEMBER.txt for details.
>
> 7). Documentation Updates
> -------------------------
>
> All the reference parts of the Samba documentation (the
> manual pages) have been updated and converted to a document
> format that allows automatic generation of HTML, SGML, and
> text formats.  These documents now ship as standard in HTML
> and manpage format.
>
> =====================================================================
>
> NOTE - Some important option defaults changed
> ---------------------------------------------
>
> Several parameters have changed their default values.  The most
> important of these is that the default security mode is now user
> level security rather than share level security.
>
> This (incompatible) change was made to ease new Samba installs
> as user level security is easier to use for Windows 95/98 and
> Windows NT clients.
>
> ********IMPORTANT NOTE****************
>
> If you have no "security=" line in the [global] section of
> your current smb.conf and you update to Samba 2.0 you will
> need to add the line :
>
> security=share
>
> to get exactly the same behaviour with Samba 2.0 as you
> did with previous versions of Samba.
>
> ********END IMPORTANT NOTE*************
>
> In addition, Samba now defaults to case sensitivity options that
> match a Windows NT server precisely, that is, case insensitive
> but case preserving.
>
> The default format of the smbpasswd file has also been
> changed for this release, although the new tools will read
> and write the old format, for backwards compatibility.
>
> =====================================================================
>
> NOTE - Primary Domain Controller Functionality
> ----------------------------------------------
>
> This version of Samba contains code that correctly implements
> the undocumented Primary Domain Controller authentication
> protocols.  However, there is much more to being a Primary
> Domain Controller than serving Windows NT logon requests.
>
> A useful version of a Primary Domain Controller contains
> many remote procedure calls to do things like enumerate users,
> groups, and security information, only some of which Samba currently
> implements. In addition, there are outstanding (known) bugs with
> using Samba as a PDC in this release that the Samba Team are actively
> working on. For this reason we have chosen not to advertise and
> actively support Primary Domain Controller functionality with this
> release.
>
> This work is being done in the CVS (developer) versions of Samba,
> development of which continues at a fast pace.  If you are
> interested in participating in or helping with this development
> please join the Samba-NTDOM mailing list.  Details on joining
> are available at :
>
> http://samba.org/listproc/
>
> Details on obtaining CVS (developer) versions of Samba
> are available at:
>
> http://samba.org/cvs.html
>
> =====================================================================
>
> If you have problems, or think you have found a bug please email
> a report to :
>
>         samba-bugs at samba.org
>
> As always, all bugs are our responsibility.
>
> Regards,
>
>         The Samba Team.
>
> ------------------------------
>
> End of SAMBA Digest 1926
> ************************