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, but the
documentation suggests it is a certificate generator and certificate
manager add-on for Mozilla email client programs.
Certificates issued by certificate authorities work to enable you to
sign emails that can be sent to anyone, but both sender and recipient
need each other's public keys for encryption. Trading certificates with
an initial email and reply using signed emails is about as convenient as
it gets before you can start sending encrypted emails.
Before secure emails, you had to encrypt a file and send it as an
attachment. Self-extracting files were executable (.exe) and all the
emails I tried to send with an executable file were stopped. This means
both need the same encryption software. Trading passwords securely may
be a problem using stand alone encryption. In my experience, the
majority have no idea that their emails are being routinely scanned by
hackers looking for a quick profit. I keep hearing stories about people
sending credit card info to a family member to make a purchase and the
credit card or bank account being raided for all it is worth by a hacker
even before the family member can use it. I do not even like sending
unencrypted emails that have no personal information, but convincing the
drooling mouth breather with a mind of a gnat that encryption is good is
as harder than teaching people to breathe under water. They argue, "I
have nothing to hide."
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
