Re: [Coder-Com] suggestion of a WHOIS modification

2003-01-05 Thread The Storm Surfer
On Wed, Jan 01, 2003 at 02:28:53PM -0500, Alocin wrote: > About the *.user.undernet.org and the fact that it is nice to protect > yourself against attacks, it is also a pain for channel ops to find out who > is doing what and to find out to whom they should complain if they want to > inform an ISP

Re: [Coder-Com] suggestion of a WHOIS modification

2003-01-04 Thread Py Fivestones
Well I think this thread was answered satisfactorily (thanks) and we now how to educate users as to how to report abusive hidden hosts. Don't you love it when things work and when comments or concerns get rectified :P May we all have a happy and healthy new year. stoney` At 03:24 AM 1/3/2003 -0600

Re: [Coder-Com] suggestion of a WHOIS modification

2003-01-03 Thread Tom Scott
Not a bad idea @ all. - Necro stoney` wrote: Well technically since cservice issues usernames that allow users to mode +x, they need to be notified when there's credible evidence of abuse. Unfortunately, the only way to confirm abuse is by having an IRCop check user@hosts of clones and then r

Re: [Coder-Com] suggestion of a WHOIS modification

2003-01-03 Thread s gibinski
t identify the actual perpetrators. Sorry to be so long winded. -stephen From: stoney` <[EMAIL PROTECTED]> Subject: Re: [Coder-Com] suggestion of a WHOIS modification Date: Fri, 03 Jan 2003 00:18:58 -0500 Well technically since cservice issues usernames that allow users to mode +x, they need t

Re: [Coder-Com] suggestion of a WHOIS modification

2003-01-03 Thread Andrew Miller
Quoting stoney` <[EMAIL PROTECTED]>: > Well technically since cservice issues usernames that allow users to mode > +x, they need to be notified when there's credible evidence of abuse. > Unfortunately, the only way to confirm abuse is by having an IRCop check > user@hosts of clones and then report

Fwd: Re: [Coder-Com] suggestion of a WHOIS modification

2003-01-03 Thread Andrew Miller
-To: Andrew Miller [EMAIL PROTECTED] Subject: Re: [Coder-Com] suggestion of a WHOIS modification To: [EMAIL PROTECTED] Quoting stoney` [EMAIL PROTECTED]: > Well technically since cservice issues usernames that allow users to mode > +x, they need to be notified when there's credib

Re: [Coder-Com] suggestion of a WHOIS modification

2003-01-03 Thread plankie
Isn't it an idea to create a new or change an existing X-command for level 400 and up to find out the host-IP adress. I think of something like: Level <400: /msg x verify #holland plankie -X- [EMAIL PROTECTED] is logged in as plankie Level >400: /msg x verify #holland plankie -X- [EMAIL PROTECTED

Re: [Coder-Com] suggestion of a WHOIS modification

2003-01-03 Thread Larry Kaeto
From: "bas" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, January 03, 2003 5:41 AM Subject: Re: [Coder-Com] suggestion of a WHOIS modification > > You also give the perfect rpotection to pples wanting to do any illegal activities at all... > > > >

Re: [Coder-Com] suggestion of a WHOIS modification

