Re: [GENERAL] How to encrypt data in Postgresql

2003-07-25 Thread Reuben D. Budiardja 
On Thursday 24 July 2003 02:59 pm, Franco Bruno Borghesi wrote:
 You must install pgcrypto (its in your contrib/pgcrypto directory).

 Then, the functions crypt and gen_salt will become available.

 As an example, to insert a new user (peter) with an encrypted password
 (1234) you can do:
 INSERT INTO myUsers(name, pass) VALUES ('peter', crypt('1234',
 gen_salt('md5'));

 To verify that anypassword is OK:
 SELECT (anypassword=crypt(anypassword, pass)) WHERE name='peter';

I think if you encrypt MD5 before storing it into the table, then there is no 
way to retrieve the corresponding clear text right? since MD5 is one-way 
encryption..

RDB


 The package includes many other functions, listed in README.pgcrypto.

 On Thu, 2003-07-24 at 15:18, Terence Chang wrote:
  Hi there:
 
  I know this might be an easy answer, but I was unable to figure out
  the solution.
 
  I would like to encrypt a password field in the table. I could not
  figure out how phpPGAdmin did.
 
  Should I use PHP's MD5 to encrypt the password? Is there a function in
  PostgreSQL that can encrypt the data with MD5?
 
  I would like to encrypt the data in PostgreSQL, so other program can
  use the same function. Can anyone give me some hints? What key word
  should I search in the document?
 
  Thansk!

-- 
Reuben D. Budiardja
Department of Physics and Astronomy
The University of Tennessee, Knoxville, TN
-
/\  ASCII Ribbon Campaign against HTML
\ /  email and proprietary format  
 X   attachments.
/ \
-
Have you been used by Microsoft today? 
Choose your life. Choose freedom. 
Choose LINUX.
-


---(end of broadcast)---
TIP 6: Have you searched our list archives?

   http://archives.postgresql.org

Re: [GENERAL] How to encrypt data in Postgresql

2003-07-25 Thread Richard Welty 
On Fri, 25 Jul 2003 09:33:30 -0400 Reuben D. Budiardja [EMAIL PROTECTED] wrote:

 I think if you encrypt MD5 before storing it into the table, then there
 is no 
 way to retrieve the corresponding clear text right? since MD5 is one-way 
 encryption..

yes, but normally when doing passwords, one encrypts and compares the
encrypted form. being able to decrypt stored passwords is generally
considered to be a bad thing.

this goes back to the earliest days of Un*x, at the very least. i know it
was standard in V7, it probably was standard in V6, and likely was being
done that way even before then (V7 is where my Un*x experience starts.)

one of the raps on Windows NT  friends is that the password hashes are
easily reversable, which means that if you manage to steal them, you're
well positioned to take ownership of the system.

but this is kind of OT for a postgresql list now...

richard
--
Richard Welty [EMAIL PROTECTED]
Averill Park Networking 518-573-7592
Java, PHP, PostgreSQL, Unix, Linux, IP Network Engineering, Security



---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
  joining column's datatypes do not match