I think we could defiantly store the individual parts encrypted in
dbmail_mimeparts and still have the hash on the un-encrypted data. But
the key to encrypt and decrypt would need to be stored/obtained
somewhere for imapd and pop3d to know how to read and write those blobs.
The header caching though would have the un-encrypted lines for the main
envelope (subject line too). Now even if the message is stored as
encrypted blobs, the network traffic will still transmit the message to
the client un-encrypted.
Again this comes back to what parts of the email you need to have encrypted.
-Jon
Michael Monnerie wrote:
On Donnerstag 18 Dezember 2008 Paul Stevens wrote:
cat message.eml|myencryptingfilter.sh --key $pgpid|dbmail-smtp -u
$user
Yes, but I think he meant you cannot read it with POP/IMAP then. His
goal seems to be to have encryption on the server, only for the stored
e-mail. BUT then the encryption+key has to be on the server, so in case
of a hacker attack it's still easy for the hacker to get db contents +
encryption tool+keys. And then I ask: what do you want to reach?
mfg zmi
------------------------------------------------------------------------
_______________________________________________
DBmail mailing list
[email protected]
https://mailman.fastxs.nl/mailman/listinfo/dbmail
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
_______________________________________________
DBmail mailing list
[email protected]
https://mailman.fastxs.nl/mailman/listinfo/dbmail
