Thread: SVN Commit by dpage: r5106 - in trunk/pgadmin3: . src src/db src/dlg src/include src/utils

SVN Commit by dpage: r5106 - in trunk/pgadmin3: . src src/db src/dlg src/include src/utils

From

svn@pgadmin.org

Date:

30 April 2006, 20:13:29

Author: dpage

Date: 2006-04-30 21:13:00 +0100 (Sun, 30 Apr 2006)

New Revision: 5106

Revision summary: http://svn.pgadmin.org/cgi-bin/viewcvs.cgi/?rev=5106&view=rev

Log:
Pre-encrypt passwords before sending them down the wire or displaying them in SQL statements.


Added:
   trunk/pgadmin3/src/include/md5.h
   trunk/pgadmin3/src/utils/md5.cpp
Modified:
   trunk/pgadmin3/CHANGELOG
   trunk/pgadmin3/TODO
   trunk/pgadmin3/src/db/pgConn.cpp
   trunk/pgadmin3/src/dlg/dlgRole.cpp
   trunk/pgadmin3/src/dlg/dlgUser.cpp
   trunk/pgadmin3/src/include/module.mk
   trunk/pgadmin3/src/include/pgConn.h
   trunk/pgadmin3/src/pgAdmin3.dsp
   trunk/pgadmin3/src/utils/module.mk

Re: SVN Commit by dpage: r5106 - in trunk/pgadmin3:

From

Andreas Pflug

Date:

01 May 2006, 10:46:14

svn@pgadmin.org wrote:
> Author: dpage
>
> Date: 2006-04-30 21:13:00 +0100 (Sun, 30 Apr 2006)
>
> New Revision: 5106
>
> Revision summary: http://svn.pgadmin.org/cgi-bin/viewcvs.cgi/?rev=5106&view=rev
>
> Log:
> Pre-encrypt passwords before sending them down the wire or displaying them in SQL statements.

Is that a good idea to do this in a private md5 implementation? libpq is
going to/already exporting a method for this, which will make us less
sensitive to backend changes.

Regards,
Andreas