FreeTDS Development Group

[Steve Langasek <vorlon AT netexpress.net>]

On Thu, Oct 10, 2002 at 10:53:04AM +0200, ZIGLIO Frediano wrote:

> > Thanks Steve.u right. 
> > I'm now using win2000 and SQL2000 Enterprise to get the trace. but not
> > every client login with this kind of packet, only a few do 
> > so. most of the
> > client login with the TDS V7 packet type. interesting? 
> > suprising? I have
> > checked all the server configurations, but no result.
> > Maybe this is V8 login packet, and use encode method.
> > I use user sa and null password to login, if u like, please 
> > let me konw
> > the packet structure. Thanks.

> I think only ms know the structure.

Some of us know part of the structure; it's documented in RFCs.  The
Samba Team knows a lot of the structure: Microsoft isn't really going to
make this stuff hard to decipher at the expense of their own ability to
maintain their operating system ;), so there's a lot of commonality
between the various MS-designed protocols.

It's just a matter of putting all of that together.

> However as state first two data exchange seem a capability report (supported
> in mssql2k), second exchange contain a certificate (this is the reason of
> ldap, also you can note that is not coded in ucs2). Other 2 exchange should
> contain password and the challenge (crypted)...

> At this point anyone know the exchange of data for SSL or other protocol
> that use certificates ?

Probably GSSAPI, not SSL.  SSL certs wouldn't make sense: the actual
query data is being sent in plaintext, so it's not using SSL encryption;
and SSL is not part of the Active Directory (Win2K LDAP) infrastructure,
whereas GSSAPI is.

Steve Langasek
postmodern programmer

Attachment: pgpwwuOjFSF6v.pgp
Description: PGP signature