svn commit: samba r12695 - in branches/SAMBA_4_0/source/scripting/libjs: .

[Christopher R. Hertel]

On Wed, Jan 04, 2006 at 05:32:34PM +0100, Jelmer Vernooij wrote:
> On Wed, Jan 04, 2006 at 05:26:15PM +0100, G?mes G?za wrote about 'Re: svn commit: samba r12695 - in?branches/SAMBA_4_0/source/scripting/libjs: .':
> > Jelmer Vernooij ?rta:
> > >>Jelmer Vernooij wrote:
> > >>>>Does windows allow such a name in 'system -> computer name'?
> > >>>Samba 3 allows it so it is necessary in some cases to have, in order
> > >>>to have a clean upgrade path.
> > >>  Is this something that can be detected and optionally corrected
> > >>in an upgrading script?
> > >Yes, it could be detected and corrected. However, we could only fix this
> > >on the server that is being upgraded - If it is a DC, its domain members
> > > will break because we can't fix the NetBIOS name remotely. If it is a
> > >domain member, it won't be able to access its domain later on.
> > Just my 2c:
> > The cleanest way would be to check for that kind of names before doing
> > any modification, and if any found drop an error message to the admin
> > explaining the phenomen and giving the steps she/he needs to perform
> > before a successfull migration and then exit.
> I don't think we should forbid dots in NetBIOS names at all - forcing
> users to change their NetBIOS domain name will require them to rejoin
> all their workstations and possibly change other things as well. I
> don't think allowing NetBIOS names will be that much work (if it would 
> require any specific work at all) to support in Samba4.

Jelmer's right.

Dots are completely legal in NetBIOS names.  Some Windows systems will 
disallow them or warn the user when they are entered, but there's no 
restriction on the wire.  They can, at best, be considered a hint that the 
name "might" be a DNS name.

The only octet that is supposedly disallowed in NetBIOS names is nul
(0x00).  That restriction goes back to an old IBM document that I don't
have (dangit).  Nul bytes can, however, be used in NetBIOS names.  The
most common & obvious situations are a nul suffix byte <00> and nuls as
padding.

I have not been able to reproduce it, but I did once see nuls in the name 
itself, probably as the result of a Unicode string being used without 
translation.

Chris -)-----

-- 
"Implementing CIFS - the Common Internet FileSystem" ISBN: 013047116X
Samba Team -- http://www.samba.org/     -)-----   Christopher R. Hertel
jCIFS Team -- http://jcifs.samba.org/   -)-----   ubiqx development, uninq.
ubiqx Team -- http://www.ubiqx.org/     -)-----   crh at ubiqx.mn.org
OnLineBook -- http://ubiqx.org/cifs/    -)-----   crh at ubiqx.org