-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday, 05.03.2004 at 11:10 +0200, Radu-Adrian Popescu wrote:
> | While I can see how to protect a PGSQL connection using SSH > | tunneling or a VPN, I cannot see any way to encrypt a PGSQL > | database stored on a hard disk, put aside the possibility to > | encrypt the hosting file system with LoopAES. What's wrong with using a LoopAES filesystem? It protects against someone walking off with the server, or at least the hard disk, and being able to see the data. Keeping encrypted data in the database itself is also perfectly possible; you just need to decide what you're going to use to decrypt it afterwards. Dave. - -- Dave Ewart [EMAIL PROTECTED] Computing Manager, Epidemiology Unit, Oxford Cancer Research UK PGP: CC70 1883 BD92 E665 B840 118B 6E94 2CFD 694D E370 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFASEZpbpQs/WlN43ARApVHAKD+ymIbp+HAFUJwaTQ7JyUL07f3GgCeN9D7 miJut0SeQ7/16ANQf1NUUWk= =lzG/ -----END PGP SIGNATURE----- ---------------------------(end of broadcast)--------------------------- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
