Unfortunately, that page is very outdated.
E.g., version 5 of the ICQ protocol which is mentioned as new
on that page was used in ICQ99. It has since been abandoned in
ICQ2000 by the same protocol as AIM uses (if I am not mistaken).
Also, all specs of version 5 of the ICQ protocol that I have
seen so far are lacking a lot of the actual protocol (trust me,
I have written an ICQ server in perl using protocol version 5 ;)
Unfortunately, I never had the time nor interest to document the
protocol myself, but the server we wrote is GPLed so I can
provide it if anyone really is interested.
//Peter
> -----Original Message-----
> From: Dragos Ruiu [mailto:dr@xxxxxxxxxx]
> Sent: 22 August 2000 22:12
> To: Guy Harris; Jason Lewis
> Cc: ethereal-users@xxxxxxxx
> Subject: Re: [ethereal-users] Re: Request for a Plugin for ethereal
>
> I can save you some time with the ICQ protocol. There is a page
> dedicated to specifications of it at:
> http://www.d.kth.se/~d95-mih/icq/
>
> It's great stuff... kudos
> to the maintainers.
>
> cheers,
> --dr
>
> On Tue, 22 Aug 2000, Guy Harris wrote:
> > This should be sent to "ethereal-users@xxxxxxxx", not just to me;
> > Ethereal isn't *my* program, I'm just one of the developers, and not
> > even the person who originally created it (that's Gerald Combs).
> >
> > In any case:
> >
> > > I have thought up a new wish list feature for ethereal. With the
> > > newly added packet decoding features you have added (you
> rule!), it
> > > would be great to have a plugin that understood certain
> protocols and
> > > depending on what they are or the data the contain
> interact with the
> > > desktop in live action. For example, it would be nice to
> have a plugin
> > > called like LiveChat that decodes and displays all AIM
> (AOL Instant
> > > Messaging) that is going on on the line. It would show
> converstation to
> > > from etc. Perhaps show what users are viewing on the web for
> > > monitoring? Play that mp3 that someone is ftping across
> the line. I
> > > understand that each item would have to be setup
> indendently and alot of
> > > protocol knowledge would be needed? Could we try it for
> AIM though? It
> > > would be great fun. I am gonna start looking at the
> packet make-up
> > > tomorrow! I hope they don't encode the info! Knowing AOL, we are
> > > probably safe!!!
> --
> Dragos Ruiu <dr@xxxxxxxxxx> dursec.com ltd. / kyx.net -
> we're from the future
> pgp fingerprint: 18C7 E37C 2F94 E251 F18E B7DC 2B71 A73E D2E8 A56D
> pgp key: http://www.dursec.com/drkey.asc
>