| From: | Ben <bench(at)silentmedia(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Firewall Security Requirements for Postgresql Access |
| Date: | 2004-09-07 22:51:11 |
| Message-ID: | Pine.LNX.4.44.0409071549140.14155-100000@localhost.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Well, R/W doesn't make much sense for TCP.... incoming/outgoing SYN
packets make more sense, and if the database is located outside the
firewall, you really only need to allow outgoing SYN packets on the port
(as well as packets related to that session, of course).
On Wed, 8 Sep 2004, Gaetano Mendola wrote:
> Randy Yates wrote:
>
> > Is opening up port 5432 (R/W both directions) all that is required
> > of a firewall in order to access a postgres database outside the
> > firewall?
>
> Yes it is.
>
>
> Regards
> Gaetano Mendola
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to majordomo(at)postgresql(dot)org)
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-09-07 22:53:06 | Re: Firewall Security Requirements for Postgresql Access |
| Previous Message | Gaetano Mendola | 2004-09-07 22:22:35 | Re: Firewall Security Requirements for Postgresql Access |