> This is the format of the 330 raw.
> 330: target handle handle is logged in as
Actually, it's ": 330:is logged in as"
> But I wondered... wouldn't it be more logic to put the second or third part
> of this format at the end of the return?
Nope. The present format was selected because it's
At 15:15 07/12/2002, you wrote:
Coders,
This is the format of the 330 raw.
330: target handle handle is logged in as
Actually it's more like nickname handle :is logged in as
: denotes the "last parameter" in irc protocol. It's logical to do it this
way, because it's machine-parsable.
But I w
Coders,
This is the format of the 330 raw.
330: target handle handle is logged in as
But I wondered... wouldn't it be more logic to put the second or third part
of this format at the end of the return? It's mostly the 330 raw that is
used for this kind of information on many networks. Strange eno
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> > I was whois'ing a friend that is connected to mesa.* and I observed that a
> > remote whois (/whois nick nick) was returning me a different username.
>
> I attempted to replicate this and was unable to do so. Do you have more
> examples of this
> I was whois'ing a friend that is connected to mesa.* and I observed that a
> remote whois (/whois nick nick) was returning me a different username.
I attempted to replicate this and was unable to do so. Do you have more
examples of this behavior?
--
Kevin L. Mitchell <[EMAIL PROTECTED]>
> At 23:34 13/10/2002, you wrote:
>> Before we get too carried away, this bug is on the server season`d is on,
>> not diemen.*, and it actually looks like someone has specifically hacked
>> mesa's code.
>
> i'd not worry for mesa* if i were you if its bugged
> it more than certain than its more t
At 23:34 13/10/2002, you wrote:
>Before we get too carried away, this bug is on the server season`d is on,
>not diemen.*, and it actually looks like someone has specifically hacked
>mesa's code.
i'd not worry for mesa* if i were you if its bugged
it more than certain than its more than just "hack
Whatever his reasons where he just rendered the server hiding code for
/whois useles. Atleast for clients on his server. Since it's the only one
behaving like this you can easily verify if someone is on that server.
/Gen
Before we get too carried away, this bug is on the server season`d is on,
not diemen.*, and it actually looks like someone has specifically hacked
mesa's code.
mesa.* is using u2.10.11.02 and I tested and confirmed this from elsene.*
which is also using u2.10.11.02 and doesn't have this bug.
See
hi there,
I was whois'ing a friend that is connected to mesa.* and I observed that a
remote whois (/whois nick nick) was returning me a different username.
[12:44] -> Server: whois season`d
Season`d is [EMAIL PROTECTED] * *** This space left empty. ***
Season`d using *.undernet.org The Undernet
10 matches
Mail list logo