Alex Daniloff escribió: > You're missing this point: > > 4. When the Mail Server receives a message encrypted with subscriber's > private > key, it decrypts it using existing subscriber's private key stored in SQL > database. Then the Mail Server encrypts this message with the Mailing List > public encryption key and distributes it to all other Mailing List > subscribers. >
If someone else finds a mailing list server that do this, do not use it :-) this would be: 1. highly innecifient and resource hungry 2. insecure as hell, I reccommend you to RTFM :) especially the GPG related documentation, that **clearly** warns on this approach 's insecurity. You are tying to solve a non-technical problem with encryption and your requirements are so ill conceived (storing private keys in a database is the part that smells fishy enough to discard your idea) that I suggest you either talk to your lawyer about privacy and confidentility rules of your business and/or think your requirements better, what you are trying to do is plain wrong.. and having wrong security is worse than no security at all. -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
