Protocols/OSCAR/SNAC/OSERVICE PROBE REQ: Difference between revisions
No edit summary |
No edit summary |
||
Line 117: | Line 117: | ||
</td></tr></table> | </td></tr></table> | ||
=== From Aleksandr Shutko: Client verification sequence === | |||
<table width=640 bgcolor=darkblue cellSpacing=0 cellPadding=0 border=0><tr><td> | |||
<table width=100% cellSpacing=2 cellPadding=0 border=0><tr><td bgcolor=#E9E9E9> | |||
<table width=100% cellSpacing=0 cellPadding=0 bgcolor="#4040FF" border=0> | |||
<tr> | |||
<td><b><font size=2 color="white"> <a name="verification"></a> Client verification sequence</font></b></td> | |||
</tr> | |||
</table> | |||
</td></tr> | |||
<tr><td bgcolor=#E9E9E9> | |||
<table width=100% cellSpacing=0 cellPadding=0 border=0> | |||
<tr><td colspan=3 height=5></td></tr> | |||
<tr><td width=5> </td> | |||
<td> | |||
| |||
This request used by AOL AIM server to recognize clone clients. The | |||
request contains eight bytes. The first four are an offset, the second | |||
four are a length.<br><br> | |||
| |||
When the client receives the request, it adds it to the current ds | |||
(0x00400000) and dereferences it, copying the data into a buffer which | |||
it then runs directly through the MD5 hasher. The 16 byte output of | |||
the hash is then sent back to the server.<br><br> | |||
<table width=100% cellSpacing=0 cellPadding=0 align=center border=0> | |||
<tr><td width=20></td> | |||
<td> | |||
<table width=580 bgcolor=darkblue cellSpacing=0 cellPadding=0 border=0><tr><td> | |||
<table width=100% cellSpacing=2 cellPadding=0 border=0><tr><td bgcolor=#7070D0><b><font size=2 color=white> Client verification</font></b></td></tr> | |||
<tr><td bgcolor=#E5E5E5> | |||
<table width=580 cellSpacing=1 cellPadding=1 border=0> | |||
<tr> | |||
<td bgcolor=#f9f9f9 width=35 valign=top> <b><<</b></td> | |||
<td bgcolor=#f9f9f9 width=200 valign=top> <b>[[Protocols/OSCAR/SNAC_01_1f|SNAC(01,1F)]]</b></td> | |||
<td bgcolor=#f9f9f9 valign=top> Server ack client for verification reply</td> | |||
</tr> | |||
<tr> | |||
<td bgcolor=#f9f9f9 valign=top> <b>>></b></td> | |||
<td bgcolor=#f9f9f9 valign=top> <b>[[Protocols/OSCAR/SNAC_01_20|SNAC(01,20)]]</b></td> | |||
<td bgcolor=#f9f9f9 valign=top> Client sends verification reply</td> | |||
</tr> | |||
</table> | |||
</td></tr></table> | |||
</td></tr></table> | |||
</td></tr></table> | |||
<br> | |||
</td><td width=15> | |||
</td></tr></table> | |||
</td></tr></table> | |||
</td></tr></table> | |||
=== OSERVICE SNACs === | === OSERVICE SNACs === |
Latest revision as of 11:59, 14 February 2021
OSCAR Protocol |
Introduction • Terms • Clients |
Basic |
Datatypes • FLAP • SNAC • TLV |
UUIDs • Errors • Tool IDs |
Host Interaction |
Rate Limits • Migration • Messages |
Other Services |
ADMIN • ADVERT • ALERT |
BART • BOS • BUCP • CHAT |
CHAT_NAV |
Tutorials |
Sign On • BART • Rendezvous |
ICBM • Locate • Buddies |
Foodgroups |
OSERVICE (0x0001) |
LOCATE (0x0002) |
BUDDY (0x0003) |
ICBM (0x0004) |
ADVERT (0x0005) |
INVITE (0x0006) |
ADMIN (0x0007) |
POPUP (0x0008) |
PD (0x0009) |
USER_LOOKUP (0x000A) |
STATS (0x000B) |
TRANSLATE (0x000C) |
CHAT_NAV (0x000D) |
CHAT (0x000E) |
ODIR (0x000F) |
BART (0x0010) |
FEEDBAG (0x0013) |
ICQ (0x0015) |
BUCP (0x0017) |
ALERT (0x0018) |
PLUGIN (0x0022) |
UNNAMED_FG_24 (0x0024) |
MDIR (0x0025) |
ARS (0x044A) |
ID | Origin | Name | Foodgroup | Service | Status | Version |
---|---|---|---|---|---|---|
0x0001, 0x001F | Host | OSERVICE__PROBE_REQ | Unspecified | All | Active | 4.0 |
Client verification request.
SNAC Header
Foodgroup | uint16 (word) | 00 01 |
Subgroup | uint16 (word) | 00 1F |
Flags | uint16 (word) | 00 00 |
Request ID | uint32 (dword) | 00 00 00 00 |
SNAC Data
Unconfirmed: This SNAC contains no data
From Aleksandr Shutko: SNAC(01,1F) server client verification command SNAC(01,1F) OSERVICE__PROBE_REQ
|
Example SNAC dump with flap header:
|
From Aleksandr Shutko: Client verification sequence
|
OSERVICE SNACs
|