Re: [dev] [ii] exposed password on process monitoring

From: Ivan Kanakarakis <>
Date: Thu, 19 Apr 2012 23:54:45 +0300

Anyhow the correct way to connect to a server and
register/auth to the services is two different things.

you need PASS to connect to servers that need it
you need "/j nickserv identify .." to register/auth

no matter if popular servers seem to "merge" this
that's the way it should be, there're not interchangeable

so I guess PASS is not going away
and the delayed identify should also take place
(except again in cases like connecting to freenode,
that make this optional if you send PASS).
PASS should be handled by the client (ii)
identify is something the user is responsible for.

_AT_Strake thanks for the patch.
'ii -j file' works fine, though 'ii -j -' doesnt seem so

On 19 April 2012 23:27, Truls Becken <> wrote:

> On Thu, Apr 19, 2012 at 21:21, Kurt H Maier wrote:
> > PASS has nothing to do with nickserv.
> > nickserv has nothing to do with PASS.
> >
> > any server that uses data from the PASS string to do shit with nickserv
> > is doing that on its own.
> >
> > Why is this not filtering into anyone's skull?
> Because:
> 1) as you mentioned, some servers such as freenode auto-identify with
> nickserv if you send PASS
> 2) the most popular servers do not require PASS to connect
> So for the user they seem to have the same effect.
> Perhaps 2) is partly the reason they do 1), by the way.
> -Truls

*Ivan c00kiemon5ter V Kanakarakis*  >:3
Received on Thu Apr 19 2012 - 22:54:45 CEST

This archive was generated by hypermail 2.3.0 : Thu Apr 19 2012 - 23:00:08 CEST