>
> (plus do you want to give a hacker the ability to /kill you if they
> happen to get your username and password?)
>
they can only do that once.
after that, they changed the password, or you know your account is hacked and you
change it.
and anyway use a strong password
On Wednesday, Jun 11, 2003, at 12:09 Pacific/Auckland, Gavin Grieve
wrote:
On Wed, 2003-06-11 at 10:00, Tim Ramsey wrote:
Frederik Vervaet wrote:
Will be abused instantly. For example : users on a shared uni
network behind
NAT will have same [EMAIL PROTECTED] thus allowing them to collide other
On Wed, 2003-06-11 at 10:00, Tim Ramsey wrote:
> Frederik Vervaet wrote:
> > Will be abused instantly. For example : users on a shared uni network behind
> > NAT will have same [EMAIL PROTECTED] thus allowing them to collide others from
> > the same
> > network.
My thoughts are similar. At vari
Frederik Vervaet wrote:
Will be abused instantly. For example : users on a shared uni network behind
NAT will have same [EMAIL PROTECTED] thus allowing them to collide others from the
same
network.
What about allowing the user to lower the ping timeout setting on connect?
That seems a usable comp
- Original Message -
From: "Tim Ramsey" <[EMAIL PROTECTED]>
> Hiho,
>
> I'm currently having problems with my firewall which cause my IRC
> connections to be dropped at the client side. My nick remains on IRC
> until the server finally ping times me out. When I try to reconnect
> right
Hiho,
I'm currently having problems with my firewall which cause my IRC
connections to be dropped at the client side. My nick remains on IRC
until the server finally ping times me out. When I try to reconnect
right away, I have to choose a new, temporary nick until the old nick
drops off.
H
