IWETHEY v. 0.3.0 | TODO
1,095 registered users | 0 active users | 1 LpH | Statistics
Login | Create New User
IWETHEY Banner

Welcome to IWETHEY!

New How did they get on the Windows network?
Due to long hard work by the Samba team reverse engineering the secret protocols.

It's reported that, when Microsoft trains new network programmers, they use the Samba code, not their own. The Samba code is orderly and well commented while their own is a nearly uninterpretable mess.
[link|http://www.aaxnet.com|AAx]
New If that is true
then MS revealing its secrets won't help anyone as the problem is already solved

A
Play I Some Music w/ Papa Andy
Saturday 8 PM - 11 PM ET
All Night Rewind 11 PM - 5 PM
Reggae, African and Caribbean Music
[link|http://westcottradio.org|Tune In]
New Bozo
Reverse engineering is based on observation and experimentation.

There are many assumptions made. While it may work for the moment, in most circumstances, it is fragile and tends to breaks on MS updates. And then there is a mad scramble to figure out what happened and patch it, or use a different option, or simply do without.

I use SMBFS and CIFS to access windows servers from my Linux box via the mount command (not that I expect you to really understand what I just said). In certain circumstances, using certain a application, in certain ways, the files it generates gets corrupt.

It worked just fine when I first set it up, and then one day, the MS server got patched, and it stopped working.

I've given up since the general support consensus is no one really knows what to expect during the interaction. I generate the files locally and then copy them over to the final Windows share destination, which seems ot work. For now.

New No, the problem is not solved.
Samba is extremely good and well crafted but there are features of domain controllers and other enterprise level features that are unimplemented or unreliable in Samba because reverse engineering them has been extremely difficult.

Also, when Microsoft makes even niggling changes without revealing the specifications there is a fairly long delay before they can be implemented in Samba.

Of course one if the problems in reverse engineering is the band-aid and bailing wire approach Microsoft used to turn IBM's PCNet into Today's Microsoft Networking. It is not necessarily at all consistent.
[link|http://www.aaxnet.com|AAx]
Expand Edited by Andrew Grygus Sept. 18, 2007, 04:27:02 PM EDT
New EGADS NetBEUI!
--
[link|mailto:greg@gregfolkert.net|greg],
[link|http://www.iwethey.org/ed_curry|REMEMBER ED CURRY!] @ iwethey
PGP key: 1024D/B524687C 2003-08-05
Fingerprint: E1D3 E3D7 5850 957E FED0  2B3A ED66 6971 B524 687C
Alternate Fingerprint: 09F9 1102 9D74  E35B D841 56C5 6356 88C0
Alternate Fingerprint: 455F E104 22CA  29C4 933F 9505 2B79 2AB2
     EU Court rejects MS's appeal, upholds $613M fine. - (Another Scott) - (12)
         No... its ONLY for matters of *LAW*. - (folkert)
         Oh never mind - (bepatient) - (1)
             ;-) -NT - (Another Scott)
         Re: EU Court rejects MS's appeal, upholds $613M fine. - (andread) - (8)
             How did they get on the Windows network? - (Andrew Grygus) - (4)
                 If that is true - (andread) - (3)
                     Bozo - (crazy)
                     No, the problem is not solved. - (Andrew Grygus) - (1)
                         EGADS NetBEUI! -NT - (folkert)
             Not quite. - (Another Scott) - (2)
                 And the fines will keep growing - (bepatient) - (1)
                     And don't forget the exchange rate... -NT - (scoenye)

Those responsible have been sacked.
78 ms