Microsoft requires the SMB protocol to be changed ...

[Christopher R. Hertel]

Yeah, this is just a case of one coder deliberately constructing hex 
constants in poor taste.  The code is part of the HyperV code that Microsoft 
submitted under the GPL to the Linux kernel.  They didn't catch it, and it 
looks as though it took 3 years before a Linux kernel coder caught it.

On 07/20/2012 05:08 PM, Christopher R. Hertel wrote:
> The article states that the hex strings in question were magic constants
> used by their HyperV.  Nothing to do with SMB.
>
> Until I see news to the contrary, I won't blame Microsoft as a whole for
> this.  One coder making a dimwitted joke that no one at Microsoft caught
> because it's not really the kind of thing one goes looking to find.
>
> I think it is interesting, however, that it was caught by an Open Source
> coder.  I don't think this would be as likely to go unnoticed in an OSS kernel.
>
> Chris -)-----
>
> On 07/20/2012 04:46 PM, Richard Sharpe wrote:
>> As a result of an embarrassing disclosure
>> http://www.bbc.com/news/technology-18922629, Microsoft is now
>> rewriting the SMB protocol to prevent any occurrence on the wire of
>> the string 0x0B00B135.
>>
>

-- 
"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