samba - Oct 2004 - Impact of bnetd judgment on Samba?

Just wondering if the decisions in the bnetd case might affect Samba at 
all?

http://www.freedom-to-tinker.com/doc/2004/bnetd_30sep.pdf

 From my reading, the judge is claiming that because the bnetd authors 
didn't have permission to reverse engineer the Battle.Net protocol, 
they breached copyright by reverse engineering it. Apparently in the 
USA you can waive your legal rights through clickwrap licensing, and 
part of the EULA for various Blizzard games and Terms of Use for 
Battle.Net included language that forbade reverse engineering the 
network protocol.

Alex

"If knowledge can create problems, it is not through ignorance that we 
can solve them."  --Isaac Asimov

[localhost cifs]# mount -v -t cifs  //10.5.1.76/temp /tmp/tory -o user=user

Password:  parsing options: rw,user=tblue

mount.cifs kernel mount options
unc=//10.5.1.76\temp,ip=10.5.1.76,pass=pass,ver=1,rw,user=user 
mount error 22 = Invalid argument
Refer to the mount.cifs(8) manual page (e.g.man mount.cifs)

What is with mount.cifs making the unc path //x.x.x.x\???  <<--- should be
/
no?

Kernel Redhat 2.4.21-20
CIFS version both 1.02b and 1.20b (whatever the latest).

Mount cifs from samba 3.0 (since the samba CVS links are busted).

Any help with this

On Tuesday 05 October 2004 23:05, Alex Satrapa wrote:
> Just wondering if the decisions in the bnetd case might affect Samba at
> all?
>
The specs of the SMB protocol are public, so at least at present there's not
much anybody can do.  The real question (which only time will answer) is 
whether or not MS will insert new patented technology into a newer version of 
the protocol.  Nobody really knows, but given the need for backwards 
compatibility the existing protocol is likely to be supported for the 
forseeable future anyway.  So I wouldn't worry (yet).