FreeTDS Development Group

[Brian Bruns <camber AT umcc.ais.org>]

Ok, after a brief look at the login packet for TDS 7.0 here's what I have
(I'm tired and going to bed so take this with a grain of salt). Stephan, I
need your input on what you set hostname/appname/password/and any other
settings to. Also does any of this change from run to run which would
indicate a time/pid/whatever field. So without further adieu...

TDS 7.0 Login Packet Layout

Everything is unknown unless stated otherwise. Send corrections/additions
to camber AT ais.org (Brian Bruns)

0:16            Okay, we have a new packet type 0x10 = 7.0 login packet ?
1:1             Last packet indicator, this is the final packet
2:0
3:204           Total length of packet including 8 byte header 
4:0
5:0
6:1
7:0
8:196           Length of payload
9:0             "
10:0
11:0
12:0
13:0
14:0
15:112 p
16:0
17:0
18:0
19:0
20:0
21:0
22:0
23:6
24:35 #
25:130
26:250          This stuff looks very bitwise much like TDS 5.0's capabilities
27:255          it's probably a capabilities negotiation of some sort
28:0            You might want to play with any options you can find
29:0            and see how it affects these bytes
30:0
31:0            Otherwise it's best to consider them magic for now
32:224
33:3
34:0
35:0
36:136
37:255
38:255
39:255
40:54 6     
41:4
42:0
43:0
44:86 V     Apparently these are in some order and this is null 
45:0
46:0
47:0
48:86 V     Position of username (relative to byte 8..ie after packet header)
49:0
50:2        Length of username (sa) in bytes not octets
51:0
52:90 Z     Apparently these are in some order and this is null 
53:0
54:0
55:0
56:90 Z    Position of app name (MS SQL Query Analyzer)
57:0
58:21      length of app name (in bytes not octets)
59:0
60:132     Position of ? (test) password perhaps?
61:0
62:4       length of ?
63:0
64:0       why the extra 4 bytes relative to the others?
65:0       if this is password (technically authorization field) then
66:0       this could be which scheme to use (guessing)
67:0
68:140    Position of lib name ? (ODBC)
69:0
70:4      length of lib name?
71:0
72:148    Position of ? (null)
73:0
74:0
75:0
76:148    Postion of ? (null)
77:0
78:0
79:0
80:0      we should assume that what follows is variable length  
81:64 @   and it runs until position 86 of the payload
82:51 3   but otherwise I have no idea.
83:154
84:107 k
85:80 P
86:148
87:0
88:48 0
89:0
90:196
91:0
92:0
93:0
94:115 s     Username (pos 86 relative to payload start...94-8=86)
95:0
96:97 a
97:0
98:77 M     App name (pos 90)
99:0
100:83 S
101:0
102:32  
103:0
104:83 S
105:0
106:81 Q
107:0
108:76 L
109:0
110:32  
111:0
112:81 Q
113:0
114:117 u
115:0
116:101 e
117:0
118:114 r
119:0
120:121 y
121:0
122:32  
123:0
124:65 A       
125:0
126:110 n
127:0
128:97 a
129:0
130:108 l
131:0
132:121 y
133:0
134:122 z
135:0
136:101 e
137:0
138:114 r
139:0
140:116 t      ? (pos 132)
141:0 
142:101 e
143:0
144:115 s
145:0
146:116 t
147:0
148:79 O      Library name?  (pos 140)
149:0
150:68 D
151:0
152:66 B
153:0
154:67 C
155:0
156:78 N     Do you know what this is?
157:84 T
158:76 L
159:77 M
160:83 S
161:83 S
162:80 P
163:0
164:1
165:0
166:0
167:0
168:6
169:130
170:0
171:0
172:0
173:0
174:0
175:0
176:0
177:0
178:0
179:0
180:0
181:0
182:0
183:0
184:0
185:0
186:0
187:0
188:0
189:0
190:0
191:0
192:48 0
193:0
194:0
195:0
196:0
197:0
198:0
199:0
200:48 0
201:0
202:0
203:0