| From: | Goran Thyni <goran(at)bildbasen(dot)se> |
|---|---|
| To: | brett(at)work(dot)chicken(dot)org |
| Cc: | ocie(at)paracel(dot)com, maillist(at)candle(dot)pha(dot)pa(dot)us, scrappy(at)hub(dot)org, jwieck(at)debis(dot)com, Andreas(dot)Zeugswetter(at)telecom(dot)at, pgsql-hackers(at)hub(dot)org |
| Subject: | Re: [HACKERS] Solution to the pg_user passwd problem !?? (c) |
| Date: | 1998-02-26 16:35:18 |
| Message-ID: | 19980226163518.17392.qmail@guevara.bildbasen.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> What about a public/private key mechanism, like ssh?
Yes, just use ssh as-is and run psql etc in a ssh tunnel
when running over insecure nets.
Making cryptography part of pgsql is not good idea for two reasons:
1. It is bloat
2. It make us targets of legal-problems (US-export-control etc).
IMHO, even Kerberous should be removed.
info about ssh is available at:
http://www.cs.hut.fi/ssh/ free version
http://www.ssh.fi/ commercial (+mac/windows) versions
regards,
--
---------------------------------------------
Gran Thyni, sysadm, JMS Bildbasen, Kiruna
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas G. Lockhart | 1998-02-26 17:03:27 | Re: [QUESTIONS] Re: RH5.0/PostgreSQL Regression Test Failures |
| Previous Message | Andrew Martin | 1998-02-26 16:31:55 | Snapshot 26Feb98 - another minor showstopper |