The problem is having the data encrypted as it is stored. Paul Stevens
said in one of his posts that this is a *bad* idea. Is this because of
the amount of time it would take, or is there another problem here? What
I was thinking is that if I had the encryption library on the server
then on the insert code for the messageblks table (only for non header
parts, obviously) I could call the encrypt function using the public key
of the user it is being inserted into. Then when he opens the email on
his client, his private key would open it automatically.
Then the only thing I would have to worry about is sniffers and people
accessing the computer to read email, which I am really not worried about.
Is there a reason this wouldn't work?
Sim
If I have the PGP library on the server and I call the Encrypt function
using a
Again, gnuPG or PGP should be all you need. The content will be stored
encrypted, where only the receiver is able to decrypt.
And provides the same security as your password encrypted documents.
They can be cracked if one logs onto the CEO computer.
Marc
_______________________________________________
DBmail mailing list
[email protected]
https://mailman.fastxs.nl/mailman/listinfo/dbmail
