Re: [Coder-Com] Idea. (HIGHLY RECOMMENDED)

2002-12-18 Thread peter green
one option is to use a * in the ip field so a server can link form anywhere then set a very strong password From: Kev <[EMAIL PROTECTED]> To: Philippe Roux <[EMAIL PROTECTED]> CC: [EMAIL PROTECTED] Subject: Re: [Coder-Com] Idea. (HIGHLY RECOMMENDED) Date: Tue, 17 Dec 2002 17:24:41 -0500 Received:

Re: [Coder-Com] Idea. (HIGHLY RECOMMENDED)

2002-12-18 Thread [EMAIL PROTECTED]
Security no-no. Bad idea. IMO At 10:18 AM 12/18/2002 +, peter green wrote: one option is to use a * in the ip field so a server can link form anywhere then set a very strong password From: Kev <[EMAIL PROTECTED]> To: Philippe Roux <[EMAIL PROTECTED]> CC: [EMAIL PROTECTED] Subject: Re: [Co

RE: [Coder-Com] Idea. (HIGHLY RECOMMENDED)

2002-12-18 Thread Tom Rons
> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]] On Behalf Of [EMAIL PROTECTED] > Sent: Wednesday, December 18, 2002 1:02 PM > To: [EMAIL PROTECTED] > Subject: Re: [Coder-Com] Idea. (HIGHLY RECOMMENDED) > > > Security no-no. Bad idea. IMO > > At 10:18 AM 12/

Re: [Coder-Com] Idea. (HIGHLY RECOMMENDED)

2002-12-18 Thread daaave
* "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> [2002-12-18 07:02:13 -0500]: > Security no-no. Bad idea. IMO "Security" is merely a tradeoff between locking things down and allowing functionality. :) With things the way they are, ircu's security is completely preventing the functionality, which (a

[Coder-Com] DCC

2002-12-18 Thread Curcan Ovidiu
I cannot send files via DCC... I know what you're going to say: check your mIRC settings, check your firewall rules. Did that already an not only once. Yesterday i decided to investigate it further. I turned mIRC's debugging on and typed this command: //.quote PRIVMSG $me : $+ $chr(1) $+ DCC CH

Re: [Coder-Com] Idea. (HIGHLY RECOMMENDED)

2002-12-18 Thread Kev
> one option is to use a * in the ip field so a server can link form anywhere > then set a very strong password We may not be EfNet, but we *are* Eris-free. -- Kevin L. Mitchell <[EMAIL PROTECTED]>

Re: [Coder-Com] DCC

2002-12-18 Thread Kev
> I know what you're going to say: check your mIRC settings, check your firewal > l rules. Did that already an not only once. Yesterday i decided to investigat > e it further. I turned mIRC's debugging on and typed this command: > > //.quote PRIVMSG $me : $+ $chr(1) $+ DCC CHAT chat 3245235969 666

Re: [Coder-Com] DCC

2002-12-18 Thread splidge
On Wed, Dec 18, 2002 at 09:53:20AM -0800, Curcan Ovidiu wrote: > As you can see bucharest.* CHANGED the IP and the port in the DCC request. > 1055353908 is my real IP (the IP bucharest.* knows me by), but mIRC > doesn't listen for incoming connections on that port This change is almost certainly

[Coder-Com] Fwd: [Cservice]

2002-12-18 Thread stoney`
Anyone care to field this one? stoney` From: "Dave..." <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Subject: [Cservice] Date: Wed, 18 Dec 2002 11:53:51 -0600 Organization: None, I'm a total slob! X-Mailer: Microsoft Outlook Express 6.00.2800.1106 Sender: [EMAIL PROTECTED] Reply-To: "Dave..." <[EMA

Re: [Coder-Com] Idea. (HIGHLY RECOMMENDED)

2002-12-18 Thread Tom Scott
lol Kev wrote: one option is to use a * in the ip field so a server can link form anywhere then set a very strong password We may not be EfNet, but we *are* Eris-free.

Re: [Coder-Com] DCC

2002-12-18 Thread evi|one
Yeap, you and splidge were right. It's my router's fault... - Original Message - From: Kev <[EMAIL PROTECTED]> Date: Wed, 18 Dec 2002 13:27:06 -0500 To: "Curcan Ovidiu" <[EMAIL PROTECTED]> Subject: Re: [Coder-Com] DCC > I know what you're going to say: check your mIRC settings, check you