List:Internals« Previous MessageNext Message »
From:Baron Schwartz Date:April 12 2009 2:55am
Subject:Client Authentication Packet w/ databasename
View as plain text  
According to
http://forge.mysql.com/wiki/MySQL_Internals_ClientServer_Protocol#Client_Authentication_Packet

If the client authentication packet includes the initial database, it
is preceded by a 0x00 filler byte.  What I'm seeing in tcpdump doesn't
seem to match that.  Here's what I see, with the packet header
omitted:

8da20300000000010800000000000000000000000000000000000000000000006d73616e64626f7800143e05bd06881b5c515a527f5228ccd1afe13ba6a86d7973716c00

Which as I see it, is 'msandbox'  (6d73616e64626f78) trying to connect
to 'mysql' database (6d7973716c00).  The scramble buffer is a
length-coded binary that precedes 'mysql', but there's no 0x00 byte in
between the scramble buffer and the database name as the wiki page
states.

It's a wiki; I feel like I should just fix it myself, but wanted to
check here first :)
Thread
Client Authentication Packet w/ databasenameBaron Schwartz12 Apr
  • Re: Client Authentication Packet w/ databasenameEric Day12 Apr
    • Re: Client Authentication Packet w/ databasenameBaron Schwartz12 Apr
      • Re: Client Authentication Packet w/ databasenameBaron Schwartz12 Apr
        • Re: Client Authentication Packet w/ databasenameEric Day12 Apr
          • Re: Client Authentication Packet w/ databasenameBaron Schwartz12 Apr
          • Re: Client Authentication Packet w/ databasenameBaron Schwartz12 Apr
            • Re: Client Authentication Packet w/ databasenameEric Bergen13 Apr
              • Re: Client Authentication Packet w/ databasenameKay Röpke14 Apr
                • Re: Client Authentication Packet w/ databasenameBaron Schwartz16 Apr
            • Re: Client Authentication Packet w/ databasenameKristian Nielsen13 Apr
            • Re: Client Authentication Packet w/ databasenameMichael Widenius13 Apr
  • Re: Client Authentication Packet w/ databasenameKonstantin Osipov13 Apr