From: | Tim Ellis <Tim(dot)Ellis(at)gamet(dot)com> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | vwebtest(at)webhart(dot)deepnet(dot)cx, pgsql-admin(at)postgresql(dot)org |
Subject: | Re: DB Access Restrictions |
Date: | 2002-08-21 23:20:43 |
Message-ID: | 20020821192043.418d2b29.Tim.Ellis@gamet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-jdbc |
> If your network is not secure, I recommend MD5. In fact, we recommend
> MD5 with encrypted_passwords enabled in postgresql.conf in almost all
> cases. Encrypted passwords will be the default in 7.3.
psql seems to work flawlessly with MD5 passwords, which is no great
surprise.
The JDBC client doesn't seem to work. I had to go back to "password."
Is there something the client has to do with JDBC to make MD5 passwords
work? The particular client I'm talking about is DB Visualizer.
--
Tim Ellis
Senior Database Architect
Gamet, Inc.
From | Date | Subject | |
---|---|---|---|
Next Message | Klaus Sonnenleiter | 2002-08-22 00:55:19 | Re: password encryption |
Previous Message | Tim Ellis | 2002-08-21 23:18:21 | Re: OT: password encryption (salt theory) |
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Cramer | 2002-08-22 00:28:22 | Re: Update ResultSet for JDBC |
Previous Message | Felipe Schnack | 2002-08-21 19:44:50 | OFF-TOPIC: stored procedures |