Re: [Enigmail] What about PGP/Header support?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/15/2014 02:28 PM, Egbert van der Wal wrote: I actually see encryption as less of an issue. When I send an encrypted message to someone, I need to know for sure that the recipient knows about PGP encryption and knows how to decode it. If I send an encrypted message to someone who does not use PGP, he/she cannot read it, no matter what. How do you send an encrypted message to someone who does not use PGP? You need his public key to do that. - -- .~. Jean-David Beyer Registered Linux User 85642. /V\ PGP-Key:166D840A 0C610C8B Registered Machine 1935521. /( )\ Shrewsbury, New Jerseyhttp://linuxcounter.net ^^-^^ 08:20:01 up 3 days, 17:22, 2 users, load average: 4.44, 4.35, 4.41 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJTJZdhAAoJEBZthAoMYQyLUmsH/0u3IEQiqCJGoMBicr5XGiQh ciflEIZ6EC7XI4YtPwyqWIKm98iUqZTPr/f2wZVBJO6IZE7+d6Y9RJghV6ZDn2gI Fr8jyTu+g4PtCzj2VWycKKP9ok8ZgRfcAMOtCmWFRK+5ErGt7qDOLw6B/TAmUlsc 7arfGsUh39lLFpPo9xfWpFc0qMlIwmaM+TZIzl+xbUbq6tsXujZ0M1JSM3lq9r21 z1pQJuUQazHg2BnVxLz2TInVkuwZoSWzi+8XROmLa+SQQSgFusYGeo0D3QM73jJM 3Elqr8DI6R8pYaFhS0qwFml+f+Ry5BrPdtI3Oc/Rf5UZGkLCxeJvtpOTh2Exspg= =AzgD -END PGP SIGNATURE- ___ enigmail-users mailing list enigmail-users@enigmail.net https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
Re: [Enigmail] Using Enigmail for mailing lists
-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 Hi Boris, me and some friends of mine want to exchange encrypted emails on our mailing list. Does enigmail support encryption for multiple recepients? How would you encrypt information on a mailing list? I know of three ways to achieve this: either request anyone joining to provide his/her key to the list master who in turn merges all received keys in some keyring that is redistributed to all members - or by using one shared key. In general, both only work with smaller groups. In the first case, all members need to regularly redownload the current list-public-keyring and adopt their per-receipint rules. In the latter case, you need to trust each member to redistribute the key (and not being haked). In your case it seems to be a smaller group. *If* all members have the ability to define rules such as Enigmail can, there is a third way: you import the pub keys of all members and define a per-receipient rule Encrypt all messages to list-address to the following keys: member1, member2, That works well at least for our internal Enigmail team list address ;-) Olav - -- The Enigmail Project - OpenPGP Email Security For Mozilla Applications -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (MingW32) Comment: Dies ist eine elektronische Signatur - http://www.enigmail.net/ iQGcBAEBAwAGBQJTJcl3AAoJEKGX32tq4e9WrY0L/i5nEUGh/CTlgPP0ZB04Oq+a qKQV09P+ZyNO3kTEdhxk+RIj3shuX4oCunrCQR24kC2U2KDs3TGGhJ+86WU8R5D+ Fcw9/1jbLuCQMwD4aXRceo7wd7gwPMtX4B5scSpfYjZGgT/s71cCPeGQCyLyrdBD eoexvIJQvW5iLDpaoIBFrZJhv9xAMq+Kg2qGD/yt3aUcj+drVpN3ySpJcLE5J4iA uA5Zb3Q2clmgRTHiXlKRrvKFyMrUZCRZo4CH+fXr6oPTtgy/Sbq8GPcyujrvF86e UybC0GWLoWBDW5O5jFxve0Fxiqp2iiodpm9lcrt94kJHB6r70sgX+todJsF169yp nreZVTHIU5Qw3RW71l/l0ooHd3T8eL6oeCT5J5HVU8ZNnPGRsC4rYP3dOaqiZvxN X+Cc5NIXXTeB2VD0j+nXjYCpyYpMCO+N7sMHmbjgDVx4qaGPyaCKFTUk34AlsXWu WbXD8+suOxF/NJmZcp+7enbUvw6umZpjheq7SdkY6A== =Lwpa -END PGP SIGNATURE- ___ enigmail-users mailing list enigmail-users@enigmail.net https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
Re: [Enigmail] What about PGP/Header support?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 03/16/14 08:21, Jean-David Beyer wrote: On 03/15/2014 02:28 PM, Egbert van der Wal wrote: I actually see encryption as less of an issue. When I send an encrypted message to someone, I need to know for sure that the recipient knows about PGP encryption and knows how to decode it. If I send an encrypted message to someone who does not use PGP, he/she cannot read it, no matter what. How do you send an encrypted message to someone who does not use PGP? You need his public key to do that. Exactly. How are you going to send an encrypted message to someone who does not have a public key? You can't. Period. Unless you separately arrange a symmetric encryption key to use or pre-arrange to send a symmetric encryption key out-of-band. It's a non-issue from the point of view of Enigmail. If you *can* send someone an encrypted message, you have their public key. If they don't have one, you don't have it either, and you can't. End of story. - -- Phil Stracchino Babylon Communications ph...@caerllewys.net p...@co.ordinate.org Landline: 603.293.8485 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEAREIAAYFAlMl+d4ACgkQ0DfOju+hMkkmPACglLEX3Ck6PjsHRz9j0unq6maY mhIAoMbURRphgGtl9mzuhQlFCmWPjJ8b =8A5S -END PGP SIGNATURE- ___ enigmail-users mailing list enigmail-users@enigmail.net https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
Re: [Enigmail] What about PGP/Header support?
Oh, I most definitely can send an encrypted message to anyone. The recipient will not be able to decrypt it since I don't have his public key so I'll have to use some random other key, but I can send him an encrypted message. Anyway, these things confirm my point: the way the PGP signature is transfered is only relevant for signed but unencrypted mails as you may as well send these mails to people that do know know, understand or use PGP. And those people may get confused by the way that the signature is transfered: either inline or as an attachment. Embedding this in the header solves this issue. Of course, it will require further specification in an RFC and it will require more broad support than from just one client (although I personally don't know anyone that does use PGP and does not use Enigmail to do so but that's just my personal circle, of course). But it has to start somewhere, right? Regards, Egbert On 03/16/2014 08:22 PM, Phil Stracchino wrote: On 03/16/14 08:21, Jean-David Beyer wrote: On 03/15/2014 02:28 PM, Egbert van der Wal wrote: I actually see encryption as less of an issue. When I send an encrypted message to someone, I need to know for sure that the recipient knows about PGP encryption and knows how to decode it. If I send an encrypted message to someone who does not use PGP, he/she cannot read it, no matter what. How do you send an encrypted message to someone who does not use PGP? You need his public key to do that. Exactly. How are you going to send an encrypted message to someone who does not have a public key? You can't. Period. Unless you separately arrange a symmetric encryption key to use or pre-arrange to send a symmetric encryption key out-of-band. It's a non-issue from the point of view of Enigmail. If you *can* send someone an encrypted message, you have their public key. If they don't have one, you don't have it either, and you can't. End of story. ___ enigmail-users mailing list enigmail-users@enigmail.net https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net signature.asc Description: OpenPGP digital signature ___ enigmail-users mailing list enigmail-users@enigmail.net https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
