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

[Christopher R. Hertel]

> > I still don't think we should allow a dot here.  It may be allowed by
> > crh's rules, but I think we are just asking for pain in Samba4 if we
> > allow it.

They are not my rules.  I'm only the messenger.

Any octet value may be encoded using the scheme in RFC1002.  There is a
rule against using nul bytes, but I have (once) seen nuls in a name.  I 
had to rewrite a chunk of my own testing code to deal with that name.  I 
wish I still had the capture.

There is also a rule against using the asterisk ('*') as the first octet,
but that rule is bent.  (That's why the *SMBSERVER name is never
registered.)

> > Does windows allow such a name in 'system -> computer name'?

If not, then the restriction is enforced at the application layer, not
further down in the stack where it matters.

I wound up writing my own nbt query tool a while back because nmblookup
would not allow me to do things I needed to do, such as query for a
mixed-case NetBIOS name.  Such names do exist in the wild, I'm afraid.
The program I wrote will throw a warning if there's a dot in a NetBIOS 
name, but it goes ahead and uses it anyway.

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