2003-01-02 Thread stoney`
Well technically since cservice issues usernames that allow users to mode +x, they need to be notified when there's credible evidence of abuse. Unfortunately, the only way to confirm abuse is by having an IRCop check user@hosts of clones and then report it to cservice (messy isn't it). We curre

Re: [Coder-Com] suggestion of a WHOIS modification

2003-01-02 Thread Tom Scott
You mean like #support on GamesNET or #feds on QuakeNet? That kinda thing? Py Fivestones wrote: The question still remains: How can a user complain to a lamer's ISP? I think there's a need to have something in place to allow users to report abuse to ISPs. Currently the only thing a user can do

Re: [Coder-Com] suggestion of a WHOIS modification

2003-01-02 Thread Py Fivestones
The question still remains: How can a user complain to a lamer's ISP? I think there's a need to have something in place to allow users to report abuse to ISPs. Currently the only thing a user can do is email abuse@ (after the fact) or track down an IRCop who may or may not decide to join a chan

Re: [Coder-Com] suggestion of a WHOIS modification

2003-01-02 Thread Daniel Reed
On 2003-01-02T11:45-0500, [EMAIL PROTECTED] wrote: ) To the peoples who are suggesting that this would deprive sormal users ) of their protection, let remember some things: ) 1- It will always be a choice to join or not a channel. auto-join on ) invite are not an issue, this is a client matter. Wan

Re: [Coder-Com] suggestion of a WHOIS modification

2003-01-02 Thread Chris Crowther
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday 02 Jan 2003 4:56 pm, [EMAIL PROTECTED] wrote: > You also give the perfect rpotection to pples wanting to do any illegal > activities at all... That's a specious argument, if law enforcment want information, they'll just ask for i

Re: [Coder-Com] suggestion of a WHOIS modification

2003-01-02 Thread Fre
> You also give the perfect rpotection to pples wanting to do any illegal activities at all... So your fix would involve exposing everyone just to catch a little minority that is causing mayham ? I'm growing tired of this "hey illegal stuff happens so we should just get rid of any and all privacy

Re: [Coder-Com] suggestion of a WHOIS modification

2003-01-02 Thread bas
> You also give the perfect rpotection to pples wanting to do any illegal activities >at all... > > Regards, > > - Alocin if someone does something really bad, such as bringing 30 clones and flood, it can be against the net policy so the chanop who has logged everything can contact an IRCop, th

Re: [Coder-Com] suggestion of a WHOIS modification

2003-01-02 Thread alocin
> While I am sure there are users that abuse multiregistering to X > from a > single IP, there are also multiple users employing single IP's > in the many > household and small business LAN's utilizing various forms of > shared connections. > > I wonder if the loss of utility for these users might

Re: [Coder-Com] suggestion of a WHOIS modification

2003-01-02 Thread alocin
> The hidden +x host was created with a reason: To protect users > and Undernet > > staff. If I run a ddos/botchan, and an oper walks in to gline > them, or a cservice admin join and removes my X bot, I really > think I shouldn't be able > > to see his IP, even if I'm a chanop. > > Spike This is

Re: [Coder-Com] suggestion of a WHOIS modification

2003-01-02 Thread William Van Wyck
- Original Message - From: "Tom Scott" <[EMAIL PROTECTED]> To: "Alocin" <[EMAIL PROTECTED]> Cc: "Undernet Coder Comitee" <[EMAIL PROTECTED]> Sent: Thursday, January 02, 2003 4:30 AM Subject: Re: [Coder-Com] suggestion of a WHOIS modificati

Re: [Coder-Com] suggestion of a WHOIS modification

2003-01-02 Thread Jochen
The hidden +x host was created with a reason: To protect users and Undernet staff. If I run a ddos/botchan, and an oper walks in to gline them, or a cservice admin join and removes my X bot, I really think I shouldn't be able to see his IP, even if I'm a chanop. Spike Op woensdag 1 januari 2003

RE: [Coder-Com] suggestion of a WHOIS modification

2003-01-02 Thread Ivan Degiorgio
Sent: Thursday, January 02, 2003 3:07 PM To: Tom Scott Cc: [EMAIL PROTECTED] Subject: Re: [Coder-Com] suggestion of a WHOIS modification > But a channel op could be an attacker too! Also...if we're gonna stop > multiregistering we could possibly just say only 3-5 names per IP addres

Re: [Coder-Com] suggestion of a WHOIS modification

2003-01-02 Thread Tom Laermans
At 13:30 02-01-2003, you wrote: But a channel op could be an attacker too! Also...if we're gonna stop multiregistering we could possibly just say only 3-5 names per IP address. Also..Chanops could possibly talk to an IRCop and only the IRCop could find out the real hostmask..Chanops would never

Re: [Coder-Com] suggestion of a WHOIS modification

2003-01-02 Thread Fre
> But a channel op could be an attacker too! Also...if we're gonna stop > multiregistering we could possibly just say only 3-5 names per IP address. > > Also..Chanops could possibly talk to an IRCop and only the IRCop could > find out the real hostmask..Chanops would never know it. IRCops would go

Re: [Coder-Com] suggestion of a WHOIS modification

2003-01-02 Thread bas
> find out the real hostmask..Chanops would never know it. IRCops would go > into the channel, the Chanop would op him, and the IRCop would put the > ban on the flooder. > > - Necromncr exposing the real host to everyone in the channel.

Re: [Coder-Com] suggestion of a WHOIS modification

2003-01-02 Thread Chris Crowther
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday 02 Jan 2003 12:30 pm, Tom Scott wrote: > into the channel, the Chanop would op him, and the IRCop would put the > ban on the flooder. Opers have no place setting bans in a channel they're not usualy an OP in, and it's not somethi

Re: [Coder-Com] suggestion of a WHOIS modification

2003-01-02 Thread Tom Scott
But a channel op could be an attacker too! Also...if we're gonna stop multiregistering we could possibly just say only 3-5 names per IP address. Also..Chanops could possibly talk to an IRCop and only the IRCop could find out the real hostmask..Chanops would never know it. IRCops would go into t

Re: [Coder-Com] suggestion of a WHOIS modification

2003-01-01 Thread Daniel Reed
On 2003-01-01T14:28-0500, Alocin wrote: ) The fact that a person decide to join a channel is still his own choice, so ) it will not impact on the desire to protect a user privacy or security... If ) they join a channel they accept to obey by the rules of the channel and to ) allow acces to their tr