Thread: CVS Commit by dpage: Updated todo.

CVS Commit by dpage: Updated todo.

From
cvs@cvs.pgadmin.org
Date:
Log Message:
-----------
Updated todo.

Modified Files:
--------------
    pgadmin3:
        CHANGELOG.txt (r1.133 -> r1.134)


Attachment

Re: CVS Commit by dpage: Updated todo.

From
Andreas Pflug
Date:
cvs@cvs.pgadmin.org wrote:

> +    <li>2004-09-16 DP  1.2B2 mask passwords on dlgServer [Ivan Nejgebauer]

This comes up every half year or so.
I don't see too much sense in this todo, esp. since there's no viable
way to implement it without trying to recode the backend's password
encryption (what we certainly won't do)

Regards,
Andreas

Re: CVS Commit by dpage: Updated todo.

From
"Dave Page"
Date:

> -----Original Message-----
> From: Andreas Pflug [mailto:pgadmin@pse-consulting.de]
> Sent: 16 September 2004 11:16
> To: pgadmin-hackers@postgresql.org; Ivan Nejgebauer; Dave Page
> Subject: Re: [pgadmin-hackers] CVS Commit by dpage: Updated todo.
>
> cvs@cvs.pgadmin.org wrote:
>
> > +    <li>2004-09-16 DP  1.2B2 mask passwords on dlgServer [Ivan
> > + Nejgebauer]
>
> This comes up every half year or so.
> I don't see too much sense in this todo, esp. since there's
> no viable way to implement it without trying to recode the
> backend's password encryption (what we certainly won't do)

Huh? This stops someone casually looking over your shoulder and reading
your password as you type it in when adding a new server.

(and its committed - I just forgot to update the changelog).

/D

Re: CVS Commit by dpage: Updated todo.

From
Andreas Pflug
Date:
Dave Page wrote:
>

>
> Huh? This stops someone casually looking over your shoulder and reading
> your password as you type it in when adding a new server.
>

Ay...
Cancel my last msg.
I was thinking of the *user* password issue.

This was a clear case of "type ahead" :-)

Regards,
Andreas