[Coder-Com] gline uworld command doesn't require to be authed
Hello, I noticed an ircop can do /msg uworld gline ... with authed to uworld, but he can't remgline or anything as not authed. Is that a bug ? -- Chojin
[Coder-Com] new /whois line backwards?
Hi, Just been looking on amsterdam.nl.eu.undernet.org, and noticed the new ACCOUNT reply in the /whois, but it seems to be backwards. For example: Valcor is ~[EMAIL PROTECTED] Valcor is «Jonathan Angliss» Valcor on Amsterdam.NL.EU.undernet.org Valcor Valcor is logged in as Valcor on @#help-ops, @#help, @#canadian, @#greensward Valcor idle 0 s, signed on «Fri 12th Apr 2002 09:58a» That is the mirc result, and I know I'm running PnP with my mirc, so I thought it might be that, but I tried from BitchX at home, and got this result: ÚÄ---Ä--ÄÄ-ÄÄ---Ä--ÄÄ-Ä--- -- - | Valcor (~[EMAIL PROTECTED]) (unknown) ³ ircname : Jonathan Angliss | channels : @#help @#canadian @#greensward ³ server : *.undernet.org (The Undernet Underworld) ùíù Valcor Valcor is logged in as It seems the username is either in the wrong order, or the text is worded backwards... or is this just me? Just to make 100% sure it wasn't a script, I got somebody else that was using a non-scripted version of mirc to /whois me... Valcor is ~[EMAIL PROTECTED] * Jonathan Angliss Valcor on @#help @#canadian @#greensward Valcor using *.undernet.org The Undernet Underworld Valcor End of /WHOIS list. - Valcor Valcor is logged in as Am I seeing wrong? - Valcor
Re: [Coder-Com] new /whois line backwards?
At 17:04 12/04/2002, you wrote: >Hi, > >Just been looking on amsterdam.nl.eu.undernet.org, and noticed the new >ACCOUNT reply in the /whois, but it seems to be backwards. For >example: > > Valcor is ~[EMAIL PROTECTED] > Valcor is «Jonathan Angliss» > Valcor on Amsterdam.NL.EU.undernet.org > Valcor Valcor is logged in as > Valcor on @#help-ops, @#help, @#canadian, @#greensward > Valcor idle 0 s, signed on «Fri 12th Apr 2002 09:58a» Its not backwards. In the replies to a whois, the parameters are given first and the text/description is given last. This allows clients and server admins to change "is logged in as" to whatever they want, as the information needed is always in the first parameter, the rest just contains a description text. Its done the same way for idle and signon, the reply is: :server 317 source target (idletime) (signontime) :seconds idle, signon time -- - Lee H <[EMAIL PROTECTED]> // fl_ @ ircnet - - Any fool can criticize, condemn and complain, and most fools do. -- Benjamin Franklin
Re: [Coder-Com] new /whois line backwards?
> Just been looking on amsterdam.nl.eu.undernet.org, and noticed the new
> ACCOUNT reply in the /whois, but it seems to be backwards. For
> example:
The reply is actually technically:
:Amsterdam.NL.EU.undernet.org 330 Valcor Valcor Valcor :is logged in as
(Assuming you did the /whois on yourself, which should be the only way
you can get the type of response you saw.)
Now the first "Valcor" is simply the requestor's nickname. The second
one is the target of the /whois. The third is the account name. The
last argument is where it is intentionally. This order makes it easier
to parse the reply message for the username. This is also consistent
with other elements of the /whois reply: 313 ("is an IRC Operator")
and 317 (idle time and sign-on time). This allows another network
(say) to change the "is logged in as" portion of the reply without
messing up scripts.
Until the clients incorporate support for this numeric, it'll either
look a little funny, or you'll have to use a script to reorder the
reply for human ordering. I'm personally against reordering the reply
in the server code because of the benefits I've already mentioned...
--
Kevin L. Mitchell <[EMAIL PROTECTED]>
Re: [Coder-Com] new /whois line backwards?
Hi Kev,
That cleared it up... thanks... you'll have to excuse my knowledge...
I'm just starting to understand the code a little better, although not
a coder myself (at least not this language)... I'm starting to pick
more things up.
- Valcor
-Original Message-
From: Kev [mailto: [EMAIL PROTECTED]]
Sent: Friday, April 12, 2002
To: Valcor [mailto: [EMAIL PROTECTED]
Subject: [Coder-Com] new /whois line backwards?
--
>> Just been looking on amsterdam.nl.eu.undernet.org, and noticed the new
>> ACCOUNT reply in the /whois, but it seems to be backwards. For
>> example:
> The reply is actually technically:
> :Amsterdam.NL.EU.undernet.org 330 Valcor Valcor Valcor :is logged in as
> (Assuming you did the /whois on yourself, which should be the only way
> you can get the type of response you saw.)
> Now the first "Valcor" is simply the requestor's nickname. The second
> one is the target of the /whois. The third is the account name. The
> last argument is where it is intentionally. This order makes it easier
> to parse the reply message for the username. This is also consistent
> with other elements of the /whois reply: 313 ("is an IRC Operator")
> and 317 (idle time and sign-on time). This allows another network
> (say) to change the "is logged in as" portion of the reply without
> messing up scripts.
> Until the clients incorporate support for this numeric, it'll either
> look a little funny, or you'll have to use a script to reorder the
> reply for human ordering. I'm personally against reordering the reply
> in the server code because of the benefits I've already mentioned...
--End of Message--
Re: [Coder-Com] new /whois line backwards?
Yes, for future reference, you can easily sniff everything that mIRC sends to the server and gets back by doing: /debug on It's recorded to a file in your mirc directory, debug.log. Make sure to turn it off quickly though or you'll get a huge log building up. I've submitted this as a bug report to mIRC, as well as its lack of support for /userIP, numeric 307. It seems to just echo that back too. (BTW, does 2.10.11 with host hiding make it so /useip and /userhost doesn't work anymore in case the host is hidden?) Is Undernet routinely in touch with the authors of the major IRC clients to let them know of new support which must be added? -- James Evans aut viam inveniam aut faciam PGP? http://www.lehigh.edu/~jae7/pgpkey.txt
Re: [Coder-Com] new /whois line backwards?
> I've submitted this as a bug report to mIRC, as well as its lack of > support for /userIP, numeric 307. It seems to just echo that back too. Which, by the way, was changed--at Khaled's request, even. It's now 340. > (BTW, does 2.10.11 with host hiding make it so /useip and /userhost > doesn't work anymore in case the host is hidden?) Just changes the apparent IP to 127.0.0.1 and the apparent hostname to .users.undernet.org--the latter string is configurable via the features subsystem. -- Kevin L. Mitchell <[EMAIL PROTECTED]>
Re: [Coder-Com] new /whois line backwards?
Both the IP 127.0.0.1 and the users.undernet.org can be changed. Vampire just added HIDDEN_IP feature so you can change the ip (127.0.0.1) in conf. To change the users.undernet.org, just edit HIDDEN_HOST in your F-Lines (Feature Lines). Just changes the apparent IP to 127.0.0.1 and the apparent hostname to .users.undernet.org--the latter string is configurable via the features subsystem. ~reed UnderNet Spelling/Grammar Checker UnderNet Coder Committee Odd Guy Planetarion VirusFix Member/Helper/BotAdmin cyclebot Project Administrator
Re: [Coder-Com] new /whois line backwards?
begin quote from James Evans on Apr 12, 2002: > (BTW, does 2.10.11 with host hiding make it so /useip and /userhost > doesn't work anymore in case the host is hidden?) If you have a hidden host, /userhost just reports that one (like /whois) and /userip reports a configurable fake, defaulting to 127.0.0.1 :) -- Alex Badea * Undernet Coder-Com contributer
[Coder-Com] Sugestion..
today .. i helping user on #cservice .. and anyone stoled your password .. and then .. he go to "Forgotten Pass" to receive a "New Pass" .. then he received the pass .. more when he tried to login a username he get a error.. +- so "X- auth failed(max login is 1) i dont remember the msg sure" then because who stoled your username make login in seu username and seted the max logins 1. so he cant login to your username for change a pass, then we need a kill the people who using your username for he login again to your username .. so .." Think .. is have many peoples the same error? .. need kill all? " .. i think maybe is to creat a new command to X. One Example i Think :) - Disable or unlogin maybe. Unlogin could function so, who thus had the correct password in the X.. can so send one command to X and thus the X would cancel the Login of the person who was logged. would be good I thinks... :) just a suggestion .. MiTNiCk :) thanks.
