| From: | Nicolas Huillard <nhuillard(at)ghs(dot)fr> |
|---|---|
| To: | "'Doug Alcorn'" <doug(at)lathi(dot)net>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | RE: using ssh for network authentication |
| Date: | 2000-05-21 16:37:46 |
| Message-ID: | 01BFC355.64CDAB20@ppp12-cergy.isdnet.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
The thing I usually do for this kind of protection is setup the machine's firewall, under Linux (just a matter of a new ipchains/ipfwadm small set of rules). I would also change Postrgres's pg_hba.conf file. It might be easy to deny all direct access to Postgres port 5432 using it.
Nicolas Huillard
-----Message d'origine-----
De: Doug Alcorn [SMTP:doug(at)lathi(dot)net]
Date: dimanche 21 mai 2000 05:02
À: pgsql-admin(at)postgresql(dot)org
Objet: [ADMIN] using ssh for network authentication
OK, I saw in the admin guide about how to do port redirection using
ssh. I even got it working. My question now is how to prevent any
network connections to my server via port 5432 and make sure they all
come through my sshd.
--
(__) Doug Alcorn (mailto:doug(at)lathi(dot)net - http://www.lathi.net)
oo / Win a 66GB capacity tape drive. Help me win too!
|_/ http://www.ecrix.com/extreme/getReferrals.cfm?ref=7612
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Loïc TREGOUËT | 2000-05-22 13:22:28 | inet type , select distinct troubles |
| Previous Message | Doug Alcorn | 2000-05-21 03:01:57 | using ssh for network authentication |