Search Postgresql Archives

Re: Making the DB secure

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On 06/20/2005 12:32:12 PM, Együd Csaba wrote:
Hi,
thank you very much. These are very good ideas, I think.
I forgot one thing to mention. We will have very few clients (max. 20)
and
all clients will be required to have a fix IP address. Fix IP
addresses can
be listed in pg_hba.conf to filter incoming IPs very efficiently. With
this
note, do you think we need VPN or other enhancement?

You want to consider the failure modes.  LANs can be
ARP spoofed to redirect traffic to elsewhere than their
destination IP, or what happens if the client does not request
encryption or the server is restarted without encryption
enabled, etc.  You don't want to be allowing insecure
communication by accident and unawares.  VPNs are
designed to disable communication
on failure, and the designers have presumably thought
of all the senarios.  When you roll your own security
you need to be the one that thinks of everything.
(Of course, some VPN products are much less secure
than others.)

And maintaining things over time is always an issue.

Karl <kop@xxxxxxxx>
Free Software:  "You don't pay back, you pay forward."
                 -- Robert A. Heinlein


---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
     subscribe-nomail command to majordomo@xxxxxxxxxxxxxx so that your
     message can get through to the mailing list cleanly

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux