James wrote:
Ray_Net wrote:
James wrote:
Ray_Net wrote:
James wrote:
Mark Hansen wrote:
On 10/25/2010 12:46 PM, James wrote:
You make it seem as if you never sent or received an encrypted
email using your method. If you had, you would know what each
participant is required to have. Still, when I have time, I will
continue to research Enigmail. So far it seems it will only work
with Mozilla email client programs.
Actually, I sent encrypted/signed message to and received from
many people. However, I don't know what they were using.
Reading the documentation makes it seem that it is a certificate
creator and manager. There is nothing that presumes the
certificates will not work anywhere a certificate is used. I do
not think this will solve the problem in sending certificate
encrypted emails to Thunderbird and receiving certificate
encrypted emails from Thunderbird.
I tried again to encrypt to Thunderbird and again failed. All the
other attempts succeeded. Without a definitive answer to the
SeaMonkey email certificate problem, I must migrate back to
Thunderbird.
Personally, I believe that all internet traffic should be
encrypted. Unfortunately, the majority say, "I keep myself
vulnerable because I want to be abused, here is my banking
information". I do not wish the hackers to know that I am saying
things like, "Hello, how are you?" in the emails I send. Let them
try to decrypt it to find out there is no personal info there.
So you need to sent the public key to everyone in the world -
because you don't know to which person the destination of the next
mail will be...
Is that not how Enigmail works? You trade public keys (certificates)
then you may encrypt? I have zero experience with Enigmail,
Me too :-) I think that you must send public key but you should
encrypt with your personal key. I never use encrypted mail to not
force the recipent to install decryption software, etc ... let the
people stay simple and reserve encrypted mail if you want to sent
sensible data in a mail.
It seems to me that Enigmail makes certificates easier to create and
manage, but the signed and encrypted emails themselves are handled the
same with or without Enigmail. If you would like to practice, you may
send me a signed email. I will then reply signed. Then we may attempt
sending each other encrypted emails. You with Enigmail and me without.
It should work as we are both using SeaMonkey. I would like to test it
out with someone that is using Thunderbird as I have only one
correspondent that uses Thunderbird for encryption and it would be
useful to find out if it works or the problem is with SeaMonkey or
with Thunderbird. One point on a chart does not make a graph.
SeaMonkey to SeaMonkey test completed. Both SeaMonkey email clients had
certificate authority issued certificates. After trading signed emails,
encryption was successful in both directions.
Unfortunately, that does not help explain why it fails with Thunderbird.
Without a fix, migrating back to Thunderbird will be necessary.
My thanks to everyone that has contributed to this thread.
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
