Jonathan Feally wrote: > I think we could defiantly store the individual parts encrypted in > dbmail_mimeparts and still have the hash on the un-encrypted data.
That won't work. If the hash cannot be verified against the blob, you cannot check for key-collisions. > Again this comes back to what parts of the email you need to have > encrypted. My point indeed. If you follow the filter path by converting all messages to s/mime or pgp/mime you are up and running. Of course reading email would require access to the secret key used to encrypt in the first place, which means you would have to have access to the public keys for all users for whom you'd wish to encrypt storage. But you'd be home free if you do. Of course anyone accessing your database could still do traffic analyses and such on the cleartext header caching tables, but all message content would be inaccessible. -- ________________________________________________________________ Paul Stevens paul at nfg.nl NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31 The Netherlands________________________________http://www.nfg.nl _______________________________________________ DBmail mailing list [email protected] https://mailman.fastxs.nl/mailman/listinfo/dbmail
