From michaeljgruber+mozdevnews at fastmail.fm Fri Jul 3 01:12:57 2009 From: michaeljgruber+mozdevnews at fastmail.fm (Michael J Gruber) Date: Fri, 03 Jul 2009 10:12:57 +0200 Subject: [Enigmail] RFE/Suggestion Message-ID: Hi there, just a small suggestion which may be easy to implement for someone with a good overview of the code base: Have an item "Import attached keys" in the message context menu. Right now one can import keys/signatures from the context menu of attachments. But this is impractical when one has to deal with the myriad of automated e-mails after a key signing party (caff/ca-bot). I'm resorting to mutt for now. The suggested menu option should work with multiple selections, go through each e-mail and call gpg --import on them, thereby importing all keys or signatures which are attached. Cheers, Michael P.S.: I'm using Enigmail/cvs with TB/comm-central, at least there I don't see anything in that context menu. Sorry if it's merely an issue with TB3. From olav at mozilla-enigmail.org Fri Jul 3 01:31:45 2009 From: olav at mozilla-enigmail.org (Olav Seyfarth) Date: Fri, 03 Jul 2009 10:31:45 +0200 Subject: [Enigmail] RFE/Suggestion In-Reply-To: References: Message-ID: <4A4DC1F1.3030700@mozilla-enigmail.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi Michael, > Sorry if it's merely an issue with TB3. it isn't. But please use bugzilla to file the RFE. That way it will not be forgotten. Thanks for your suggestion, Olav -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12-svn5008 (MingW32) Comment: Diese ist eine Digitale Signatur nach OpenPGP-Standard Comment: http://privat.seyfarth.de/olav/schluessel.html iEYEAREIAAYFAkpNwe8ACgkQL/NBt8fdKe3WQACdF9k4oz4sWLn4ctc9ea289S0Z WS4An0aYwAzRk6T+3sdkBcCWMRLmuPNc =RFfw -----END PGP SIGNATURE----- From maike.marrek at gmx.de Tue Jul 7 12:54:55 2009 From: maike.marrek at gmx.de (maike.marrek@gmx.de ) Date: Tue, 07 Jul 2009 21:54:55 +0200 Subject: [Enigmail] Installation enigmail addon/Seamonkey Message-ID: <20090707195459.16DB7844AB@mozdev.mozdev.org> Hallo, ich benutze XP und kann mit meinem aktuellen seamonkey nicht das enigmail-addon installieren. Fehlermeldung 211. S?mtliche Suchmaschinen liefern mir leider keinen brauchbaren L?sungsvorschlag - au?er dass ich unter linux nur ein sudo machen m?sste ;-) habe jetzt bereits saubere neuinstallionen ausprobiert ... aber nichts ... habt Ihr vielleicht einen L?sungsvorschlag? Mit bestem Dank & Gru? aus Frankfurt Maike From mlisten at hammernoch.net Tue Jul 7 23:05:07 2009 From: mlisten at hammernoch.net (=?ISO-8859-1?Q?Ludwig_H=FCgelsch=E4fer?=) Date: Wed, 08 Jul 2009 08:05:07 +0200 Subject: [Enigmail] Installation enigmail addon/Seamonkey In-Reply-To: <20090707195459.16DB7844AB@mozdev.mozdev.org> References: <20090707195459.16DB7844AB@mozdev.mozdev.org> Message-ID: <4A543713.9050809@hammernoch.net> Hi, first of all, this list uses english. Using other languages limits the number of useful replies. Also, more users benefit from solutions found during a disussion held in english :-) maike.marrek at gmx.de wrote on 07.07.09 21:54: > Hallo, > > ich benutze XP und kann mit meinem aktuellen seamonkey nicht das > enigmail-addon installieren. Fehlermeldung 211. So you're using Seamonkey 1.1.17? Which version of enigmail did you try to install? What is the exact error message? > S?mtliche Suchmaschinen liefern mir leider keinen brauchbaren > L?sungsvorschlag - au?er dass ich unter linux nur ein sudo machen m?sste > ;-) > > habe jetzt bereits saubere neuinstallionen ausprobiert ... aber nichts ... > > habt Ihr vielleicht einen L?sungsvorschlag? Maybe some traces from an unsuccessful install of enigmail remain in your user profile which is not touched by a reinstall of Seamonkey. So it would be useful to start over with a fresh user profile. Please back up your old profile if it contains valuable mails and/or settings. > Mit bestem Dank & Gru? aus Frankfurt Greetings from Bamberg :-) Ludwig -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 550 bytes Desc: OpenPGP digital signature URL: From cai.0407 at gmail.com Thu Jul 9 20:29:24 2009 From: cai.0407 at gmail.com (Kosuke Kaizuka) Date: Fri, 10 Jul 2009 12:29:24 +0900 Subject: [Enigmail] Enigmail v0.96 Beta Released In-Reply-To: <4A4913AE.2040200@mozilla-enigmail.org> References: <4A4913AE.2040200@mozilla-enigmail.org> Message-ID: <4A56B594.2060401@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi, Why don't you change Enigmail's icons for Tb win to ones which fits Tb 2.0 defalut theme. For example, toolbar buttons of Tb main window and mail compose window mistaches other Tb default buttons (reply, forward and S/MIME) ;-) Tue Jun 30 2009 04:19:10 GMT+0900, Patrick Brunschwig wrote: > I have created a beta version of Enigmail v0.96 for Thunderbird 2.0.x > and SeaMonkey 1.1.x. The release has several new features and > enhancements, and contains a lot of fixed bugs. In particular, I tried > to address all known bugs that can be fixed without rewriting major > parts of Enigmail or Thunderbird. > > The (unsigned) beta release can be found here, I expect to create an > official v0.96 release in 1-2 weeks: > > > Unfortunately, the release still lacks several language packs, in > particular: > - Chinese (traditional and simplified) > - Czech > - Dutch > - Finnish > - French > - Greek > - Hungarian > - Korean > - Norwegian > - Romanian > - Slovak > - Spanish (es-AR and es-ES) > - Turkish > > For all the languages above, any new texts will be displayed in English. > If you volunteer to translate the new and changes texts, then please > contact me! > > Have fun! > -Patrick _______________________________________________ Enigmail mailing list Enigmail at mozdev.org https://www.mozdev.org/mailman/listinfo/enigmail - -- Kosuke Kaizuka -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEAREKAAYFAkpWtZQACgkQxsAYUFhjCPqAzgCeIlPo7q0jboeg4zHsUqte6olF DroAn34gLjwM9GieMDKqUt4kMrvrzEkG =crSb -----END PGP SIGNATURE----- From patrick at mozilla-enigmail.org Fri Jul 10 10:08:30 2009 From: patrick at mozilla-enigmail.org (Patrick Brunschwig) Date: Fri, 10 Jul 2009 19:08:30 +0200 Subject: [Enigmail] Enigmail v0.96 Beta Released In-Reply-To: <4A56B594.2060401@gmail.com> References: <4A4913AE.2040200@mozilla-enigmail.org> <4A56B594.2060401@gmail.com> Message-ID: <4A57758E.3080601@mozilla-enigmail.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Kosuke Kaizuka wrote: > Tue Jun 30 2009 04:19:10 GMT+0900, Patrick Brunschwig wrote: >> I have created a beta version of Enigmail v0.96 for Thunderbird 2.0.x >> and SeaMonkey 1.1.x. The release has several new features and >> enhancements, and contains a lot of fixed bugs. In particular, I tried >> to address all known bugs that can be fixed without rewriting major >> parts of Enigmail or Thunderbird. > [...] > >> For all the languages above, any new texts will be displayed in English. >> If you volunteer to translate the new and changes texts, then please >> contact me! > Hi, > > Why don't you change Enigmail's icons for Tb win to ones which fits Tb > 2.0 defalut theme. > For example, toolbar buttons of Tb main window and mail compose window > mistaches other Tb default buttons (reply, forward and S/MIME) ;-) There will be new icons for Thunderbird 3.0. - -Patrick -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEVAwUBSld1jHcOpHodsOiwAQgj5wf/Q0YcEhDu96w+nFp/n31/q7L4leuqi+90 Vn6Fr2hKWifnn8abpXkLvesLYU56JquplPoUWnruD7RHoOGs7EJ3qWVThb8M/dG5 Jqy6gtMZIcAax/nrFweYo+N1w3HLBjhzAaukmcU0XatXUWdZfc/rny0/m4PeXfPk dpx8Ou8CYLJaN/J/f132xo0L/UHHUhqh7eyF701ea/9WJYQAd3yNi4jO5WcSDAHO jMDIkMoSXGw2d7w2s5mvkTfETUDIPFE5OJX4OH2Ph3aToaT/AZGoKNUZLTNodwrp 2OlokpvVV44ovgvTm7q0V1BE4R3Fg+xHrchG1bsaHIKL9aJw6nMUog== =wVaF -----END PGP SIGNATURE----- From patrick at mozilla-enigmail.org Fri Jul 10 10:35:47 2009 From: patrick at mozilla-enigmail.org (Patrick Brunschwig) Date: Fri, 10 Jul 2009 19:35:47 +0200 Subject: [Enigmail] Installation enigmail addon/Seamonkey In-Reply-To: <4A543713.9050809@hammernoch.net> References: <20090707195459.16DB7844AB@mozdev.mozdev.org> <4A543713.9050809@hammernoch.net> Message-ID: <4A577BF3.9000907@mozilla-enigmail.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Ludwig H?gelsch?fer wrote: > Hi, > > first of all, this list uses english. Using other languages limits the > number of useful replies. Also, more users benefit from solutions found > during a disussion held in english :-) > > maike.marrek at gmx.de wrote on 07.07.09 21:54: >> Hallo, >> >> ich benutze XP und kann mit meinem aktuellen seamonkey nicht das >> enigmail-addon installieren. Fehlermeldung 211. > > So you're using Seamonkey 1.1.17? Which version of enigmail did you try > to install? What is the exact error message? > >> S?mtliche Suchmaschinen liefern mir leider keinen brauchbaren >> L?sungsvorschlag - au?er dass ich unter linux nur ein sudo machen m?sste >> ;-) >> >> habe jetzt bereits saubere neuinstallionen ausprobiert ... aber nichts ... >> >> habt Ihr vielleicht einen L?sungsvorschlag? > > Maybe some traces from an unsuccessful install of enigmail remain in > your user profile which is not touched by a reinstall of Seamonkey. So > it would be useful to start over with a fresh user profile. Please back > up your old profile if it contains valuable mails and/or settings. > >> Mit bestem Dank & Gru? aus Frankfurt According to the Mozilla documentation, error 211 means "Installation not started" (which is not very helpful, but all I could find). I could imagine that you don't have the rights required to install Enigmail. You'll need local Administrator rights for SeaMonkey 1.x to install Enigmail. Also, make sure that the 1st start of SeaMonkey after Enigmail is installed is done with local administrator rights. - -Patrick -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEVAwUBSld78ncOpHodsOiwAQiKvwf+LA9hBVOF183/mjRDWTAY3lAgWOriXHIE YPMlS3BPp+U4Zd6SovWRcCjKQndkbnuh0Jg/OOfdaXwpQDvVWpSNILCVZ/7UQ/og ePsAQBL+bNYB/54S+KXmZwDCgBqZF4EKavaP21LBFCAZMRb1yEYnz1K3uPRXI3Pl kEbL715CGSmyGE3acL879BZ6FvqxL/SlrowaJgvJ3fKLd8Cq/pF7HsJ0vZMD2D+/ hLgJ2W0cE+iSH/vYUiHJAPfqGCqPCeawCiB7xEaMs9e6HJVl8WfUNQv6wnmi+5zu abn+eIRexiI4gwR+cTvvPjyxtvENgGJSnnUTsjtH44se0bZTk4tkgw== =0DOP -----END PGP SIGNATURE----- From patrick at mozilla-enigmail.org Fri Jul 10 10:35:47 2009 From: patrick at mozilla-enigmail.org (Patrick Brunschwig) Date: Fri, 10 Jul 2009 19:35:47 +0200 Subject: [Enigmail] Installation enigmail addon/Seamonkey In-Reply-To: <4A543713.9050809@hammernoch.net> References: <20090707195459.16DB7844AB@mozdev.mozdev.org> <4A543713.9050809@hammernoch.net> Message-ID: <4A577BF3.9000907@mozilla-enigmail.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Ludwig H?gelsch?fer wrote: > Hi, > > first of all, this list uses english. Using other languages limits the > number of useful replies. Also, more users benefit from solutions found > during a disussion held in english :-) > > maike.marrek at gmx.de wrote on 07.07.09 21:54: >> Hallo, >> >> ich benutze XP und kann mit meinem aktuellen seamonkey nicht das >> enigmail-addon installieren. Fehlermeldung 211. > > So you're using Seamonkey 1.1.17? Which version of enigmail did you try > to install? What is the exact error message? > >> S?mtliche Suchmaschinen liefern mir leider keinen brauchbaren >> L?sungsvorschlag - au?er dass ich unter linux nur ein sudo machen m?sste >> ;-) >> >> habe jetzt bereits saubere neuinstallionen ausprobiert ... aber nichts ... >> >> habt Ihr vielleicht einen L?sungsvorschlag? > > Maybe some traces from an unsuccessful install of enigmail remain in > your user profile which is not touched by a reinstall of Seamonkey. So > it would be useful to start over with a fresh user profile. Please back > up your old profile if it contains valuable mails and/or settings. > >> Mit bestem Dank & Gru? aus Frankfurt According to the Mozilla documentation, error 211 means "Installation not started" (which is not very helpful, but all I could find). I could imagine that you don't have the rights required to install Enigmail. You'll need local Administrator rights for SeaMonkey 1.x to install Enigmail. Also, make sure that the 1st start of SeaMonkey after Enigmail is installed is done with local administrator rights. - -Patrick -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEVAwUBSld78ncOpHodsOiwAQiKvwf+LA9hBVOF183/mjRDWTAY3lAgWOriXHIE YPMlS3BPp+U4Zd6SovWRcCjKQndkbnuh0Jg/OOfdaXwpQDvVWpSNILCVZ/7UQ/og ePsAQBL+bNYB/54S+KXmZwDCgBqZF4EKavaP21LBFCAZMRb1yEYnz1K3uPRXI3Pl kEbL715CGSmyGE3acL879BZ6FvqxL/SlrowaJgvJ3fKLd8Cq/pF7HsJ0vZMD2D+/ hLgJ2W0cE+iSH/vYUiHJAPfqGCqPCeawCiB7xEaMs9e6HJVl8WfUNQv6wnmi+5zu abn+eIRexiI4gwR+cTvvPjyxtvENgGJSnnUTsjtH44se0bZTk4tkgw== =0DOP -----END PGP SIGNATURE----- From sean at srima.eu Sun Jul 12 09:40:08 2009 From: sean at srima.eu (Sean Rima) Date: Sun, 12 Jul 2009 17:40:08 +0100 Subject: [Enigmail] Been away, Enigmail not on 2.0.0.22 Message-ID: <4A5A11E8.3050901@srima.eu> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi Been away for awhile, And Updated my Thunderbird to 2.0.0.22 but Enigmail does not work, is there anything I need to do Sean -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) - GPGshell v3.73 Comment: Gossamer Spider Web of Trust: http://www.gswot.org Comment: Contact Details http://rima.tel iEYEAREIAAYFAkpaEdwACgkQydfi32iLfZiNxgCgl7NDTcSVSdRJRfGp+iWFFc06 WjcAoJpSdr4ymx2xBy+/3NP1EW9F83rx =9+XK -----END PGP SIGNATURE----- From jmoore3rd at bellsouth.net Sun Jul 12 09:48:41 2009 From: jmoore3rd at bellsouth.net (John W. Moore III) Date: Sun, 12 Jul 2009 12:48:41 -0400 Subject: [Enigmail] Been away, Enigmail not on 2.0.0.22 In-Reply-To: <4A5A11E8.3050901@srima.eu> References: <4A5A11E8.3050901@srima.eu> Message-ID: <4A5A13E9.3000604@bellsouth.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Sean Rima wrote: > Been away for awhile, And Updated my Thunderbird to 2.0.0.22 but > Enigmail does not work, is there anything I need to do If You installed the latest Enigmail Nightly Build then it will _not_ work on 2.0.0.22 as the Nightly Builds began following the Thunderbird3/SeaMonkey2 API over a week ago. works nicely with 2.0.0.22pre. [IIRC the latest Tb stable release is 2.0.0.21] NOTE: The above Link is to a Beta version so YMMV. :) If You are using Shredder [Tb3.0b3] then You will need the Enigmail Nightly Build(s). HTH JOHN ;) Timestamp: Sunday 12 Jul 2009, 12:44 --400 (Eastern Daylight Time) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10-svn5068: (MingW32) Comment: Public Key at: http://tinyurl.com/8cpho Comment: Gossamer Spider Web of Trust: http://www.gswot.org Comment: Personal Web Page: http://tinyurl.com/yzhbhx iQEcBAEBCgAGBQJKWhPnAAoJEBCGy9eAtCsP4LQIAIyRPCDlEC56q7gHeOlKE3Jt SxD7sQmO0NI20t9O8swL/FUMGfIvr5OBg+CYdkzfI/uf91Iqq+4LasioF0ln5nAd O/V7d3G0zMcFbAafXl1p35RirrWp1o5hZfUuZUksz0MATfWattS1dkJTAtvdCsU/ dL3+6m6l6PvbYq0e7c2gTANKBLWeusoLiaAJ30x4rzQW7UbuedeV8W7HfryP/Smn LOiRNpEdtBfkUXHKIWM1AUthFX6kc8I1er2/I2JqYKOYIy2kmJtrnBsKBZAvgGEw vohdqCOLIleieooXb2QQt+2suuX5IvhYvLDcU7stR6wH0cW7gpOh4NdZfxM7WEA= =Eo20 -----END PGP SIGNATURE----- From sean at srima.eu Sun Jul 12 09:52:32 2009 From: sean at srima.eu (Sean Rima) Date: Sun, 12 Jul 2009 17:52:32 +0100 Subject: [Enigmail] Been away, Enigmail not on 2.0.0.22 In-Reply-To: <4A5A13E9.3000604@bellsouth.net> References: <4A5A11E8.3050901@srima.eu> <4A5A13E9.3000604@bellsouth.net> Message-ID: <4A5A14D0.40901@srima.eu> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 John W. Moore III wrote: >> Been away for awhile, And Updated my Thunderbird to 2.0.0.22 but >> Enigmail does not work, is there anything I need to do > > If You installed the latest Enigmail Nightly Build then it will _not_ > work on 2.0.0.22 as the Nightly Builds began following the > Thunderbird3/SeaMonkey2 API over a week ago. > > works nicely > with 2.0.0.22pre. [IIRC the latest Tb stable release is 2.0.0.21] > I installed/downloaded from the main addons site as I am using the current production Thunderbird Sean -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) - GPGshell v3.73 Comment: Gossamer Spider Web of Trust: http://www.gswot.org Comment: Contact Details http://rima.tel iEYEAREIAAYFAkpaFMkACgkQydfi32iLfZilUACgiwUa8lym8fp4vEBu6pAX238l 1PoAn1bQwRKtXsdsDx3ke7JmMZ9AQmgy =+HHH -----END PGP SIGNATURE----- From sean at srima.eu Sun Jul 12 10:01:46 2009 From: sean at srima.eu (Sean Rima) Date: Sun, 12 Jul 2009 18:01:46 +0100 Subject: [Enigmail] Been away, Enigmail not on 2.0.0.22 In-Reply-To: <4A5A13E9.3000604@bellsouth.net> References: <4A5A11E8.3050901@srima.eu> <4A5A13E9.3000604@bellsouth.net> Message-ID: <4A5A16FA.8080605@srima.eu> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 John W. Moore III wrote: > Sean Rima wrote: > >> Been away for awhile, And Updated my Thunderbird to 2.0.0.22 but >> Enigmail does not work, is there anything I need to do > > If You installed the latest Enigmail Nightly Build then it will _not_ > work on 2.0.0.22 as the Nightly Builds began following the > Thunderbird3/SeaMonkey2 API over a week ago. > > works nicely > with 2.0.0.22pre. [IIRC the latest Tb stable release is 2.0.0.21] > > NOTE: The above Link is to a Beta version so YMMV. :) > > If You are using Shredder [Tb3.0b3] then You will need the Enigmail > Nightly Build(s). > Just stuck that on and it works with 2.0.0.22 Sean -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Gossamer Spider Web of Trust: http://www.gswot.org Comment: Contact Details http://rima.tel Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEAREIAAYFAkpaFvoACgkQydfi32iLfZjO2QCdFydDJuSAMHS8tpX/fmbXIPkp OFsAn3VstQEPDATS5kx9jaPkDZnepMN2 =qNcs -----END PGP SIGNATURE----- From maike.marrek at gmx.de Sun Jul 12 11:36:18 2009 From: maike.marrek at gmx.de (maike.marrek@gmx.de ) Date: Sun, 12 Jul 2009 20:36:18 +0200 Subject: [Enigmail] Installation enigmail addon/Seamonkey In-Reply-To: <4A577BF3.9000907@mozilla-enigmail.org> References: <20090707195459.16DB7844AB@mozdev.mozdev.org> <4A543713.9050809@hammernoch.net> <4A577BF3.9000907@mozilla-enigmail.org> Message-ID: <20090712183625.9A1258442D@mozdev.mozdev.org> > According to the Mozilla documentation, error 211 means "Installation > not started" (which is not very helpful, but all I could find). I could > imagine that you don't have the rights required to install Enigmail. > You'll need local Administrator rights for SeaMonkey 1.x to install > Enigmail. Also, make sure that the 1st start of SeaMonkey after Enigmail > is installed is done with local administrator rights. > > -Patrick As you supposed there were no problems to install enigmail with administration rights - sorry, this solution was quite one one could have solved on its own :-( Thanks a lot for your support! Maike From brusefamelion at gmail.com Sun Jul 12 12:00:06 2009 From: brusefamelion at gmail.com (David) Date: Sun, 12 Jul 2009 15:00:06 -0400 Subject: [Enigmail] Encrypting saved messages Message-ID: <4A5A32B6.4050001@gmail.com> Using Enigmail and Thunderbird 3.0b3pre. Emails to be 'sent later' as saved encrypted. Is there a feature/setting somewhere that will save 'saved' emails encrypted? If not who/how do I ask for this feature. :-) -- David From jmoore3rd at bellsouth.net Sun Jul 12 12:58:35 2009 From: jmoore3rd at bellsouth.net (John W. Moore III) Date: Sun, 12 Jul 2009 15:58:35 -0400 Subject: [Enigmail] Encrypting saved messages In-Reply-To: <4A5A32B6.4050001@gmail.com> References: <4A5A32B6.4050001@gmail.com> Message-ID: <4A5A406B.7050505@bellsouth.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 David wrote: > Using Enigmail and Thunderbird 3.0b3pre. > > Emails to be 'sent later' as saved encrypted. > > Is there a feature/setting somewhere that will save 'saved' emails > encrypted? The outbox.xpi Extension/Add-On, when installed, will 'process' messages after clicking 'Send Later' and before storing them in 'Unsent Messages' folder. JOHN ;) Timestamp: Sunday 12 Jul 2009, 15:58 --400 (Eastern Daylight Time) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10-svn5068: (MingW32) Comment: Public Key at: http://tinyurl.com/8cpho Comment: Gossamer Spider Web of Trust: http://www.gswot.org Comment: Personal Web Page: http://tinyurl.com/yzhbhx iQEcBAEBCgAGBQJKWkBnAAoJEBCGy9eAtCsPk0gH/iVT0rhVS5/Oa39skv9pNUhe kCB3GjLamLfj1dyhu4NRERDQyOz8B8ZzL91AV1gAsY4rBIqvN+97iXdNwTTlkWHR 7P+HZeTAZOWAJSVIrd4iGFTbc6wRZJ6e2lG7CSkjAxaOF0E3Su5USs3dY02RUzb2 M3N2KaPlUFaG1zMPwJTQjozy6C01TdTNN68kSxfFasdGs+8SVhOT4gvIXv54xs52 tUcbnvQJj7avWhpv8jdEjRLBTvwt4F7FuWsLUPU7XMldcN58etrmNAzUURLrsl2P WzpKC7ilBw9HBp96j4iIZ1Zde5OOLnYc3az2r6GYPFQU7TfubYGOhrVu3Q/LQ4Y= =ohcb -----END PGP SIGNATURE----- From brusefamelion at gmail.com Sun Jul 12 13:51:24 2009 From: brusefamelion at gmail.com (David) Date: Sun, 12 Jul 2009 16:51:24 -0400 Subject: [Enigmail] Encrypting saved messages In-Reply-To: <4A5A406B.7050505@bellsouth.net> References: <4A5A32B6.4050001@gmail.com> <4A5A406B.7050505@bellsouth.net> Message-ID: <4A5A4CCC.7060404@gmail.com> On 7/12/2009 3:58 PM, John W. Moore III wrote: > David wrote: >> Using Enigmail and Thunderbird 3.0b3pre. > >> Emails to be 'sent later' as saved encrypted. > >> Is there a feature/setting somewhere that will save 'saved' emails >> encrypted? > > The outbox.xpi Extension/Add-On, when installed, will 'process' messages > after clicking 'Send Later' and before storing them in 'Unsent Messages' > folder. > > JOHN ;) > Timestamp: Sunday 12 Jul 2009, 15:58 --400 (Eastern Daylight Time) _______________________________________________ Enigmail mailing list Enigmail at mozdev.org https://www.mozdev.org/mailman/listinfo/enigmail I have found this and downloaded it from the developers site. But it fails to install here with this error: see attached Suggestions please. -- David -------------- next part -------------- A non-text attachment was scrubbed... Name: Capture.JPG Type: image/jpeg Size: 22799 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From olav at mozilla-enigmail.org Sun Jul 12 13:52:26 2009 From: olav at mozilla-enigmail.org (Olav Seyfarth) Date: Sun, 12 Jul 2009 22:52:26 +0200 Subject: [Enigmail] Encrypting saved messages In-Reply-To: <4A5A32B6.4050001@gmail.com> References: <4A5A32B6.4050001@gmail.com> Message-ID: <4A5A4D0A.8020401@mozilla-enigmail.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi David, > Is there a feature/setting somewhere that will save 'saved' emails > encrypted? Enigmail should ask you whether to save drafts/to-be-sent mails encryptedly. If not I assume that you once checked "don't save encrypted" along with "do not ask me again". Please check your preferences (in prefs.js while TB is not running) and just delete lines for prefs you'd like to be asked again. Olav -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12-svn5008 (MingW32) Comment: Diese ist eine Digitale Signatur nach OpenPGP-Standard Comment: http://privat.seyfarth.de/olav/schluessel.html iEYEAREIAAYFAkpaTQkACgkQL/NBt8fdKe3s2QCdHIAX0L6UrKq9mfP5cl1fbJ9a IHcAn3dUHK417Z0UjT5/YVBoG4kAHt/1 =IMPn -----END PGP SIGNATURE----- From brusefamelion at gmail.com Sun Jul 12 14:30:11 2009 From: brusefamelion at gmail.com (David) Date: Sun, 12 Jul 2009 17:30:11 -0400 Subject: [Enigmail] Encrypting saved messages In-Reply-To: <4A5A4D0A.8020401@mozilla-enigmail.org> References: <4A5A32B6.4050001@gmail.com> <4A5A4D0A.8020401@mozilla-enigmail.org> Message-ID: <4A5A55E3.4070209@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 7/12/2009 4:52 PM, Olav Seyfarth wrote: > Hi David, > >> Is there a feature/setting somewhere that will save 'saved' emails >> encrypted? > > Enigmail should ask you whether to save drafts/to-be-sent mails encryptedly. > If not I assume that you once checked "don't save encrypted" along with "do > not ask me again". Please check your preferences (in prefs.js while TB is not > running) and just delete lines for prefs you'd like to be asked again. > > Olav Thank you. Would you have any idea *exactly* what the phrase is in prefs.js that I am looking for here? - -- David -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) iEYEARECAAYFAkpaVeIACgkQzrAMrEP3F1o3tQCfeuKQDiqjAxO95lfiqYMeTzoX eKcAmwd/+njOt+bFELV3ZaSjSQ1KcSWW =m4cq -----END PGP SIGNATURE----- From jmoore3rd at bellsouth.net Sun Jul 12 16:09:05 2009 From: jmoore3rd at bellsouth.net (John W. Moore III) Date: Sun, 12 Jul 2009 19:09:05 -0400 Subject: [Enigmail] Encrypting saved messages In-Reply-To: <4A5A4CCC.7060404@gmail.com> References: <4A5A32B6.4050001@gmail.com> <4A5A406B.7050505@bellsouth.net> <4A5A4CCC.7060404@gmail.com> Message-ID: <4A5A6D11.8010304@bellsouth.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 David wrote: > I have found this and downloaded it from the developers site. But it > fails to install here with this error: see attached > > Suggestions please. Yes, this is because the Developers haven't 'caught up' with Tb3.0 yet. Works fine in 2.0.0.22pre which is a main reason why I switched back for "production work." :) Due to the radical change in the API many Extension/Add-On Authors have yet to turn their attention toward Thunderbird 3 or SeaMonkey 2. Until such time as there is an 'Official Release' of Tb3 living without various customizations is the price that must be paid for running betas. Patrick is to be commended for choosing to pursue Enigmail development with an eye toward the 'future' of Mozilla Messaging. JOHN ;) Timestamp: Sunday 12 Jul 2009, 19:08 --400 (Eastern Daylight Time) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10-svn5068: (MingW32) Comment: Public Key at: http://tinyurl.com/8cpho Comment: Gossamer Spider Web of Trust: http://www.gswot.org Comment: Personal Web Page: http://tinyurl.com/yzhbhx iQEcBAEBCgAGBQJKWm0PAAoJEBCGy9eAtCsPdqsH/2oZxieC/N/ef29i7C8ZPXHB rhTnHyvRzJcNhtLc90Y05ca4dKJlQ4fya8EIs4KffSrRqBo+rsmW6dCJtLL8Udfx 36wEpF3bk0X127dbsPhtRP/xRF63qRnLp+y/pO5gu5vfgTyldz9tgA8fBVV/Lsmv nwTKTdn+Jniz/EFYuzkiGsEZ+QjdKkwIgT0KxUNaTGB1edgyfS6l3lPlqwn5GzHR ctGNQOUfR0UMMPZTY4DlRjvNvbuA4c+UKTGMR704G8vZsXfr8YOzS1yYmzvWbt9E mOzwwBJ0jsB7+mwbDJPPTlmWkEvOpFtdZEKA4ja0dBSVCWDtoGq6DubKUpSK+Zs= =XgSM -----END PGP SIGNATURE----- From brusefamelion at gmail.com Sun Jul 12 18:18:59 2009 From: brusefamelion at gmail.com (David) Date: Sun, 12 Jul 2009 21:18:59 -0400 Subject: [Enigmail] Encrypting saved messages In-Reply-To: <4A5A6D11.8010304@bellsouth.net> References: <4A5A32B6.4050001@gmail.com> <4A5A406B.7050505@bellsouth.net> <4A5A4CCC.7060404@gmail.com> <4A5A6D11.8010304@bellsouth.net> Message-ID: <4A5A8B83.9000902@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 7/12/2009 7:09 PM, John W. Moore III wrote: > David wrote: > >> I have found this and downloaded it from the developers site. But it >> fails to install here with this error: see attached > >> Suggestions please. > > Yes, this is because the Developers haven't 'caught up' with Tb3.0 yet. > Works fine in 2.0.0.22pre which is a main reason why I switched back > for "production work." :) > > Due to the radical change in the API many Extension/Add-On Authors have > yet to turn their attention toward Thunderbird 3 or SeaMonkey 2. Until > such time as there is an 'Official Release' of Tb3 living without > various customizations is the price that must be paid for running betas. > Patrick is to be commended for choosing to pursue Enigmail development > with an eye toward the 'future' of Mozilla Messaging. > > JOHN ;) > Timestamp: Sunday 12 Jul 2009, 19:08 --400 (Eastern Daylight Time) Indeed._______________________________________________ Enigmail mailing list Enigmail at mozdev.org https://www.mozdev.org/mailman/listinfo/enigmail - -- David -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) iEYEARECAAYFAkpai4MACgkQzrAMrEP3F1p7ygCfQhFQczGj/T/YGO5bJz5IxJAL KfEAnAx7cAzu0N4o7rtiSwLm7VQQMzgp =1H3A -----END PGP SIGNATURE----- From olav at mozilla-enigmail.org Mon Jul 13 01:32:18 2009 From: olav at mozilla-enigmail.org (Olav Seyfarth) Date: Mon, 13 Jul 2009 10:32:18 +0200 Subject: [Enigmail] Encrypting saved messages In-Reply-To: <4A5A55E3.4070209@gmail.com> References: <4A5A32B6.4050001@gmail.com> <4A5A4D0A.8020401@mozilla-enigmail.org> <4A5A55E3.4070209@gmail.com> Message-ID: <4A5AF112.3010208@mozilla-enigmail.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi David, > Thank you. Would you have any idea *exactly* what the phrase is in > prefs.js that I am looking for here? extensions.enigmail.saveEncrypted Olav -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12-svn5008 (MingW32) Comment: Diese ist eine Digitale Signatur nach OpenPGP-Standard Comment: http://privat.seyfarth.de/olav/schluessel.html iEYEAREIAAYFAkpa8REACgkQL/NBt8fdKe3w9gCgkeBbb5ii5w/77ETn6fgmAKsx s6cAoKK1qDF5dVOd+k8m8DGSZzSCLU1P =1q1J -----END PGP SIGNATURE----- From brusefamelion at gmail.com Mon Jul 13 04:02:45 2009 From: brusefamelion at gmail.com (David) Date: Mon, 13 Jul 2009 07:02:45 -0400 Subject: [Enigmail] Encrypting saved messages In-Reply-To: <4A5AF112.3010208@mozilla-enigmail.org> References: <4A5A32B6.4050001@gmail.com> <4A5A4D0A.8020401@mozilla-enigmail.org> <4A5A55E3.4070209@gmail.com> <4A5AF112.3010208@mozilla-enigmail.org> Message-ID: <4A5B1455.2060604@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 7/13/2009 4:32 AM, Olav Seyfarth wrote: > Hi David, > >> Thank you. Would you have any idea *exactly* what the phrase is in >> prefs.js that I am looking for here? > > extensions.enigmail.saveEncrypted Thank you. I do not actually have a 'prefs.js' but I do have two 'enigmail.js' files. They are very similar but not identical. One, the shorter one, is in: C:\Users\David\AppData\Roaming\Thunderbird\Profiles\u78d8n2v.default\extensions\{847b3a00-7ab1-11d4-8f02-006008948af5}\defaults\pref it is titled /* Default pref values for Enigmail */ and contains // show "save draft encrypted" message (and remember selected state) pref("extensions.enigmail.saveEncrypted",0); The other, longer, one is in: C:\Users\David\AppData\Roaming\Thunderbird\Profiles\u78d8n2v.default\extensions\{847b3a00-7ab1-11d4-8f02-006008948af5}\defaults\preferences /* Default pref values for Enigmail */// the last configured Enigmail version pref (all one line) and it contains: ("extensions.enigmail.recipientsSelection",2); // show "save draft encrypted" message (and remember selected state) pref("extensions.enigmail.saveEncrypted",0) I appears that saving 'draft' emails requires that the account settings have to be set to always sign and always encrypt. That signs all drafts and encrypts them of course. Even if there is no key for the 'recipient' that the email is going to. I have no idea what key Enigmail uses but I assume mine. That is not going to be acceptable I think. Unless this saves the draft encrypted and then sends the email unencrypted. That will require a lot of 'per-recipient' rules. :-) - -- David -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) iEYEARECAAYFAkpbFFUACgkQzrAMrEP3F1pedACfd7O4+J1ba00PnhmUYUOzXyi8 EH0AnjqbjcaZ0UAJ66T22QKjy2huvUKx =R4cf -----END PGP SIGNATURE----- From olav at mozilla-enigmail.org Mon Jul 13 04:11:16 2009 From: olav at mozilla-enigmail.org (Olav Seyfarth) Date: Mon, 13 Jul 2009 13:11:16 +0200 Subject: [Enigmail] Encrypting saved messages In-Reply-To: <4A5B1455.2060604@gmail.com> References: <4A5A32B6.4050001@gmail.com> <4A5A4D0A.8020401@mozilla-enigmail.org> <4A5A55E3.4070209@gmail.com> <4A5AF112.3010208@mozilla-enigmail.org> <4A5B1455.2060604@gmail.com> Message-ID: <4A5B1654.6060803@mozilla-enigmail.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi David, > extensions\{847b3a00-7ab1-11d4-8f02-006008948af5}\defaults is the wrong file: It's the default preferences, not *your* preferences. You should look in u78d8n2v.default directly. Olav -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12-svn5008 (MingW32) Comment: Diese ist eine Digitale Signatur nach OpenPGP-Standard Comment: http://privat.seyfarth.de/olav/schluessel.html iEYEAREIAAYFAkpbFlIACgkQL/NBt8fdKe1AywCeLeftCl3JoVe7EE1CFt6AOvaD zY8Ani4TXZmv2dvkOAxiV7I6oh6qO28j =//No -----END PGP SIGNATURE----- From brusefamelion at gmail.com Mon Jul 13 05:30:42 2009 From: brusefamelion at gmail.com (David) Date: Mon, 13 Jul 2009 08:30:42 -0400 Subject: [Enigmail] Encrypting saved messages In-Reply-To: <4A5B1654.6060803@mozilla-enigmail.org> References: <4A5A32B6.4050001@gmail.com> <4A5A4D0A.8020401@mozilla-enigmail.org> <4A5A55E3.4070209@gmail.com> <4A5AF112.3010208@mozilla-enigmail.org> <4A5B1455.2060604@gmail.com> <4A5B1654.6060803@mozilla-enigmail.org> Message-ID: <4A5B28F2.8000308@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 7/13/2009 7:11 AM, Olav Seyfarth wrote: > Hi David, > >> extensions\{847b3a00-7ab1-11d4-8f02-006008948af5}\defaults > > is the wrong file: It's the default preferences, not *your* preferences. > You should look in u78d8n2v.default directly. I apologize for being so dense but this feature does not appear to work for me as I thought that it would work. Or more likely I do not understand just how it works. The line extensions.enigmail.saveEncrypted is set to 1 if I have my email address settings set to sign and encrypt every draft or email that is saved or sent even if the recipient does not have a key. Since it asks for *my* passpharse when saving I assume that it uses my key. This does however offer me the opportunity to create a per-recipient rule before sending an encrypted email to a recipient that can not decrypt it. It is not exactly what I had expected. I was thinking of a system that would only encrypt emails to recipients whose keys I have in my keyring. Perhaps this way is a better way. Once again. Thank you for your help. - -- David -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) iEYEARECAAYFAkpbKPIACgkQzrAMrEP3F1ppkQCfZRcLGN4JVvzME5rMv5ic8kSs wO8AoIYYWAwl49dKHCiYodLz+hoA+lr/ =KBca -----END PGP SIGNATURE----- From olav at mozilla-enigmail.org Mon Jul 13 05:59:42 2009 From: olav at mozilla-enigmail.org (Olav Seyfarth) Date: Mon, 13 Jul 2009 14:59:42 +0200 Subject: [Enigmail] Encrypting saved messages In-Reply-To: <4A5B28F2.8000308@gmail.com> References: <4A5A32B6.4050001@gmail.com> <4A5A4D0A.8020401@mozilla-enigmail.org> <4A5A55E3.4070209@gmail.com> <4A5AF112.3010208@mozilla-enigmail.org> <4A5B1455.2060604@gmail.com> <4A5B1654.6060803@mozilla-enigmail.org> <4A5B28F2.8000308@gmail.com> Message-ID: <4A5B2FBE.3010907@mozilla-enigmail.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi David, > The line extensions.enigmail.saveEncrypted is set to 1 if I have > my email address settings set to sign and encrypt every draft or email > that is saved or sent even if the recipient does not have a key. Since > it asks for *my* passpharse when saving I assume that it uses my key. Not 100% correct: Enigmail/GnuPG cannot encrpyt to someone you don't have the public key from. Enigmail asking yor your passphrase is beecause you set it to *sign* all your outgoing mail. > This does however offer me the opportunity to create a per-recipient > rule before sending an encrypted email to a recipient that can not > decrypt it. Per receipient rules are necessary if a receipient (here: one email address) has more than one encryption key (residing in one ore more main keys) and if you write to a group of people (a mailing list) that you want all individual receipients be be able to decrypt. Of to set Enigmail to not or always sign or encrypt to somebody. The per receipient rules are applied last (when sending) so they are not meant to set defaults. > It is not exactly what I had expected. I was thinking of a system that > would only encrypt emails to recipients whose keys I have in my keyring. Maybe http://enigmail.mozdev.org/documentation/advanced.php#keySel is what you are looking for. You must enable "Display expert settings" in Enigmail basic preferences: http://enigmail.mozdev.org/documentation/basic.php Olav -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12-svn5008 (MingW32) Comment: Diese ist eine Digitale Signatur nach OpenPGP-Standard Comment: http://privat.seyfarth.de/olav/schluessel.html iEYEAREIAAYFAkpbL74ACgkQL/NBt8fdKe2UbwCgqXTsNmOGCISoI9Oz/vUlC0CX TgUAoKaHsenZXxvRNILS6m0v/lxtM1h/ =Q+rC -----END PGP SIGNATURE----- From abuse at clean-mx.de Mon Jul 13 06:21:03 2009 From: abuse at clean-mx.de (Gerhard W. Recher (abuse)) Date: Mon, 13 Jul 2009 15:21:03 +0200 Subject: [Enigmail] Thunderbird Message filter with forwards fails In-Reply-To: <4A5B2FBE.3010907@mozilla-enigmail.org> References: <4A5A32B6.4050001@gmail.com> <4A5A4D0A.8020401@mozilla-enigmail.org> <4A5A55E3.4070209@gmail.com> <4A5AF112.3010208@mozilla-enigmail.org> <4A5B1455.2060604@gmail.com> <4A5B1654.6060803@mozilla-enigmail.org> <4A5B28F2.8000308@gmail.com> <4A5B2FBE.3010907@mozilla-enigmail.org> Message-ID: <4A5B34BF.7040408@clean-mx.de> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi my filter contains a rule: |version="8" logging="no" name="test forward" enabled="yes" type="1" action="Forward" actionValue="person at domain.tld" action="Move to folder" actionValue="imap://abuse%40clean-mx.de at ksrv8.netpilot.net/tobi" condition="OR (from,contains,person at anotherdomain.tld)" | If i Install Enigma these forwards will produce a a messagebox "sending failed please check your settings..." If i Deinstall enigma (deactivationg does not help !) all things are fine. tb version 2.0.0.022 on win xp/sp3 and latest enigma plugin. 0.95.7-tb+sm any ideas ? - -- Gerhard -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQEcBAEBAgAGBQJKWzS/AAoJEBTGcx9kwGtzEuoIAI+w1VVzdCxROvxhcAbUbSdD Vpc2vEfnxWr+yCBMiP89v8O9O1grbFeYSQKs97XnCCmDXt00z0no1n62qRaCQfi5 FtTOWKoqjQKf7O8XA10jsxCeBBHqDQn4H7K8/7jBdLTAcpY9DYrfVP75YUIvp+u/ k0+aS4Ua9HqsjOaFwNO6uwkOqJW6eZoC5DK8z1qDp0ZI8v4fFvxekgBC4RWwm1cu c0GM3pX0OqPYZNh/9ZS74S8Od60boUtA787RKRXKTStpFbMyWe1FqYpG9+GMSEUT 7APUb0z/Z21Iul51JYDgA560hCxIneMJJ4G+jHUf4bJZqAbyhjQiV3E56NoL/LQ= =B+SL -----END PGP SIGNATURE----- From abuse at clean-mx.de Mon Jul 13 06:27:36 2009 From: abuse at clean-mx.de (Gerhard W. Recher (abuse)) Date: Mon, 13 Jul 2009 15:27:36 +0200 Subject: [Enigmail] displaying decryptet message with wrong mime type Message-ID: <4A5B3648.6080201@clean-mx.de> Hi one of our contacts has a brain dead cryptogateway this one produces multiple text/plain encrypted parts but the last text/plain part is a real text/html part. so Thunderbird displays html code and is *not* rendering this... is this a problem of enigma or of thunderbird in common ? raw message data looks like this: |.. .. other headers .. Content-Type: multipart/mixed; Boundary="0__=4EBBFF5CDFD6A7728f9e8a93df938690918c4EBBFF5CDFD6A772" - --0__=4EBBFF5CDFD6A7728f9e8a93df938690918c4EBBFF5CDFD6A772 Content-Type: multipart/related; Boundary="1__=4EBBFF5CDFD6A7728f9e8a93df938690918c4EBBFF5CDFD6A772" - --1__=4EBBFF5CDFD6A7728f9e8a93df938690918c4EBBFF5CDFD6A772 Content-Type: multipart/alternative; Boundary="2__=4EBBFF5CDFD6A7728f9e8a93df938690918c4EBBFF5CDFD6A772" - --2__=4EBBFF5CDFD6A7728f9e8a93df938690918c4EBBFF5CDFD6A772 Content-Type: text/plain Content-Transfer-Encoding: 7bit - -----BEGIN PGP MESSAGE----- Version: GnuPG v1.4.2 (GNU/Linux) hQIOA5gtC4 wgJGkrEAf/fvr3XUGL028Xdc4e8KPbbeszXWdEqRQMtyd+rTCkIqb3 ... ... decypted is this the real test/plain part of this message .... qphsxRApqaV4scWLit6B3NN7Oc0V5nfo2MBJN7JV4JA= =cmUx - -----END PGP MESSAGE----- - --2__=4EBBFF5CDFD6A7728f9e8a93df938690918c4EBBFF5CDFD6A772 Content-Type: text/plain Content-Transfer-Encoding: 7bit - -----BEGIN PGP MESSAGE----- Version: GnuPG v1.4.2 (GNU/Linux) >>>>>>>>>> this decypted part is the text/html part of this message >>>>>>>>>>>>>>>>>>>>>>>>>>>> - -----END PGP MESSAGE----- - --2__=4EBBFF5CDFD6A7728f9e8a93df938690918c4EBBFF5CDFD6A772-- - --1__=4EBBFF5CDFD6A7728f9e8a93df938690918c4EBBFF5CDFD6A772 Content-Disposition: attachment; filename="graycol.gif.pgp" Content-Type: application/octet-stream; name="graycol.gif.pgp" Content-Transfer-Encoding: 7bit - -----BEGIN PGP MESSAGE----- Version: GnuPG v1.4.2 (GNU/Linux) ... .. | From patrick at mozilla-enigmail.org Mon Jul 13 07:02:09 2009 From: patrick at mozilla-enigmail.org (Patrick Brunschwig) Date: Mon, 13 Jul 2009 16:02:09 +0200 Subject: [Enigmail] Thunderbird Message filter with forwards fails In-Reply-To: <4A5B34BF.7040408@clean-mx.de> References: <4A5A32B6.4050001@gmail.com> <4A5A4D0A.8020401@mozilla-enigmail.org> <4A5A55E3.4070209@gmail.com> <4A5AF112.3010208@mozilla-enigmail.org> <4A5B1455.2060604@gmail.com> <4A5B1654.6060803@mozilla-enigmail.org> <4A5B28F2.8000308@gmail.com> <4A5B2FBE.3010907@mozilla-enigmail.org> <4A5B34BF.7040408@clean-mx.de> Message-ID: <4A5B3E61.6070508@mozilla-enigmail.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Gerhard W. Recher (abuse) wrote: > hi > > > my filter contains a rule: > > |version="8" > logging="no" > name="test forward" > enabled="yes" > type="1" > action="Forward" > actionValue="person at domain.tld" > action="Move to folder" > actionValue="imap://abuse%40clean-mx.de at ksrv8.netpilot.net/tobi" > condition="OR (from,contains,person at anotherdomain.tld)" | > > > > If i Install Enigma these forwards will produce a a messagebox > "sending failed please check your settings..." > If i Deinstall enigma (deactivationg does not help !) all things are fine. > > tb version 2.0.0.022 on win xp/sp3 and latest enigma plugin. 0.95.7-tb+sm > > any ideas ? Forwarding-rules with Enigmail configured to sign/encrypt by default is currently not supported. - -Patrick -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEVAwUBSls+YXcOpHodsOiwAQhQgQgAi5uBKD68SnaZwEziofLIHMnlBSPDyA4s DDLookMtJqtIVYC86IYbS9YgogUSRyUo9Lk01LW/P8hEm4dBS+usOACbDvJnq1Af 3oO8ZIKkSZBxxft9NS0g6Z0RUVV15bfFRYnmoj5pGF+pJFrAqGQVKcSU/hOdiwCI kqtrXClM0TDAaXPwUzyiKNYhpBROeQWBWQA7DFAck0ttp7NW+CoZPo0Wq6b53nEm plHCbXPVgXpJ6/3p+/7tcCnhbDFNzII/BfybdJ+5FVm9MQdG+bhCOw3GafPoWxGt pob8XTWtuBif97qRGclZruKJgDlpeRtRvLRq7Ez9Z+xedTCckYrHyg== =vzSC -----END PGP SIGNATURE----- From brusefamelion at gmail.com Mon Jul 13 07:47:35 2009 From: brusefamelion at gmail.com (David) Date: Mon, 13 Jul 2009 10:47:35 -0400 Subject: [Enigmail] Encrypting saved messages In-Reply-To: <4A5B2FBE.3010907@mozilla-enigmail.org> References: <4A5A32B6.4050001@gmail.com> <4A5A4D0A.8020401@mozilla-enigmail.org> <4A5A55E3.4070209@gmail.com> <4A5AF112.3010208@mozilla-enigmail.org> <4A5B1455.2060604@gmail.com> <4A5B1654.6060803@mozilla-enigmail.org> <4A5B28F2.8000308@gmail.com> <4A5B2FBE.3010907@mozilla-enigmail.org> Message-ID: <4A5B4907.7010506@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 7/13/2009 8:59 AM, Olav Seyfarth wrote: > Hi David, > >> The line extensions.enigmail.saveEncrypted is set to 1 if I have >> my email address settings set to sign and encrypt every draft or email >> that is saved or sent even if the recipient does not have a key. Since >> it asks for *my* passpharse when saving I assume that it uses my key. > > Not 100% correct: Enigmail/GnuPG cannot encrpyt to someone you don't have > the public key from. Enigmail asking yor your passphrase is beecause you > set it to *sign* all your outgoing mail. Sir: When I have all four checkboxes marked Sign-non-encrypted Sign encrypted Encrypt messages by default Use PGP/MIME *or* just Encrypt messages by default marked Thunderbird/Enigmail will save a draft email to any and all recipients encrypted. Even if the recipient does *not* have a key. Enigmail *does* ask for a key when the draft is loaded and a 'send' is selected. >> This does however offer me the opportunity to create a per-recipient >> rule before sending an encrypted email to a recipient that can not >> decrypt it. > > Per receipient rules are necessary if a receipient (here: one email address) > has more than one encryption key (residing in one ore more main keys) and if > you write to a group of people (a mailing list) that you want all individual > receipients be be able to decrypt. Of to set Enigmail to not or always sign > or encrypt to somebody. The per receipient rules are applied last (when > sending) so they are not meant to set defaults. Which is as I expected. But what I had thought that I would see was that drafts of emails to recipients that *do not have a key* would be saved and *not* encrypted. And that drafts of emails to recipients that *do have a key* would be saved and encrypted. Not *all* drafts. >> It is not exactly what I had expected. I was thinking of a system that >> would only encrypt emails to recipients whose keys I have in my keyring. > > Maybe http://enigmail.mozdev.org/documentation/advanced.php#keySel is what > you are looking for. You must enable "Display expert settings" in Enigmail > basic preferences: http://enigmail.mozdev.org/documentation/basic.php I am in no way an expert with Enigmail. But I have been a user for several years. I thought that I had this working the way I described above at one time. But I must be mistaken. Thank you again. - -- David -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) iEYEARECAAYFAkpbSQcACgkQzrAMrEP3F1puvwCfbLSqEyNYySvnrn3Yj7X23MGI MLUAn01iSjJVz6Oe1uxu7bmEsE8KAYUB =sKoc -----END PGP SIGNATURE----- From jamesrome at gmail.com Mon Jul 13 07:49:16 2009 From: jamesrome at gmail.com (James Rome) Date: Mon, 13 Jul 2009 10:49:16 -0400 Subject: [Enigmail] Troubles in Windows 7 Message-ID: <4A5B496C.2060904@gmail.com> I am running the nightly build of Enigmail for Thunderbird 3b2 inside Windows 7 running inside Parallels on my MacPro. I pointed Enigmail to C:\cygwin\bin\gpg.exe. But when I get an encrypted massage, I enter the password for the private key, and nothing happens--the message is still displayed encrypted. The error console says: enigmail> C:\cygwin\bin\gpg.exe --charset utf8 --batch --no-tty --status-fd 2 -- decrypt --passphrase-fd 0 --no-use-agent gpg: WARNING: using insecure memory! gpg: please see http://www.gnupg.org/faq.html for more information gpg: malformed CRC enigmail.js: Enigmail.fixExitCode: Using gpg and exit code is 256. You seem to u se cygwin-gpg, activating countermeasures. enigmail.js: Enigmail.fixExitCode: Changing exitCode 256->0 enigmail.js: Enigmail.decryptMessageEnd: Error in command execution Everyone else canj decrypt these messages. A also tried the gpg inside gpg4win, but with similar results. I can decrypt messages that are attachments OK. But if I try to decrypt and display them, I always get a permissions error while making the temp file. How do I get this working again? Thanks, Jim Rome From rjh at sixdemonbag.org Mon Jul 13 07:52:54 2009 From: rjh at sixdemonbag.org (Robert J. Hansen) Date: Mon, 13 Jul 2009 10:52:54 -0400 Subject: [Enigmail] Troubles in Windows 7 In-Reply-To: <4A5B496C.2060904@gmail.com> References: <4A5B496C.2060904@gmail.com> Message-ID: > I am running the nightly build of Enigmail for Thunderbird 3b2 inside > Windows 7 running inside Parallels on my MacPro. You're running an unreleased version of Enigmail on an unreleased version of Thunderbird on an unreleased version of Windows. The solution is to run a released version of Enigmail on a released version of Thunderbird on a released version of Windows. We make no guarantees about the nightly builds, about Thunderbird 3.0 compatibility, or Windows 7 compatibility. From olav at mozilla-enigmail.org Mon Jul 13 07:58:59 2009 From: olav at mozilla-enigmail.org (Olav Seyfarth) Date: Mon, 13 Jul 2009 16:58:59 +0200 Subject: [Enigmail] Encrypting saved messages In-Reply-To: <4A5B4907.7010506@gmail.com> References: <4A5A32B6.4050001@gmail.com> <4A5A4D0A.8020401@mozilla-enigmail.org> <4A5A55E3.4070209@gmail.com> <4A5AF112.3010208@mozilla-enigmail.org> <4A5B1455.2060604@gmail.com> <4A5B1654.6060803@mozilla-enigmail.org> <4A5B28F2.8000308@gmail.com> <4A5B2FBE.3010907@mozilla-enigmail.org> <4A5B4907.7010506@gmail.com> Message-ID: <4A5B4BB3.1060803@mozilla-enigmail.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi David, > Thunderbird/Enigmail will save a draft email to any and all recipients > encrypted. Even if the recipient does *not* have a key. Enigmail *does* > ask for a key when the draft is loaded and a 'send' is selected. Enigmail will ask you for a key if you set the default to encrypt all messages. But it cannot encrypt without the receipient's key. > Which is as I expected. But what I had thought that I would see was that > drafts of emails to recipients that *do not have a key* would be saved > and *not* encrypted. This is what you can influence with the pref extensions.enigmail.saveEncrypted > And that drafts of emails to recipients that *do have a key* would be saved > and encrypted. Not *all* drafts. I see your point. But it's deeper that that. What should happpen with a message that has two receipients - one with a key and one without? Enigmail will only decide/ask upon sending (including Outbox), not for saving drafts. If encryption was set before saving, it will ask you whether to save encryptedly or not. But it will not do opportunistic encryption. > I am in no way an expert with Enigmail. But I have been a user for > several years. I thought that I had this working the way I described > above at one time. But I must be mistaken. I did not want to offend you. Please keep in mind that I am not a native speaker. Olav -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12-svn5008 (MingW32) Comment: Diese ist eine Digitale Signatur nach OpenPGP-Standard Comment: http://privat.seyfarth.de/olav/schluessel.html iEYEAREIAAYFAkpbS7IACgkQL/NBt8fdKe3RGACfXJHTOEUzApm3T/RqeudGwiS9 eU8AoMQlyDnViE7auz29LsWZIGd+2iq0 =1vW3 -----END PGP SIGNATURE----- From olav at mozilla-enigmail.org Mon Jul 13 08:03:11 2009 From: olav at mozilla-enigmail.org (Olav Seyfarth) Date: Mon, 13 Jul 2009 17:03:11 +0200 Subject: [Enigmail] Troubles in Windows 7 In-Reply-To: <4A5B496C.2060904@gmail.com> References: <4A5B496C.2060904@gmail.com> Message-ID: <4A5B4CAF.8080606@mozilla-enigmail.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi James, I set up latest GPG4Win 1.9.x beta along with TB3 latest-comm-1.9.1 and Enigmail nightly. Works like a charm for me. I assume that your CygWin Environment causes the problems. Try to sanitize env vars and GnuPG registry and give it another try. I doubt that it has anything to do with your virtual machine. Olav -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12-svn5008 (MingW32) Comment: Diese ist eine Digitale Signatur nach OpenPGP-Standard Comment: http://privat.seyfarth.de/olav/schluessel.html iEYEAREIAAYFAkpbTK0ACgkQL/NBt8fdKe1NkQCeIxFrKDn7rTzOgq2Ny5rW0p8E tTEAn33wwbmSmLrvnm5T8KsfpnfIk5qg =HxiZ -----END PGP SIGNATURE----- From brusefamelion at gmail.com Mon Jul 13 08:46:42 2009 From: brusefamelion at gmail.com (David) Date: Mon, 13 Jul 2009 11:46:42 -0400 Subject: [Enigmail] Encrypting saved messages In-Reply-To: <4A5B4BB3.1060803@mozilla-enigmail.org> References: <4A5A32B6.4050001@gmail.com> <4A5A4D0A.8020401@mozilla-enigmail.org> <4A5A55E3.4070209@gmail.com> <4A5AF112.3010208@mozilla-enigmail.org> <4A5B1455.2060604@gmail.com> <4A5B1654.6060803@mozilla-enigmail.org> <4A5B28F2.8000308@gmail.com> <4A5B2FBE.3010907@mozilla-enigmail.org> <4A5B4907.7010506@gmail.com> <4A5B4BB3.1060803@mozilla-enigmail.org> Message-ID: <4A5B56E2.2000307@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 7/13/2009 10:58 AM, Olav Seyfarth wrote: > Hi David, > >> Thunderbird/Enigmail will save a draft email to any and all recipients >> encrypted. Even if the recipient does *not* have a key. Enigmail *does* >> ask for a key when the draft is loaded and a 'send' is selected. > > Enigmail will ask you for a key if you set the default to encrypt all messages. > But it cannot encrypt without the receipient's key. > >> Which is as I expected. But what I had thought that I would see was that >> drafts of emails to recipients that *do not have a key* would be saved >> and *not* encrypted. > > This is what you can influence with the pref extensions.enigmail.saveEncrypted I have seen this 'extensions.enigmail.saveEncrypted' set to 0 (zero) and to 1 (one) and to 2 (two) none of which appears to not save drafts to recipients with no key not encrypted. Any number set, with the checkbox marked, will encrypt all saved drafts. Any number set, with the checkbox unmarked, will not encrypt anything. >> And that drafts of emails to recipients that *do have a key* would be saved >> and encrypted. Not *all* drafts. > > I see your point. But it's deeper that that. What should happpen with a message > that has two receipients - one with a key and one without? Enigmail will only > decide/ask upon sending (including Outbox), not for saving drafts. If encryption > was set before saving, it will ask you whether to save encryptedly or not. But > it will not do opportunistic encryption. > >> I am in no way an expert with Enigmail. But I have been a user for >> several years. I thought that I had this working the way I described >> above at one time. But I must be mistaken. > > I did not want to offend you. Please keep in mind that I am not a native > speaker. "not a native speaker"? Of course you are. Of your native language. Not mine. :-) I was not offended in any way by anything you have said. I appreciate your help. - -- David -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) iEYEARECAAYFAkpbVuEACgkQzrAMrEP3F1rUBACdEVIqLgyKKRHEDAkXbWZKSZ0x GNAAoISI6PyxcmNvfD+M+JLY5BfNY7x0 =YrbW -----END PGP SIGNATURE----- From jmoore3rd at bellsouth.net Mon Jul 13 09:23:26 2009 From: jmoore3rd at bellsouth.net (John W. Moore III) Date: Mon, 13 Jul 2009 12:23:26 -0400 Subject: [Enigmail] Troubles in Windows 7 In-Reply-To: References: <4A5B496C.2060904@gmail.com> Message-ID: <4A5B5F7E.6000103@bellsouth.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Robert J. Hansen wrote: >> I am running the nightly build of Enigmail for Thunderbird 3b2 inside >> Windows 7 running inside Parallels on my MacPro. > > You're running an unreleased version of Enigmail on an unreleased > version of Thunderbird on an unreleased version of Windows. > > The solution is to run a released version of Enigmail on a released > version of Thunderbird on a released version of Windows. > > We make no guarantees about the nightly builds, about Thunderbird 3.0 > compatibility, or Windows 7 compatibility. Everything Robert pointed out is True. That said; if You insist upon experimenting I suggest You at least move to Tb3.0b3 in addition to double checking that You have 'aimed' Enigmail correctly to gpg.exe. :-\ I am not 100% conversant on Windows 7 nor the 'Parallels' option but is it possible that the issue could be T-Bird/Enigmail is the M$ version inside Parallels and the GPG version is 'outside' Parallels in the Mac environment? :-\ JOHN ;) Timestamp: Monday 13 Jul 2009, 12:23 --400 (Eastern Daylight Time) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10-svn5068: (MingW32) Comment: Public Key at: http://tinyurl.com/8cpho Comment: Gossamer Spider Web of Trust: http://www.gswot.org Comment: Personal Web Page: http://tinyurl.com/yzhbhx iQEcBAEBCgAGBQJKW198AAoJEBCGy9eAtCsPdUkH/2uitVGUpmBpz3R70UrWerhS vombcyRYB0ohxjMvMNJ25peAJdMwC/oeHoNGNww32i3qwwSOJPnOpn6dPV1RVwCh Q/tGwCsIWV/gWS90K6KC4WyHR79F0Pfe8qhMnjs60XROUttvL+8D3ypaihuvModu S0BcSNcoWYLoWNd+aGI8qoiPw77V7xQKB6eEchAcv3efYZoZ+/nRQD/PwjQqOIqx 2SMljuWw7qA3fwUZJszkFsQcdCR7pEuMMGht1bEJ7VuGjNNiqDdE6shU8S0TgA/B zATjCeR8aZs9nr6wxwVbGm1YBv0XHuTSWrWKV235lG9YnoniEoYj8gvdKkLilAc= =9cRH -----END PGP SIGNATURE----- From jpeek at jpeek.com Sun Jul 12 21:01:36 2009 From: jpeek at jpeek.com (Jerry Peek) Date: Sun, 12 Jul 2009 21:01:36 -0700 Subject: [Enigmail] Problem with OpenPGP Setup Wizard Message-ID: <4A5AB1A0.9080107@jpeek.com> I'm running Thunderbird 2.0.0.22 under the latest Ubuntu. When I started to send a message, the OpenPGP Setup Wizard started. I chose the wizard option. The next dialog asked whether I wanted OpenPGP on all accounts or just on some. I wanted it only on one account. But I hadn't set up all accounts yet, so I clicked the "Back" button. Then I switched to the main Thunderbird window and created the other accounts. Then I came back to the OpenPGP dialog and clicked "Next" to go back to the screen where I could choose the accounts to set up. The new accounts I'd just created didn't appear in the wizard dialog, and there didn't seem to be a way to get them except to cancel and set things up manually. I suggest making the initial screen tell us that, if we move ahead, we must already have all accounts set up. Also, make the first screen a warning that we can only run the setup once -- and let us cancel at this point -- or do something else so that we're given a chance to set things up the way we want them before the wizard runs just that once. As it is, people who don't use Linux Thunderbird much will continue to be surprised by the OpenPGP dialog -- and be forced to cancel setup, as I will. Thanks for reading. Jerry From shavital at mac.com Mon Jul 13 11:01:36 2009 From: shavital at mac.com (Charly Avital) Date: Mon, 13 Jul 2009 14:01:36 -0400 Subject: [Enigmail] Troubles in Windows 7 In-Reply-To: <4A5B5F7E.6000103@bellsouth.net> References: <4A5B496C.2060904@gmail.com> <4A5B5F7E.6000103@bellsouth.net> Message-ID: <4A5B7680.3070708@mac.com> John W. Moore III wrote the following on 7/13/09 12:23 PM: [...] > I am not 100% conversant on Windows 7 nor the 'Parallels' option but is > it possible that the issue could be T-Bird/Enigmail is the M$ version > inside Parallels and the GPG version is 'outside' Parallels in the Mac > environment? :-\ I've recently upgraded to gpg4win 2.0.0rc1 [gpg (GnuPG) 2.0.12 (Gpg4win 2.0.0rc1] from gpg4win 1913, in Windows XP Pro SP3, running under VMware Fusion (I have given up Parallels), on a MacBook "Unibody" Late 2008. It runs impeccably, including GPA (which didn't function at all under the previous release). Whether Parallels or VMware, the Windows ("guest") installation runs on its own on a "virtual disk". There's an option to share functions and folders between the guest and the host (MacOSX), but this does not include GnuPG that must be installed separately in each platform. I have also gpg 2.0.12 running under Linux Ubuntu 9.04_64bits, in a separate Linux "virtual disk". There cannot be interaction or dependencies between the different installations of GnuPG. Charly From patrick at mozilla-enigmail.org Tue Jul 14 00:48:36 2009 From: patrick at mozilla-enigmail.org (Patrick Brunschwig) Date: Tue, 14 Jul 2009 09:48:36 +0200 Subject: [Enigmail] Problem with OpenPGP Setup Wizard In-Reply-To: <4A5AB1A0.9080107@jpeek.com> References: <4A5AB1A0.9080107@jpeek.com> Message-ID: <4A5C3854.4030305@mozilla-enigmail.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Jerry Peek wrote: > I'm running Thunderbird 2.0.0.22 under the latest Ubuntu. When I > started to send a message, the OpenPGP Setup Wizard started. I chose > the wizard option. > > The next dialog asked whether I wanted OpenPGP on all accounts or just > on some. I wanted it only on one account. But I hadn't set up all > accounts yet, so I clicked the "Back" button. Then I switched to the > main Thunderbird window and created the other accounts. Then I came > back to the OpenPGP dialog and clicked "Next" to go back to the screen > where I could choose the accounts to set up. > > The new accounts I'd just created didn't appear in the wizard dialog, > and there didn't seem to be a way to get them except to cancel and set > things up manually. > > I suggest making the initial screen tell us that, if we move ahead, we > must already have all accounts set up. Also, make the first screen a > warning that we can only run the setup once -- and let us cancel at this > point -- or do something else so that we're given a chance to set things > up the way we want them before the wizard runs just that once. > > As it is, people who don't use Linux Thunderbird much will continue to > be surprised by the OpenPGP dialog -- and be forced to cancel setup, as > I will. In the next version the Setup Wizard will be also available via the menu. This way it's possible to re-run it whenever you like. - -Patrick -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEVAwUBSlw3UncOpHodsOiwAQhlYwgAoiJsM/ivbC6VXO8kSFzSpM/dgLT4rcEo WhHiA4YTneeQAcG2VkoelZMo684VFjqxg4vezpG6zG0sf0cE+hohrkw6/vyzeo63 pkJRVDWvJNS1mzTmc0hs820kALYbT7Qr6TqDwhplRKjeJtREFh3YcOe1NZEwnteC 0rOUde3HoswON5Bfh1AC+y0KqhBjXyshXsxGckxcIxRIQhm8TPMpKQXuIHG2CdBn GhPJJNkezCHUIFmKSH+LkThaJ/wWNUbCP9aUWD/xkmasT3L1M6atcMrumu5oMwWW b77bIN/UrF6NDBOEQ6G8kHknWJuTc2H/QZ6Z9oiEqXjxM4X1CeoF1g== =ygbP -----END PGP SIGNATURE----- From jamesrome at gmail.com Tue Jul 14 12:10:07 2009 From: jamesrome at gmail.com (James Rome) Date: Tue, 14 Jul 2009 15:10:07 -0400 Subject: [Enigmail] Troubles in Windows 7 In-Reply-To: <4A5B4CAF.8080606@mozilla-enigmail.org> References: <4A5B4CAF.8080606@mozilla-enigmail.org> Message-ID: <4A5CD80F.8050406@gmail.com> I used the gpg4win 2.0.0rc1. And again I went back to it, picking gpg2.exe in the Enigmail. Enigmail asks me for my password, but just leaves the encrypted text showing. I have never had this problem before. Thanks, Jim Rome Hi James, I set up latest GPG4Win 1.9.x beta along with TB3 latest-comm-1.9.1 and Enigmail nightly. Works like a charm for me. I assume that your CygWin Environment causes the problems. Try to sanitize env vars and GnuPG registry and give it another try. I doubt that it has anything to do with your virtual machine. From jamesrome at gmail.com Tue Jul 14 13:35:11 2009 From: jamesrome at gmail.com (James Rome) Date: Tue, 14 Jul 2009 16:35:11 -0400 Subject: [Enigmail] Still issues with TB3 and Windows 7 Message-ID: <4A5CEBFF.7040503@gmail.com> Well, I finally got this to work. Very strange. 1) I had to go back to gpg4win 1.1.4 which has gpg.exe as opposed to gpg2.exe 2) It works with Shredder, the latest nightly, but NOT with TB3.0b2. The Enigmail setup is the same I presume for each of them since I did not have to reinstall the plugin. 3) I went back to TB 3.0b2 and it failed again. Returning to Shredder, it worked. And I installed the latest Enigmail nightly for TB3.0. Any ideas? Jim Rome From dgboles at gmail.com Wed Jul 15 07:18:41 2009 From: dgboles at gmail.com (David) Date: Wed, 15 Jul 2009 10:18:41 -0400 Subject: [Enigmail] Unverified signature error Message-ID: <4A5DE541.3080001@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 What, exactly, does this mean? And why can I not verify this signature? - ----------- OpenPGP Security Info Unverified signature gpg command line and output: C:\Program Files (x86)\GNU\GnuPG\gpg.exe gpg: Signature made 07/14/09 17:50:26 using RSA key ID 1C109517 gpg: WARNING: signature digest conflict in message gpg: Can't check signature: general error - ----------- - -- David -----BEGIN PGP SIGNATURE----- Comment: --batch iEYEARECAAYFAkpd5UEACgkQzrAMrEP3F1qzwgCeJdkBrgTPSAhFyDpFPJQfpbf2 DfYAn0mNKEGfDTO+/93Vx9MHxPX9srD+ =8bFK -----END PGP SIGNATURE----- From 2600denver at gmail.com Wed Jul 15 07:38:24 2009 From: 2600denver at gmail.com (Ringo) Date: Wed, 15 Jul 2009 10:38:24 -0400 Subject: [Enigmail] Unverified signature error In-Reply-To: <4A5DE541.3080001@gmail.com> References: <4A5DE541.3080001@gmail.com> Message-ID: <4A5DE9E0.6090909@gmail.com> I'm not sure what this means in your case, but sometimes html-formatted emails can cause bad signatures. Ringo David wrote: > What, exactly, does this mean? And why can I not verify this signature? > > ----------- > OpenPGP Security Info > > Unverified signature > > gpg command line and output: > C:\Program Files (x86)\GNU\GnuPG\gpg.exe > gpg: Signature made 07/14/09 17:50:26 using RSA key ID 1C109517 > gpg: WARNING: signature digest conflict in message > gpg: Can't check signature: general error > ----------- _______________________________________________ Enigmail mailing list Enigmail at mozdev.org https://www.mozdev.org/mailman/listinfo/enigmail From mlisten at hammernoch.net Wed Jul 15 07:41:29 2009 From: mlisten at hammernoch.net (=?ISO-8859-1?Q?Ludwig_H=FCgelsch=E4fer?=) Date: Wed, 15 Jul 2009 16:41:29 +0200 Subject: [Enigmail] Unverified signature error In-Reply-To: <4A5DE541.3080001@gmail.com> References: <4A5DE541.3080001@gmail.com> Message-ID: <4A5DEA99.1000207@hammernoch.net> David wrote on 15.07.09 16:18: > What, exactly, does this mean? And why can I not verify this signature? > > ----------- > OpenPGP Security Info > > Unverified signature > > gpg command line and output: > C:\Program Files (x86)\GNU\GnuPG\gpg.exe > gpg: Signature made 07/14/09 17:50:26 using RSA key ID 1C109517 > gpg: WARNING: signature digest conflict in message The message in question misses the "Hash: "-line in the signature part. Who or what does send/create these messages? This is not an OpenPGP compliant message. Ludwig -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 550 bytes Desc: OpenPGP digital signature URL: From dgboles at comcast.net Wed Jul 15 07:43:08 2009 From: dgboles at comcast.net (David) Date: Wed, 15 Jul 2009 10:43:08 -0400 Subject: [Enigmail] Unverified signature error Message-ID: <4A5DEAFC.2070304@comcast.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 What, exactly, does this mean? And why can I not verify this signature? - ----------- OpenPGP Security Info Unverified signature gpg command line and output: C:\Program Files (x86)\GNU\GnuPG\gpg.exe gpg: Signature made 07/14/09 17:50:26 using RSA key ID 1C109517 gpg: WARNING: signature digest conflict in message gpg: Can't check signature: general error - ----------- - -- David -----BEGIN PGP SIGNATURE----- Comment: --batch iEYEARECAAYFAkpd6vsACgkQzrAMrEP3F1rNpACZAYu1P774oCesCXMKzApR873h lcwAnRgdEyyuaR/WVo9nL4eJC/JVf7e0 =U/Vv -----END PGP SIGNATURE----- From dgboles at comcast.net Wed Jul 15 07:50:46 2009 From: dgboles at comcast.net (David) Date: Wed, 15 Jul 2009 10:50:46 -0400 Subject: [Enigmail] Unverified signature error In-Reply-To: <4A5DEA99.1000207@hammernoch.net> References: <4A5DE541.3080001@gmail.com> <4A5DEA99.1000207@hammernoch.net> Message-ID: <4A5DECC6.8010802@comcast.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 7/15/2009 10:41 AM, Ludwig H?gelsch?fer wrote: > David wrote on 15.07.09 16:18: >> What, exactly, does this mean? And why can I not verify this signature? >> >> ----------- >> OpenPGP Security Info >> >> Unverified signature >> >> gpg command line and output: >> C:\Program Files (x86)\GNU\GnuPG\gpg.exe >> gpg: Signature made 07/14/09 17:50:26 using RSA key ID 1C109517 >> gpg: WARNING: signature digest conflict in message > > The message in question misses the "Hash: "-line in > the signature part. > > Who or what does send/create these messages? This is not an OpenPGP > compliant message. > > Ludwig The message is a post/reply to the Fedora Development list made my an individual. This is the only signature that I have seen that gives this error. - -- David -----BEGIN PGP SIGNATURE----- Comment: --batch iEYEARECAAYFAkpd7MYACgkQzrAMrEP3F1pRAACgguV3fOwt7fFBxKVtLDkewJnA 4rEAmgOjScJ/XmBn666YX5ZnVO/EGSG9 =CtU2 -----END PGP SIGNATURE----- From shavital at mac.com Wed Jul 15 07:54:59 2009 From: shavital at mac.com (Charly Avital) Date: Wed, 15 Jul 2009 10:54:59 -0400 Subject: [Enigmail] Unverified signature error In-Reply-To: <4A5DE541.3080001@gmail.com> References: <4A5DE541.3080001@gmail.com> Message-ID: <4A5DEDC3.9030106@mac.com> David wrote the following on 7/15/09 10:18 AM: > What, exactly, does this mean? And why can I not verify this signature? > > ----------- > OpenPGP Security Info > > Unverified signature > > gpg command line and output: > C:\Program Files (x86)\GNU\GnuPG\gpg.exe > gpg: Signature made 07/14/09 17:50:26 using RSA key ID 1C109517 > gpg: WARNING: signature digest conflict in message > gpg: Can't check signature: general error > ----------- Please open this link which *might* provide an explanation, or at least a clue to the meaning of the warning: Does the in-line signed e-mail you were trying to verify contain a line indicating which HASH was used, like in your own post to the list: ============= -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [...etc....] ============= Charly From jmoore3rd at bellsouth.net Wed Jul 15 08:27:51 2009 From: jmoore3rd at bellsouth.net (John W. Moore III) Date: Wed, 15 Jul 2009 11:27:51 -0400 Subject: [Enigmail] Unverified signature error In-Reply-To: <4A5DECC6.8010802@comcast.net> References: <4A5DE541.3080001@gmail.com> <4A5DEA99.1000207@hammernoch.net> <4A5DECC6.8010802@comcast.net> Message-ID: <4A5DF577.60204@bellsouth.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 David wrote: > > The message is a post/reply to the Fedora Development list made my an > individual. This is the only signature that I have seen that gives this > error. It is always possible that Your 'Sender' is forcing a SHA2 Hash with a DSA Key that is _not_ DSA2 enabled. :-\ This would also create a 'Digest conflict'. JOHN ;) Timestamp: Wednesday 15 Jul 2009, 11:27 --400 (Eastern Daylight Time) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10-svn5068: (MingW32) Comment: Public Key at: http://tinyurl.com/8cpho Comment: Gossamer Spider Web of Trust: http://www.gswot.org Comment: Personal Web Page: http://tinyurl.com/yzhbhx iQEcBAEBCgAGBQJKXfV0AAoJEBCGy9eAtCsPNWIIAIDXDUbGOntx/dFXn4Au+DHf GDNMnfeYaCuM4BOLophnyDVXbkaBXfBpZikvimJESA0LmQoLvxdSIIIqA1XHAABU Y/PjR9q02Ts7y96xn4ikQr3FVs3E3j4GUStlmw5GBusARujFNinEG6fOeGkKGBZL ZwrF4j3Z9bfRC9a618bGky7IfPz7+j5hh2jk6JstkZKzd5L/lqeYxRiq538YDogS 5rV89KruVma2UdIAA+r0qGyRCVdo9GD3yySkazUVsmCCZPAB/nKbJoLOBLN+aagX +uBAG2E3MkgGLO1vI1IfskLxx0mi86QkSimhWbbuoLXKKTRjnPC4FSpRdIlgNpk= =dntV -----END PGP SIGNATURE----- From dgboles at comcast.net Wed Jul 15 08:33:46 2009 From: dgboles at comcast.net (David) Date: Wed, 15 Jul 2009 11:33:46 -0400 Subject: [Enigmail] Unverified signature error In-Reply-To: <4A5DEDC3.9030106@mac.com> References: <4A5DE541.3080001@gmail.com> <4A5DEDC3.9030106@mac.com> Message-ID: <4A5DF6DA.1000001@comcast.net> On 7/15/2009 10:54 AM, Charly Avital wrote: > David wrote the following on 7/15/09 10:18 AM: >> What, exactly, does this mean? And why can I not verify this signature? >> >> ----------- >> OpenPGP Security Info >> >> Unverified signature >> >> gpg command line and output: >> C:\Program Files (x86)\GNU\GnuPG\gpg.exe >> gpg: Signature made 07/14/09 17:50:26 using RSA key ID 1C109517 >> gpg: WARNING: signature digest conflict in message >> gpg: Can't check signature: general error >> ----------- > > Please open this link which *might* provide an explanation, or at least > a clue to the meaning of the warning: > > > > Does the in-line signed e-mail you were trying to verify contain a line > indicating which HASH was used, like in your own post to the list: > ============= > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > [...etc....] > ============= > > > Charly If you mean 'with Enigmail disabled' does it look like (this is mine) a signed message beginning with: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 and ending with: -----BEGIN PGP SIGNATURE----- Comment: --batch iEYEARECAAYFAkpd7MYACgkQzrAMrEP3F1pRAACgguV3fOwt7fFBxKVtLDkewJnA 4rEAmgOjScJ/XmBn666YX5ZnVO/EGSG9 =CtU2 -----END PGP SIGNATURE----- No. It does not. It looks like an ordinary email with this as an attachment: signature.asc and Part 1.2 These attachments are also visible with Enigmail enabled. Screenshots here: http://www.box.net/shared/bhzvud7mv4 -- David From mlisten at hammernoch.net Wed Jul 15 09:14:01 2009 From: mlisten at hammernoch.net (=?ISO-8859-1?Q?Ludwig_H=FCgelsch=E4fer?=) Date: Wed, 15 Jul 2009 18:14:01 +0200 Subject: [Enigmail] Unverified signature error In-Reply-To: <4A5DF6DA.1000001@comcast.net> References: <4A5DE541.3080001@gmail.com> <4A5DEDC3.9030106@mac.com> <4A5DF6DA.1000001@comcast.net> Message-ID: <4A5E0049.1070009@hammernoch.net> David wrote on 15.07.09 17:33: > If you mean 'with Enigmail disabled' does it look like (this is mine) a > signed message beginning with: (...) > No. It does not. > > It looks like an ordinary email with this as an attachment: > > signature.asc and Part 1.2 > > These attachments are also visible with Enigmail enabled. So this is a PGP/MIME message with the signature as attachment. When you look at the message source (ctrl-u), does it reveal lines looking like: ------------------ This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --===============1926377670== Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="------------enigC100EE2EE293DC8AA2009066" ------------------ The detail: micalg=pgp-sha512 is important. Without it, enigmail/gpg does not know which signing algorithm is to be used, defaults to MD5 and complains about the wrong format. Ludwig -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 550 bytes Desc: OpenPGP digital signature URL: From dgboles at comcast.net Wed Jul 15 09:22:10 2009 From: dgboles at comcast.net (David) Date: Wed, 15 Jul 2009 12:22:10 -0400 Subject: [Enigmail] Unverified signature error In-Reply-To: <4A5E0049.1070009@hammernoch.net> References: <4A5DE541.3080001@gmail.com> <4A5DEDC3.9030106@mac.com> <4A5DF6DA.1000001@comcast.net> <4A5E0049.1070009@hammernoch.net> Message-ID: <4A5E0232.8040607@comcast.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 7/15/2009 12:14 PM, Ludwig H?gelsch?fer wrote: > David wrote on 15.07.09 17:33: > >> If you mean 'with Enigmail disabled' does it look like (this is mine) a >> signed message beginning with: > (...) >> No. It does not. >> >> It looks like an ordinary email with this as an attachment: >> >> signature.asc and Part 1.2 >> >> These attachments are also visible with Enigmail enabled. > > So this is a PGP/MIME message with the signature as attachment. When you > look at the message source (ctrl-u), does it reveal lines looking like: > > ------------------ > This is an OpenPGP/MIME signed message (RFC 2440 and 3156) > --===============1926377670== > Content-Type: multipart/signed; micalg=pgp-sha512; > protocol="application/pgp-signature"; > boundary="------------enigC100EE2EE293DC8AA2009066" > > ------------------ > > The detail: micalg=pgp-sha512 is important. Without it, enigmail/gpg > does not know which signing algorithm is to be used, defaults to MD5 and > complains about the wrong format. > > Ludwig It say this: - --===============1762445208== Content-type: multipart/signed; boundary=nextPart4770224.AjX0mmk9Dy; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-transfer-encoding: 7bit - --nextPart4770224.AjX0mmk9Dy Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline - -- David -----BEGIN PGP SIGNATURE----- Comment: " iEYEARECAAYFAkpeAjIACgkQzrAMrEP3F1oXXQCeLYHJESyTDO5hAlXEO26oSBE+ KGcAn15OR2bzmFSKHT+Yc/rJq4kVthY3 =Nk99 -----END PGP SIGNATURE----- From shavital at mac.com Wed Jul 15 09:39:29 2009 From: shavital at mac.com (Charly Avital) Date: Wed, 15 Jul 2009 12:39:29 -0400 Subject: [Enigmail] Unverified signature error In-Reply-To: <4A5DF6DA.1000001@comcast.net> References: <4A5DE541.3080001@gmail.com> <4A5DEDC3.9030106@mac.com> <4A5DF6DA.1000001@comcast.net> Message-ID: <4A5E0641.1030108@mac.com> [...] > If you mean 'with Enigmail disabled' does it look like (this is mine) a > signed message beginning with: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > and ending with: > > > -----BEGIN PGP SIGNATURE----- > Comment: --batch > > iEYEARECAAYFAkpd7MYACgkQzrAMrEP3F1pRAACgguV3fOwt7fFBxKVtLDkewJnA > 4rEAmgOjScJ/XmBn666YX5ZnVO/EGSG9 > =CtU2 > -----END PGP SIGNATURE----- > > No. It does not. > > It looks like an ordinary email with this as an attachment: > > signature.asc and Part 1.2 > > These attachments are also visible with Enigmail enabled. > > Screenshots here: http://www.box.net/shared/bhzvud7mv4 I apologize in advance to the list for the following long post. Maybe it's time to pursue this thread OFF LIST? I believe that "with Enigmail disabled" means *before* verifying the signature, and that "with Enigmail enabled" means *after* trying to verify signature. The e-mail you describe, multipart with an attached signature file might be an OpenPGP/MIME signed e-mail (please compare with Ludwig' post). OpenPGP/MIME signed e-mails do not display visible PGP headers, footers, nor a Hash line. But if you View that e-mail's source, the latter should display, somewhere near the bottom of the source, something similar but *not identical* to: ======================= -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBCgAGBQJKXermAAoJEA52XAUJWdLjWF4IAJc3Vf94HlaXyMwa2rnCkPne wU5uwoQSY/1TNcngnRXk8u2JArEzWNlJLRfldDYwaj7DToDSc5wIEczFcltiTvwf HZTYCdf/F0HjrjL7MbF182qUWOH/9AiL297AuOr+N8unC5ysanHZiSU7dfpqr9n0 fR0Dcpj5eTi457iIwhvusy0lBCPEKQjl081VmEXb1T79NqnnHp51G12TLjCSPej6 f/9o/lUErscgwoFOP6zVhB3SzkX7ciXDokN8cA+QsfHZwqmJ8o941H2ZOf7kCg3b YGYB0pbh9nqk9FfVlJF8mKgP80NrpzB4qmopP7RZURzGWPe5vGVyaP3xp1idBB0= =qtVD -----END PGP SIGNATURE----- ======================= Moreover, in the link I sent you, one can read: "If one uses detached signatures, the gpg correctly guess hash used from the signature, uses that, and correctly verifies message." Some more information: - the originator of the e-mail whose screen shots you have uploaded to www.box.net shows as "Till Maas ". I have found a public key that seems to belong to that user: ======= pub 4096R/1C109517 created: 2007-06-22 expires: 2012-05-22 usage: SC trust: unknown validity: unknown sub 4096R/B5098148 created: 2007-06-22 expires: 2012-05-21 usage: E [ unknown] (1). Till Maas [ unknown] (2) Till Maas ======== It's a 4096 bits RSA key, therefore I believe this precludes the possibility suggested by John, that the sender might be trying to "force" a SHA2 signature with a DSA Key that is _not_ DSA2 enabled. My very wild and uneducated guess is that Till Maas 'personal-digest-preferences' are set to a digest value that conflicts with your own personal digest preferences settings. Did other members of the "Development Discussions related to Fedora" report this same problem, or are you the only one who is experiencing it? As I indicated at the beginning of this post, maybe it's time to take this thread OFF LIST? Charly From patrick at mozilla-enigmail.org Fri Jul 17 02:39:45 2009 From: patrick at mozilla-enigmail.org (Patrick Brunschwig) Date: Fri, 17 Jul 2009 11:39:45 +0200 Subject: [Enigmail] [ANN] Enigmail v0.96.0 available Message-ID: <4A6046E1.4070009@mozilla-enigmail.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 I'm happy to announce the availability of Enigmail version 0.96.0 for Thunderbird 2.0 and SeaMonkey 1.1.x. Changes ======= This release went through quite a long development cycle. I have fixed more than 80 bugs and worked on several improvements: * New Details button on the message reading window * Allow to use gpg groups as target for email addresses and rules. * There is a new option to automatically attach the signing key to sent messages. * A way of displaying the key list in the key manager window. Obtaining Enigmail ================== Enigmail can be downloaded from The changelog is available from PS. A side note for those who are wondering about Enigmail for the upcoming Thunderbird 3.0: we have currently nightly builds for Thunderbird 3.0; a release version of Enigmail will be announced once Thunderbird 3.0 is about to be released. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEVAwUBSmBG2HcOpHodsOiwAQhFrQf/ZYdkCuPXDwYD5zzpmC6USydCx/5ItIZX F5tpiJ1pT8AbDv1K1IolPcOGEUL3HmI1TPvh53zOO32uFdgvKUHe0e5JcS5lec0e iryV9SYuMte7b0vWHuDpRMkEbHKY6Conlt23pzyOCIXtP+GtRke3nP7k/MTmEpT2 AkhCFhjh7W/h08iL75kNR4yLVOvDjMIUg7rt6QTuqU8x6MskzJR/RS4TfF+/AVgE VO6k7D2Xh2SCP7H6/fYL8+C4D3jnANk9eqcFmREBRMZ6YmnHd/sBWiZaHR0rJ1Cb byHJaDh1R+LM6IOxux8xiZua+eXtO6TbK6K277GEWtBUpsPnjt1m+w== =4xA/ -----END PGP SIGNATURE----- From stefanxe at gmx.net Fri Jul 17 03:03:02 2009 From: stefanxe at gmx.net (Stefan Xenon) Date: Fri, 17 Jul 2009 12:03:02 +0200 Subject: [Enigmail] [ANN] Enigmail v0.96.0 available In-Reply-To: <4A6046E1.4070009@mozilla-enigmail.org> References: <4A6046E1.4070009@mozilla-enigmail.org> Message-ID: <4A604C56.2080903@gmx.net> Hi! I tried the new version but when selecting key management ("Schl?ssel verwalten") no keys are shown. At the same time reading and writing encrypted mails work fine. Any idea? Regards Stefan Patrick Brunschwig schrieb: > I'm happy to announce the availability of Enigmail version 0.96.0 for > Thunderbird 2.0 and SeaMonkey 1.1.x. > > > Changes > ======= > This release went through quite a long development cycle. I have fixed > more than 80 bugs and worked on several improvements: > > * New Details button on the message reading window > * Allow to use gpg groups as target for email addresses and rules. > * There is a new option to automatically attach the signing key to > sent messages. > * A way of displaying the key list in the key manager window. > > > Obtaining Enigmail > ================== > Enigmail can be downloaded from > The changelog is available from > > > PS. A side note for those who are wondering about Enigmail for the > upcoming Thunderbird 3.0: we have currently nightly builds for > Thunderbird 3.0; a release version of Enigmail will be announced once > Thunderbird 3.0 is about to be released. > _______________________________________________ Enigmail mailing list Enigmail at mozdev.org https://www.mozdev.org/mailman/listinfo/enigmail From bjtasker at btasker.me.uk Fri Jul 17 03:24:11 2009 From: bjtasker at btasker.me.uk (B J Tasker) Date: Fri, 17 Jul 2009 11:24:11 +0100 Subject: [Enigmail] [ANN] Enigmail v0.96.0 available In-Reply-To: <4A604C56.2080903@gmx.net> References: <4A6046E1.4070009@mozilla-enigmail.org> <4A604C56.2080903@gmx.net> Message-ID: <4A60514B.90902@btasker.me.uk> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This happened to me then I noticed that the "Display all keys by default option" was unchecked!! Bernard Stefan Xenon wrote: > Hi! > I tried the new version but when selecting key management ("Schl?ssel > verwalten") no keys are shown. At the same time reading and writing > encrypted mails work fine. Any idea? > > Regards > Stefan > > Patrick Brunschwig schrieb: >> I'm happy to announce the availability of Enigmail version 0.96.0 for >> Thunderbird 2.0 and SeaMonkey 1.1.x. >> >> >> Changes >> ======= >> This release went through quite a long development cycle. I have fixed >> more than 80 bugs and worked on several improvements: >> >> * New Details button on the message reading window >> * Allow to use gpg groups as target for email addresses and rules. >> * There is a new option to automatically attach the signing key to >> sent messages. >> * A way of displaying the key list in the key manager window. >> >> >> Obtaining Enigmail >> ================== >> Enigmail can be downloaded from >> The changelog is available from >> >> >> PS. A side note for those who are wondering about Enigmail for the >> upcoming Thunderbird 3.0: we have currently nightly builds for >> Thunderbird 3.0; a release version of Enigmail will be announced once >> Thunderbird 3.0 is about to be released. >> > _______________________________________________ > Enigmail mailing list > Enigmail at mozdev.org > https://www.mozdev.org/mailman/listinfo/enigmail > > _______________________________________________ > Enigmail mailing list > Enigmail at mozdev.org > https://www.mozdev.org/mailman/listinfo/enigmail > - -- B J Tasker -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Test comment Comment: This is an additional comment line within the OpenPGP signature Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkpgUUsACgkQqPQ3uX5O/PcjcQCfUmGhJjslu4OiU4UWIXsUWhLy 7x4An3zfDc1+Cui3ivn943Ng3abVKXAO =J30X -----END PGP SIGNATURE----- From shavital at mac.com Fri Jul 17 04:43:03 2009 From: shavital at mac.com (Charly Avital) Date: Fri, 17 Jul 2009 07:43:03 -0400 Subject: [Enigmail] [ANN] Enigmail v0.96.0 available In-Reply-To: <4A6046E1.4070009@mozilla-enigmail.org> References: <4A6046E1.4070009@mozilla-enigmail.org> Message-ID: <4A6063C7.2020005@mac.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Patrick Brunschwig wrote the following on 7/17/09 5:39 AM: > I'm happy to announce the availability of Enigmail version 0.96.0 for > Thunderbird 2.0 and SeaMonkey 1.1.x. > > > Changes > ======= > This release went through quite a long development cycle. I have fixed > more than 80 bugs and worked on several improvements: Works impeccably. > > * New Details button on the message reading window Nice touch, and useful. Tested all the options, all work fine. > * Allow to use gpg groups as target for email addresses and rules. I don't use groups, but I'll test this new function in the future. > * There is a new option to automatically attach the signing key to > sent messages. Testing it now, but I shall disable it later. I'll attach my public key only when needed. > * A way of displaying the key list in the key manager window. Great, and user configurable. > > > Obtaining Enigmail > ================== > Enigmail can be downloaded from > The changelog is available from Signature verifies. > > > PS. A side note for those who are wondering about Enigmail for the > upcoming Thunderbird 3.0: we have currently nightly builds for > Thunderbird 3.0; a release version of Enigmail will be announced once > Thunderbird 3.0 is about to be released. Fine. Congratulations and especially *THANKS* to all who contributed to the release of 0.96.a Charly MacOS 10.5.7-MacBook Intel C2Duo 2GHz-GnuPG 1.4.9-MacGPG 2.0.12 TB 2.0.0.22+EM 0.96.0-Apple's Mail+GPGMail 1.2.0 (v56), Key: 0xA57A8EFA -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.12 (Darwin) Comment: GnuPG for Privacy Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBCAAGBQJKYGO/AAoJEM3GMi2FW4PvhM4H+QFWXTSm/7lrP21oj6+2DcG6 msvobgTi6lLmNG7PBJ+HslkZS7upviT7jLHEGJRYTRBQFBLjgCEPYVEdqeqrCmah l+UKtmUcHrIAf0svqIyMNtOdMxD3YABAZ8mtj1IcEjL8vsB+AcGcqckaMCK5HHUl V32LwxI8iO8WR9zXXZczH5RECMjf74vCFc9l755ZHKe5P2MWBtKqsVRqgiRdN+lh UhEMbXKH+TMkmHJbxbbtDc4kfc7jFWqz7qb7CJVoaog7+JezHHNenkRsjqWKBt72 yk1HUsdb6wfGLskuYJo8jZcMBmVXAdp3fqwRW9ifOHsix9ft6SKgcuuyQ9ZyFuQ= =IFye -----END PGP SIGNATURE----- -------------- next part -------------- A non-text attachment was scrubbed... Name: 0xA57A8EFA.asc Type: application/pgp-keys Size: 3949 bytes Desc: not available URL: From stefanxe at gmx.net Fri Jul 17 06:57:51 2009 From: stefanxe at gmx.net (Stefan Xenon) Date: Fri, 17 Jul 2009 15:57:51 +0200 Subject: [Enigmail] [ANN] Enigmail v0.96.0 available In-Reply-To: <4A60514B.90902@btasker.me.uk> References: <4A6046E1.4070009@mozilla-enigmail.org> <4A604C56.2080903@gmx.net> <4A60514B.90902@btasker.me.uk> Message-ID: <4A60835F.2020003@gmx.net> You are right, it works when checking this checkbox. For my opinion this behaviour is non-intuitive and also differs to similar cases in other applications. I would prefer the behaviour as in 0.95.x. Just my two cents... B J Tasker schrieb: > This happened to me then I noticed that the "Display all keys by default > option" was unchecked!! > > Bernard > > Stefan Xenon wrote: >> Hi! >> I tried the new version but when selecting key management ("Schl?ssel >> verwalten") no keys are shown. At the same time reading and writing >> encrypted mails work fine. Any idea? > >> Regards >> Stefan > >> Patrick Brunschwig schrieb: >>> I'm happy to announce the availability of Enigmail version 0.96.0 for >>> Thunderbird 2.0 and SeaMonkey 1.1.x. >>> >>> >>> Changes >>> ======= >>> This release went through quite a long development cycle. I have fixed >>> more than 80 bugs and worked on several improvements: >>> >>> * New Details button on the message reading window >>> * Allow to use gpg groups as target for email addresses and rules. >>> * There is a new option to automatically attach the signing key to >>> sent messages. >>> * A way of displaying the key list in the key manager window. >>> >>> >>> Obtaining Enigmail >>> ================== >>> Enigmail can be downloaded from >>> The changelog is available from >>> >>> >>> PS. A side note for those who are wondering about Enigmail for the >>> upcoming Thunderbird 3.0: we have currently nightly builds for >>> Thunderbird 3.0; a release version of Enigmail will be announced once >>> Thunderbird 3.0 is about to be released. >>> >> _______________________________________________ >> Enigmail mailing list >> Enigmail at mozdev.org >> https://www.mozdev.org/mailman/listinfo/enigmail > >> _______________________________________________ >> Enigmail mailing list >> Enigmail at mozdev.org >> https://www.mozdev.org/mailman/listinfo/enigmail > > > _______________________________________________ Enigmail mailing list Enigmail at mozdev.org https://www.mozdev.org/mailman/listinfo/enigmail From jmoore3rd at bellsouth.net Fri Jul 17 08:04:46 2009 From: jmoore3rd at bellsouth.net (John W. Moore III) Date: Fri, 17 Jul 2009 11:04:46 -0400 Subject: [Enigmail] [ANN] Enigmail v0.96.0 available In-Reply-To: <4A60835F.2020003@gmx.net> References: <4A6046E1.4070009@mozilla-enigmail.org> <4A604C56.2080903@gmx.net> <4A60514B.90902@btasker.me.uk> <4A60835F.2020003@gmx.net> Message-ID: <4A60930E.1070502@bellsouth.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Stefan Xenon wrote: > You are right, it works when checking this checkbox. > > For my opinion this behaviour is non-intuitive and also differs to > similar cases in other applications. I would prefer the behaviour as in > 0.95.x. Leaving the 'box' unchecked allows One to use the 'Search' box. Enter any known or suspected attributes of the Key in question and only results pertaining to matching Keys will be displayed. JOHN ;) Timestamp: Friday 17 Jul 2009, 11:04 --400 (Eastern Daylight Time) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10-svn5068: (MingW32) Comment: Public Key at: http://tinyurl.com/8cpho Comment: Gossamer Spider Web of Trust: http://www.gswot.org Comment: Personal Web Page: http://tinyurl.com/yzhbhx iQEcBAEBCgAGBQJKYJMLAAoJEBCGy9eAtCsPCOwIAKKE34ZSxjgBfd1vhZrQpOxg H1wSwdHqOfw970ReMzJtqu7U+zeqZTzfXvqrQQvuzMnHBNmQn28Z020P/fluBQfU f5Vhw5CRG79cGq51ubEvnf1dCl/PINM3p6jnU8MXtwCuFUmNgF/Ov6TUE5NsMKqN udLS/w+xBchN70aCAQ8vyOlY4HU7RktEOgzWxxCJOJMx2N2OHlJhGIP21MRQdaE5 xi//k+P0NC65HuemShH6k883AXO+Bs1q3pGhsM2MwXjnrK8CFKjY7AnFlbO/3eNl fhBU20l0J1/j+SVFvzOS4Y8qD168gEmezEGqi1XdDj4yP67rWrHVpZY0BflpKVc= =J2QJ -----END PGP SIGNATURE----- From michaeljgruber+mozdevnews at fastmail.fm Fri Jul 17 08:16:53 2009 From: michaeljgruber+mozdevnews at fastmail.fm (Michael J Gruber) Date: Fri, 17 Jul 2009 17:16:53 +0200 Subject: [Enigmail] Building with TB3b3 Message-ID: Has anyone see this lately (missing skin/tb-linux/contents.rdf) when trying to build enigmail from cvs with comm-central-1.9.1? gmake[2]: Leaving directory `/home/mjg/src/mozstuff/objdir-comm-central-tb/mailnews/extensions/enigmail/lang' :processing /home/mjg/src/mozstuff/comm-central/mailnews/extensions/enigmail/build/package/jar.mn processing /home/mjg/src/mozstuff/comm-central/mailnews/extensions/enigmail/ui/jar.mn Traceback (most recent call last): File "/home/mjg/src/mozstuff/comm-central/mozilla/config/JarMaker.py", line 461, in main() File "/home/mjg/src/mozstuff/comm-central/mozilla/config/JarMaker.py", line 458, in main jardir=options.j) File "/home/mjg/src/mozstuff/comm-central/mozilla/config/JarMaker.py", line 231, in makeJar localedirs) File "/home/mjg/src/mozstuff/comm-central/mozilla/config/JarMaker.py", line 300, in processJarSection outHelper, jf) File "/home/mjg/src/mozstuff/comm-central/mozilla/config/JarMaker.py", line 332, in _processEntryLine raise RuntimeError("file not found: " + src) RuntimeError: file not found: skin/tb-linux/contents.rdf gmake[2]: *** [libs] Fehler 1 gmake[1]: *** [libs] Fehler 2 make: *** [default] Fehler 2 From stefanxe at gmx.net Fri Jul 17 08:20:15 2009 From: stefanxe at gmx.net (Stefan Xenon) Date: Fri, 17 Jul 2009 17:20:15 +0200 Subject: [Enigmail] [ANN] Enigmail v0.96.0 available In-Reply-To: <4A60930E.1070502@bellsouth.net> References: <4A6046E1.4070009@mozilla-enigmail.org> <4A604C56.2080903@gmx.net> <4A60514B.90902@btasker.me.uk> <4A60835F.2020003@gmx.net> <4A60930E.1070502@bellsouth.net> Message-ID: <4A6096AF.3030902@gmx.net> John W. Moore III schrieb: > Stefan Xenon wrote: >> You are right, it works when checking this checkbox. > >> For my opinion this behaviour is non-intuitive and also differs to >> similar cases in other applications. I would prefer the behaviour as in >> 0.95.x. > > Leaving the 'box' unchecked allows One to use the 'Search' box. Enter > any known or suspected attributes of the Key in question and only > results pertaining to matching Keys will be displayed. This behaviour was also in place before. With 0.95 as soon as a character was entered in the text box only the matching keys were displayed. This difference is that 0.96 starts with an empty list (which does not allow to get an overview and to scroll through the list) while 0.95 showed all keys initially. As an analogy if you open a folder on your desktop you see all containing files and subfolders (similar to 0.95). With 0.96 it would be as an empty folder is displayed initially and the content is shown after activating the check box only. :-) Regards stefan From olav at seyfarth.de Fri Jul 17 10:28:22 2009 From: olav at seyfarth.de (Olav Seyfarth) Date: Fri, 17 Jul 2009 19:28:22 +0200 Subject: [Enigmail] [ANN] Enigmail v0.96.0 available In-Reply-To: <4A6046E1.4070009@mozilla-enigmail.org> References: <4A6046E1.4070009@mozilla-enigmail.org> Message-ID: <4A60B4B6.1000606@seyfarth.de> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hallo Patrick, willst du dann das Verzeichnis http://www.mozilla-enigmail.org/download/release/0.96b/ nicht wieder l?schen?! Gru?, Olav -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEAREIAAYFAkpgtLUACgkQL/NBt8fdKe2kdACZARaTYx/tWgTXPHYObUSlHBf8 bVAAn0qVLyjXeIwhDB9E1FDhsG4ijDr5 =nunA -----END PGP SIGNATURE----- From mlisten at hammernoch.net Fri Jul 17 11:35:20 2009 From: mlisten at hammernoch.net (=?ISO-8859-1?Q?Ludwig_H=FCgelsch=E4fer?=) Date: Fri, 17 Jul 2009 20:35:20 +0200 Subject: [Enigmail] Building with TB3b3 In-Reply-To: References: Message-ID: <4A60C468.9020501@hammernoch.net> Hi, Michael J Gruber wrote on 17.07.09 17:16: > RuntimeError: file not found: skin/tb-linux/contents.rdf This file exists in my checkout done some minutes ago. Last modified July 13th. Perhaps a fresh checkout will reproduce it. Ludwig -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 550 bytes Desc: OpenPGP digital signature URL: From andy.ruddock at rainydayz.org Sat Jul 18 00:43:16 2009 From: andy.ruddock at rainydayz.org (Andy Ruddock) Date: Sat, 18 Jul 2009 09:43:16 +0200 Subject: [Enigmail] Enigmail 0.96.0 for Ubuntu Seamonkey Message-ID: <4A617D14.6040305@rainydayz.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've built Enigmail-0.96.0 for Seamonkey on Ubuntu, more details & downloads from http://www.rainydayz.org/node/17 - -- Andy Ruddock - ------------ andy.ruddock at rainydayz.org (GPG Key ID 0xA622D452) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkphfQ4ACgkQfSkWkaYi1FI1+gCgtUBudECIlJPZbDJkYJyX6s41 sWUAoIXLoEXvBOq3ZGA4m/niMdadZjg8 =8Iv+ -----END PGP SIGNATURE----- From michaeljgruber+mozdevnews at fastmail.fm Sat Jul 18 03:26:00 2009 From: michaeljgruber+mozdevnews at fastmail.fm (Michael J Gruber) Date: Sat, 18 Jul 2009 12:26:00 +0200 Subject: [Enigmail] Building with TB3b3 In-Reply-To: References: Message-ID: Ludwig H?gelsch?fer venit, vidit, dixit 17.07.2009 20:35: > Hi, > > Michael J Gruber wrote on 17.07.09 17:16: >> RuntimeError: file not found: skin/tb-linux/contents.rdf > > This file exists in my checkout done some minutes ago. Last modified > July 13th. I only had tb-mac, which is weird. I've been building successfully from there for quite a while. > Perhaps a fresh checkout will reproduce it. > > Ludwig > That indeed improved things, except for a warning during "make xpi": genxpi: Generating enigmail-0.97a-linux-x86_64.xpi in ../../../mozilla/dist/bin zip warning: name not matched: chrome/enigmail-skin-tbird.jar But everything builds and runs now, which is the best I can expect from the bleeding edge :) Michael From Liste at FamilleCollet.com Sat Jul 18 10:12:26 2009 From: Liste at FamilleCollet.com (Remi Collet) Date: Sat, 18 Jul 2009 19:12:26 +0200 Subject: [Enigmail] enigmail 0.96.0 build issue on ppc64 Message-ID: <4A62027A.6090706@FamilleCollet.com> Hi, Trying to update enigmail package available on Rpmfusion (for Fedora 10), I encounter a build failure on ppc64. Full build log http://buildsys.rpmfusion.org/logs/fedora-10-rpmfusion_free/4492-thunderbird-enigmail-0.96.0-1.fc10/ppc64/build.log The issue is that TARGET_XPCOM_ABI is not detected/set by thunderbird configure script. This trivial patch fixes this build issue --- configure.orig 2008-10-19 18:21:23.000000000 +0200 +++ configure 2009-07-18 17:44:36.000000000 +0200 @@ -5408,7 +5408,7 @@ CPU_ARCH=sparc ;; -x86_64 | sparc | ppc | ia64) +x86_64 | sparc | ppc | ia64 | ppc64) CPU_ARCH="$OS_TEST" ;; esac Enigmail Makefile seems to try to handle this case : ifeq ($(TARGET_XPCOM_ABI),) But not correctly ;) thunderbird-enigmail-0.96.0-2.fc10 is build and should be available really soon in RPMFusion for i386, x86_64, ppc and ppc64, as usually. Regards Remi. From kyshk at bc.iij4u.or.jp Tue Jul 21 06:40:23 2009 From: kyshk at bc.iij4u.or.jp (kyshk at bc.iij4u.or.jp) Date: Tue, 21 Jul 2009 22:40:23 +0900 Subject: [Enigmail] [ANN] Enigmail v0.96.0 available In-Reply-To: <4A6046E1.4070009@mozilla-enigmail.org> References: <4A6046E1.4070009@mozilla-enigmail.org> Message-ID: <4A65C547.5090200@bc.iij4u.or.jp> Hi! Enigmail is always dependable. I tried the Enigmail 0.96.0 but It is unusable Japanese language. It can not send ISO-2022-JP encode encrypt message. bad Thunderbird - Enigmail encode linkage. (Enigmail 0.95.7 is OK) ,----[ example ]- send non PGP/MIME ISO-2022-JP encrypt message | X-Enigmail-Version: 0.96.0 | Content-Type: text/plain; charset=UTF-8 | Content-Transfer-Encoding: 8bit | Status: U | | -----BEGIN PGP MESSAGE----- | Charset: ISO-2022-JP | Version: GnuPG v1.4.8 (MingW32) | Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ `---- ,----[ not ]- | Content-Type: text/plain; charset=UTF-8 | Content-Transfer-Encoding: 8bit `---- ,----[ but ]- | Content-Type: text/plain; charset=ISO-2022-JP | Content-Transfer-Encoding: 7bit `---- use: Thunderbird 2.0.0.22 (20090605) Enigmail 0.96.0 (20090717-0949) settings: --rfc2440 extensions.enigmail.warnIso2022jp=2 source message encoding is ISO-2022-JP 1.non PGP/MIME encrypt :UTF-8 (bad) 2.non PGP/MIME signed :ISO-2022-JP (good) 3.non PGP/MIME signed+encrypt :UTF-8 (bad) 4.PGP/MIME encrypt :UTF-8 (bad) 5.PGP/MIME signed :UTF-8 (bad) 6.PGP/MIME signed+encrypt :UTF-8 (bad) message(1,3,4,5,6) maybe can not read other MUA. (mojibake) Content-Type header be distinct from contents. Thunderbird 2.0.0.22 can not accurate encode. (wrong Content-Type header) Enigmail ignore [extensions.enigmail.warnIso2022jp] param. and Japanese standard encrypt(or signed) message is NO UTF-8 and NO quoted-printable. -- kiyo From Liste at FamilleCollet.com Tue Jul 21 12:23:01 2009 From: Liste at FamilleCollet.com (Remi Collet) Date: Tue, 21 Jul 2009 21:23:01 +0200 Subject: [Enigmail] enigmail 0.96.0 build issue on ppc64 In-Reply-To: <4A62027A.6090706@FamilleCollet.com> References: <4A62027A.6090706@FamilleCollet.com> Message-ID: <4A661595.4010600@FamilleCollet.com> Le 18/07/2009 19:12, Remi Collet a ?crit : > Hi, > > Trying to update enigmail package available on Rpmfusion (for Fedora > 10), I encounter a build failure on ppc64. > > Full build log > http://buildsys.rpmfusion.org/logs/fedora-10-rpmfusion_free/4492-thunderbird-enigmail-0.96.0-1.fc10/ppc64/build.log > > The issue is that TARGET_XPCOM_ABI is not detected/set by thunderbird > configure script. > Same issue with thunderbird 3.0b3 and enigmail from CVS (0.97a). thunderbird-enigmail-0.97a-0.1.cvs20090721.fc11 is on the builder and should be available really soon in RPMFusion (with thunderbird 3.0b3) for i386, x86_64, ppc and ppc64, as usually. Remi From thomas.jost at gmail.com Tue Jul 21 13:41:15 2009 From: thomas.jost at gmail.com (Thomas Jost) Date: Tue, 21 Jul 2009 22:41:15 +0200 Subject: [Enigmail] Enigmail 0.96.0 Linux x86_64 build and Arch Linux package Message-ID: <4A6627EB.2070500@gmail.com> Hi list, I built Enigmail 0.96.0 for Linux x86_64 (Arch Linux, gcc 4.4 -- same configuration as the only contributed Linux x86_64 build available for Enigmail 0.95.7 on the web site). The .xpi file is available at http://fichiers.schnouki.net/enigmail/. I also packaged it for Arch Linux. The package is available in the Arch User Repository (http://aur.archlinux.org/packages.php?ID=28640). Please vote it if you use it :) Regards -- Thomas/Schnouki -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 261 bytes Desc: OpenPGP digital signature URL: From taistealaiche at earthlights.net Wed Jul 22 09:59:32 2009 From: taistealaiche at earthlights.net (Taistealaiche) Date: Thu, 23 Jul 2009 04:59:32 +1200 Subject: [Enigmail] Multiple email addresses Message-ID: <4A674574.4010102@earthlights.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I'm not sure if these questions belong on this list so please inform me if I'm wrong. 1) Is it possible, in the case of an organisation, to have one Public Key which can be tied to several different email addreses? 2) If the above is possible, is it also possible for each email address to have a separate passphrase for that key? 3) If both of the above are possible, could someone very kindly explain how to do it? Very many thanks, Taistealaiche at 4:54 a.m. on Thursday, 23 July 2009 "Tha iomadh tonn eadar an long 's an t?r" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Are your emails secure? Comment: Always! encrypt sensitive emails iQEcBAEBAgAGBQJKZ0VzAAoJENdHWlLnbf5PIH0H+gKQfNQLBiT3/W4WeTHGTtkw DoQu5bvBy8xRpY71TuKE3ZZdPDZsR0xdQdwBNn1yuWmtBLht0Zh30imQqUCkMNvr zr0jIhYOTVhH6iN4f9Nw0YpbjPJx1LSU0vj+CmSOi/RcgN1Cxis/l16cyrcnUX/K A1fSZ5gPW7+1ZtWkCXjV/UhcxfzTo6QQ9p/Jx/bbhizIcoHSNfCS5MqyWj6Vx9mh DkXQlXryiYtqLeEL/jPhliOKvCao8OO4bB5iK4DueLwJBfOu5lCI70De7yMJz7h/ joYNMMhEQ1KLzVOXRjUwDcEUq7KGm+kYkIcjvVqaFqAnFgyhAzHDG//htbxtgCU= =m4N5 -----END PGP SIGNATURE----- -------------- next part -------------- A non-text attachment was scrubbed... Name: 0xE76DFE4F.asc Type: application/pgp-keys Size: 1998 bytes Desc: not available URL: From stefanxe at gmx.net Wed Jul 22 10:58:05 2009 From: stefanxe at gmx.net (Stefan Xenon) Date: Wed, 22 Jul 2009 19:58:05 +0200 Subject: [Enigmail] Enigmail fails with GnuPG2 + OpenPGP Card Message-ID: <4A67532D.4010105@gmx.net> Hi! I use GnuPG2 and tried to generate a key on the OpenPGP Card. Unfortunately it failed with the error message "unbekannter Fehler bei Schl?sselgenerierung" (unknown error). The Enigmail console tells me the following command is executed: C:\Program Files\GNU\GnuPG2\gpg2.exe --charset utf8 --no-tty --status- fd 1 --logger-fd 1 --command-fd 0 --with-colons --card-edit It works on the same system when configuring Enigmail to use GnuPG v1. So maybe an compatibility issue with GnuPG v2? Any idea how to solve it? Regards From alaric at metrocast.net Wed Jul 22 11:19:44 2009 From: alaric at metrocast.net (Phil Stracchino) Date: Wed, 22 Jul 2009 14:19:44 -0400 Subject: [Enigmail] Multiple email addresses In-Reply-To: <4A674574.4010102@earthlights.net> References: <4A674574.4010102@earthlights.net> Message-ID: <4A675840.1040101@metrocast.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Taistealaiche wrote: > Hi, > I'm not sure if these questions belong on this list so please inform > me if I'm wrong. They're really PGP/GnuPG/OpenPGP questions, not Enigmail questions. > 1) Is it possible, in the case of an organisation, to have one Public > Key which can be tied to several different email addreses? Yes, trivially. Though I'm not entirely certain why you would want to do such a thing. > 2) If the above is possible, is it also possible for each email > address to have a separate passphrase for that key? Yes. Though I'm not certain why you would want to do such a thing. > 3) If both of the above are possible, could someone very kindly > explain how to do it? It's really quite simple. Create the key as you normally would, distribute it to the people you intent to have it, then have each holder use the normal key management tools to change the key passphrase on it from the original passphrase to their own chosen passphrase. Though, as noted above, I'm not certain why you would want to do such a thing, and don't see what you could gain by it. - -- Phil Stracchino, CDK#2 DoD#299792458 ICBM: 43.5607, -71.355 alaric at caerllewys.net alaric at metrocast.net phil at co.ordinate.org Renaissance Man, Unix ronin, Perl hacker, Free Stater It's not the years, it's the mileage. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEAREIAAYFAkpnWEAACgkQ0DfOju+hMkmBhgCfUT6s6MXRDjsqQ14a9EwdRADi kXsAnRpAi1p6piHCdmYdwA2j/I3HA2QP =d/JR -----END PGP SIGNATURE----- From shavital at mac.com Wed Jul 22 13:07:28 2009 From: shavital at mac.com (Charly Avital) Date: Wed, 22 Jul 2009 16:07:28 -0400 Subject: [Enigmail] Multiple email addresses In-Reply-To: <4A674574.4010102@earthlights.net> References: <4A674574.4010102@earthlights.net> Message-ID: <4A677180.4030001@mac.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Taistealaiche wrote the following on 7/22/09 12:59 PM: > Hi, > I'm not sure if these questions belong on this list so please inform > me if I'm wrong. Hi, Your questions belong to the gnupg-users forum. > > 1) Is it possible, in the case of an organisation, to have one Public > Key which can be tied to several different email addreses? Anyone can generate a keypair with different user IDs (uid) that bear different e-mail addresses. You are running MingW32, so you must have, as an integral part of that installation, some kind of application to manage your keyrings. Something like GPA or GPG-Tray, I really don't remember, I don't usually run Windows. Whatever the application, you will be prompted to enter your passphrase when you want to edit your key, in order to add UIDs. > > 2) If the above is possible, is it also possible for each email > address to have a separate passphrase for that key? I don't believe it is possible. You generate one keypair, you add UIDs, it's the same keypair for each uid, and the same passphrase. If you really require a different passphrase for each e-mail address, you might need to generate a different keypair for each e-mail address, and then you'll be able to set the passphrase you want. > > 3) If both of the above are possible, could someone very kindly > explain how to do it? If you don't get detailed answers in this forum (dedicated to Enigmail), you might want to post your questions to the gnupg-users forum. > > Very many thanks, Sorry I can' do better, I don't usually run Windows. Good luck, Charly MacOS 10.5.7-MacBook Intel C2Duo 2GHz-GnuPG 1.4.9-MacGPG 2.0.12 TB 2.0.0.22+EM 0.96.0-Apple's Mail+GPGMail 1.2.0 (v56), Key: 0xA57A8EFA -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.12 (Darwin) Comment: GnuPG for Privacy Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBCAAGBQJKZ3FxAAoJEM3GMi2FW4PvRP4H/1jn3Ep0uVtmcx1F1fPSDp0N /mg4NuaquxPtABees5zjH9MPTUn9pXqyga/loo4WmxPEV4b8TuIajLq9tb4EbF1t yxuwb/b5CqGq8qizQp52eNj2ZUfO5vQ/L0DqgQQOcpc3TWTxyi+7aLizGReAlwwZ rsPrsg9gipKL7iUH31qATGBjxPVq2YLf8jrBVaWlSG2nW2YCRI6CnW/kCnaSuWyO t93HBy9XJkVR7SZ0tWwuS1vkTe6XJcdLWNo2yWTKUIpjKu6Knw19lb2g+u9ZQcaU 9Z3bI26UeuzYUzUtmKtneqMw+tvUqfw8Pm35EEaDLWYZ9mqVkRUX9IwmoEmOBIE= =Lm9u -----END PGP SIGNATURE----- -------------- next part -------------- A non-text attachment was scrubbed... Name: 0xA57A8EFA.asc Type: application/pgp-keys Size: 3949 bytes Desc: not available URL: From olav at mozilla-enigmail.org Wed Jul 22 15:11:28 2009 From: olav at mozilla-enigmail.org (Olav Seyfarth) Date: Thu, 23 Jul 2009 00:11:28 +0200 Subject: [Enigmail] Enigmail fails with GnuPG2 + OpenPGP Card In-Reply-To: <4A67532D.4010105@gmx.net> References: <4A67532D.4010105@gmx.net> Message-ID: <4A678E90.6080405@mozilla-enigmail.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi Stefan, > It works on the same system when configuring Enigmail to use GnuPG v1. > So maybe an compatibility issue with GnuPG v2? does it work using gpg2 CLI? If not it's a gpg issue. Olav -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12-svn5008 (MingW32) Comment: Diese ist eine Digitale Signatur nach OpenPGP-Standard Comment: http://privat.seyfarth.de/olav/schluessel.html iEYEAREIAAYFAkpnjo8ACgkQL/NBt8fdKe3wGgCgrUDUUziDRVOe+SwrMI4FLjZS 3O4AoKIlm4hQKYr0o5QGS/nAtcK33qV5 =CwxS -----END PGP SIGNATURE----- From stefanxe at gmx.net Wed Jul 22 22:51:52 2009 From: stefanxe at gmx.net (Stefan Xenon) Date: Thu, 23 Jul 2009 07:51:52 +0200 Subject: [Enigmail] Enigmail fails with GnuPG2 + OpenPGP Card In-Reply-To: <4A678E90.6080405@mozilla-enigmail.org> References: <4A67532D.4010105@gmx.net> <4A678E90.6080405@mozilla-enigmail.org> Message-ID: <4A67FA78.3050603@gmx.net> Hi Olax, yes, generating keys with GnuPG CLI works on the same system. Stefan Olav Seyfarth schrieb: > Hi Stefan, > >> It works on the same system when configuring Enigmail to use GnuPG v1. >> So maybe an compatibility issue with GnuPG v2? > > does it work using gpg2 CLI? If not it's a gpg issue. > > Olav _______________________________________________ Enigmail mailing list Enigmail at mozdev.org https://www.mozdev.org/mailman/listinfo/enigmail From patrick at mozilla-enigmail.org Wed Jul 22 23:45:58 2009 From: patrick at mozilla-enigmail.org (Patrick Brunschwig) Date: Thu, 23 Jul 2009 08:45:58 +0200 Subject: [Enigmail] Enigmail fails with GnuPG2 + OpenPGP Card In-Reply-To: <4A67532D.4010105@gmx.net> References: <4A67532D.4010105@gmx.net> Message-ID: <4A680726.3090403@mozilla-enigmail.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Stefan Xenon wrote: > Hi! > I use GnuPG2 and tried to generate a key on the OpenPGP Card. > Unfortunately it failed with the error message "unbekannter Fehler bei > Schl?sselgenerierung" (unknown error). The Enigmail console tells me the > following command is executed: > > C:\Program Files\GNU\GnuPG2\gpg2.exe --charset utf8 --no-tty --status- > fd 1 --logger-fd 1 --command-fd 0 --with-colons --card-edit > > It works on the same system when configuring Enigmail to use GnuPG v1. > So maybe an compatibility issue with GnuPG v2? Yes, an incompatibility with GnuPG v2. I have fixed this a few days ago. In order to use gpg2, you will need a trunk version of Enigmail. Please also note that generating keys and administration of GnuPG cards is broken in Enigmail v0.96.0; it will be fixed in the next version of Enigmail. - -Patrick -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEVAwUBSmgHJXcOpHodsOiwAQie7Af9EJpSAr8SixAwP65yUXOmdw/yC/FElgfA KQBGXEm1Xd4I/pTD3gfAnNMJjkwkOLZAkkZaw9qFH1Ro+JRvtUQtvbWuaaBQYoHh uNxVGd2zd7LXxUpwp0SXqWVl5rWRDvGYxeJumKp5V1aPuhTKU2lpYg9Tm7OxsPzQ ukCNOSIEroufevXKponpGRiBE/mniG7YH43tzeOlpkYiVCmQ0Aly6XehA3ph32zg Wu1K/ycI9VhNsrDZ8rx5GDkzPWxzgTo2oa8Bn9DpAez+RMrJPD4xoY9RVDupe7NG 9cHj6CVCQMlxLzKr+F5NMSVVbyuFRf64edr5DJOq7Md093mh9XNvcA== =DlCE -----END PGP SIGNATURE----- From rasmith1959 at gmail.com Thu Jul 23 11:01:50 2009 From: rasmith1959 at gmail.com (Roy Smith) Date: Thu, 23 Jul 2009 13:01:50 -0500 Subject: [Enigmail] Multiple email addresses In-Reply-To: References: Message-ID: Taistealaiche wrote: > Hi, > I'm not sure if these questions belong on this list so please inform > me if I'm wrong. > > 1) Is it possible, in the case of an organisation, to have one Public > Key which can be tied to several different email addreses? It is possible to have one key with several email addresses, just take a look at mine. > 2) If the above is possible, is it also possible for each email > address to have a separate passphrase for that key? Unfortunately I don't think it's possible to do this. You might be able to do this with PGP, but then PGP isn't free either. -- Roy Smith Windows XP Pro SP3 From crystal.a.brewton at gmail.com Thu Jul 23 11:08:02 2009 From: crystal.a.brewton at gmail.com (Crystal Brewton) Date: Thu, 23 Jul 2009 11:08:02 -0700 Subject: [Enigmail] Multiple email addresses In-Reply-To: References: Message-ID: <4A68A702.2040405@gmail.com> How did you manage that, if I may ask? I have OpenPGP as well as PorablePGP and would like to do this with a key, using two email addys. Also is it required to use a valid email address? Thank you in advance, Crystal Roy Smith wrote: > Taistealaiche wrote: > >> Hi, >> I'm not sure if these questions belong on this list so please inform >> me if I'm wrong. >> >> 1) Is it possible, in the case of an organisation, to have one Public >> Key which can be tied to several different email addreses? >> > > It is possible to have one key with several email addresses, just take a > look at mine. > > >> 2) If the above is possible, is it also possible for each email >> address to have a separate passphrase for that key? >> > > Unfortunately I don't think it's possible to do this. You might be able > to do this with PGP, but then PGP isn't free either. > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From taistealaiche at earthlights.net Thu Jul 23 11:14:28 2009 From: taistealaiche at earthlights.net (Taistealaiche) Date: Fri, 24 Jul 2009 06:14:28 +1200 Subject: [Enigmail] Multiple email addresses In-Reply-To: References: Message-ID: <4A68A884.8000900@earthlights.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Very many thanks for all your replies regarding this. It appears the general consensus is that it isn't possible to have a separate passphrase per user for the one key. Back to the drawing board :) On 24/07/2009 6:01 a.m., Roy Smith wrote: > Taistealaiche wrote: >> Hi, >> I'm not sure if these questions belong on this list so please inform >> me if I'm wrong. >> >> 1) Is it possible, in the case of an organisation, to have one Public >> Key which can be tied to several different email addreses? > > It is possible to have one key with several email addresses, just take a > look at mine. > >> 2) If the above is possible, is it also possible for each email >> address to have a separate passphrase for that key? > > Unfortunately I don't think it's possible to do this. You might be able > to do this with PGP, but then PGP isn't free either. Many thanks, Taistealaiche at 6:12 a.m. on Friday, 24 July 2009 "Tha iomadh tonn eadar an long 's an t?r" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Are your emails secure? Comment: Always! encrypt sensitive emails iQEcBAEBAgAGBQJKaKiEAAoJENdHWlLnbf5PAjsH/3YGEbMMVGVlffhV81aQ6c8p PogvVKYfjH42XMMEnYur5AEtCdQgP45ZAkZMcjnp834zZ8PiHfsuiFe3KEDR1ygz xeOi1ns2MAKzRYjBTypXY39VMH6Fzvd2WhBeSWd/G+bD2PYAXBN8uGSx4xbCP0pK Wqs7ytXXZijujpxBhZMGGIvRBLgs7s3BRLLy36SxA7Cwfr2ALmgkkK9H1K5pDFFF uhaRlraF7looIKUWxPsXmqFfgH9fR4yvbxAqB24JLSGvIoB96Sa2jYTLly/U9tkW BzzV9Ph5Rc/f/BEuJsW9vG+BhTOIKRBoF6qG3cKZ2myxpp4KBEd/IuG4GavkZnQ= =WVBD -----END PGP SIGNATURE----- -------------- next part -------------- A non-text attachment was scrubbed... Name: 0xE76DFE4F.asc Type: application/pgp-keys Size: 1998 bytes Desc: not available URL: From alaric at metrocast.net Thu Jul 23 11:16:39 2009 From: alaric at metrocast.net (Phil Stracchino) Date: Thu, 23 Jul 2009 14:16:39 -0400 Subject: [Enigmail] Multiple email addresses In-Reply-To: <4A68A702.2040405@gmail.com> References: <4A68A702.2040405@gmail.com> Message-ID: <4A68A907.5070909@metrocast.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Crystal Brewton wrote: > How did you manage that, if I may ask? I have OpenPGP as well as > PorablePGP and would like to do this with a key, using two email addys. > Also is it required to use a valid email address? It's trivial to add email addresses to a key. It's a standard key management function. With Enigmail, OpenPGP -> Key Management -> select key -> right-click -> Manage User IDs -> Add. - From the command line with GnuPG, gpg --edit-keys -> adduid. There's nothing to stop you from adding an invalid email address to a key if you really want to, but I fail to see what benefit there would be to doing so, since if the address is invalid you can't send mail from it and the additional uid will never get used. It would be a little like adding an extra door onto your house that opens onto a blank wall. - -- Phil Stracchino, CDK#2 DoD#299792458 ICBM: 43.5607, -71.355 alaric at caerllewys.net alaric at metrocast.net phil at co.ordinate.org Renaissance Man, Unix ronin, Perl hacker, Free Stater It's not the years, it's the mileage. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEAREIAAYFAkpoqQcACgkQ0DfOju+hMklvqACgsHPUh/WpmfZjejvzIFn70LrK RCIAoNmMPmhPWk0NFM++ozVHERoMybAx =2k8M -----END PGP SIGNATURE----- From crystal.a.brewton at gmail.com Thu Jul 23 11:19:31 2009 From: crystal.a.brewton at gmail.com (Crystal Brewton) Date: Thu, 23 Jul 2009 11:19:31 -0700 Subject: [Enigmail] Multiple email addresses In-Reply-To: <4A68A907.5070909@metrocast.net> References: <4A68A702.2040405@gmail.com> <4A68A907.5070909@metrocast.net> Message-ID: <4A68A9B3.8040206@gmail.com> Good point and thank you for the info *smiles* Phil Stracchino wrote: > Crystal Brewton wrote: > > How did you manage that, if I may ask? I have OpenPGP as well as > > PorablePGP and would like to do this with a key, using two email addys. > > Also is it required to use a valid email address? > > It's trivial to add email addresses to a key. It's a standard key > management function. > With Enigmail, OpenPGP -> Key Management -> select key -> right-click -> > Manage User IDs -> Add. > From the command line with GnuPG, gpg --edit-keys -> adduid. > > There's nothing to stop you from adding an invalid email address to a > key if you really want to, but I fail to see what benefit there would be > to doing so, since if the address is invalid you can't send mail from it > and the additional uid will never get used. It would be a little like > adding an extra door onto your house that opens onto a blank wall. > > _______________________________________________ Enigmail mailing list Enigmail at mozdev.org https://www.mozdev.org/mailman/listinfo/enigmail From alaric at metrocast.net Thu Jul 23 11:20:56 2009 From: alaric at metrocast.net (Phil Stracchino) Date: Thu, 23 Jul 2009 14:20:56 -0400 Subject: [Enigmail] Multiple email addresses In-Reply-To: References: Message-ID: <4A68AA08.5050007@metrocast.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Roy Smith wrote: > Taistealaiche wrote: >> 2) If the above is possible, is it also possible for each email >> address to have a separate passphrase for that key? > > Unfortunately I don't think it's possible to do this. You might be able > to do this with PGP, but then PGP isn't free either. It's perfectly possible. You just can't have more than one passphrase per physical copy of the key. If you want multiple people to use the same key but have different passphrases for it, then they need to have their own distinct copies of the key. (I still don't see why you would want to do this. I'm still unable to think of a scenario in which this is actually a useful thing to do.) - -- Phil Stracchino, CDK#2 DoD#299792458 ICBM: 43.5607, -71.355 alaric at caerllewys.net alaric at metrocast.net phil at co.ordinate.org Renaissance Man, Unix ronin, Perl hacker, Free Stater It's not the years, it's the mileage. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEUEAREIAAYFAkpoqggACgkQ0DfOju+hMklGsQCXc9xtvYDSCW1GkmSHygTo6blH 3gCgjxmW6s0rdaaZD67GNLfZ9Wcb2VM= =gJWV -----END PGP SIGNATURE----- From alaric at metrocast.net Thu Jul 23 11:23:59 2009 From: alaric at metrocast.net (Phil Stracchino) Date: Thu, 23 Jul 2009 14:23:59 -0400 Subject: [Enigmail] Multiple email addresses In-Reply-To: <4A68A884.8000900@earthlights.net> References: <4A68A884.8000900@earthlights.net> Message-ID: <4A68AABF.4080201@metrocast.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Taistealaiche wrote: > Very many thanks for all your replies regarding this. It appears the > general consensus is that it isn't possible to have a separate > passphrase per user for the one key. Back to the drawing board :) Oh, it's perfectly doable, as I said yesterday afternoon. It merely requires distributing individual copies of the key and setting a different passphrase on each copy. You can't have multiple passphrases on a single copy of the key. What I still don't understand is why you would want to do such a thing. Let's approach this in a different way. What is the problem you are trying to solve? - -- Phil Stracchino, CDK#2 DoD#299792458 ICBM: 43.5607, -71.355 alaric at caerllewys.net alaric at metrocast.net phil at co.ordinate.org Renaissance Man, Unix ronin, Perl hacker, Free Stater It's not the years, it's the mileage. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEAREIAAYFAkpoqr8ACgkQ0DfOju+hMknDbACeMSm/JHjTiV9uOFHOythG4bBK cDMAoKuMChbL6+UkuhL7vl0mjJFur+rI =uTAj -----END PGP SIGNATURE----- From taistealaiche at earthlights.net Thu Jul 23 11:31:58 2009 From: taistealaiche at earthlights.net (Taistealaiche) Date: Fri, 24 Jul 2009 06:31:58 +1200 Subject: [Enigmail] Multiple email addresses In-Reply-To: <4A68AABF.4080201@metrocast.net> References: <4A68A884.8000900@earthlights.net> <4A68AABF.4080201@metrocast.net> Message-ID: <4A68AC9E.6010903@earthlights.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Phil, On 24/07/2009 6:23 a.m., Phil Stracchino wrote: > Taistealaiche wrote: >> Very many thanks for all your replies regarding this. It appears the >> general consensus is that it isn't possible to have a separate >> passphrase per user for the one key. Back to the drawing board :) > > Oh, it's perfectly doable, as I said yesterday afternoon. It merely > requires distributing individual copies of the key and setting a > different passphrase on each copy. You can't have multiple passphrases > on a single copy of the key. > > What I still don't understand is why you would want to do such a thing. > > Let's approach this in a different way. What is the problem you are > trying to solve? Mainly for access for our clients. In a corporate sense, although that's not what we are, it would be handy for clients to need to use only one Public Key which would, for example, have sales@, info@, manager@, etc, attached to it. Rather than needing a separate key for each of those individual emails. Taistealaiche at 6:28 a.m. on Friday, 24 July 2009 "Tha iomadh tonn eadar an long 's an t?r" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Are your emails secure? Comment: Always! encrypt sensitive emails iQEcBAEBAgAGBQJKaKyeAAoJENdHWlLnbf5PprgIAIoby9frKUpO1b3V+eCjzWU9 AaM7DUPJc8TzQzt8Mz+ZP5pzMRZgKyEWurmLQwmVbrNEtE9mgKLrWecoU8f3kEhl n5mg7AShhHuX/g1lQukdXKRisqMiiOtguB7ulGw7uyd9x42MDy4Psa4ixvJmyV1H YWCQMPgOqOBnORvhW67p/7VKjr21jOWVSBSkHPpAm1dg7J/a6YhPWSp5eVXYo5fL 1q4g9LWRT79Vf+3/7eKOGbcKTVtby962LAM2hkWeA9dgCVsYYSSfzs19eaCGPNho Nw7gFph8+nFKdTA62gVHJVly5ApdFgS2Tp9l9mlKW+1jR+WfswFFiWTzKnYrLkQ= =KEbQ -----END PGP SIGNATURE----- -------------- next part -------------- A non-text attachment was scrubbed... Name: 0xE76DFE4F.asc Type: application/pgp-keys Size: 1998 bytes Desc: not available URL: From rasmith1959 at gmail.com Thu Jul 23 11:36:00 2009 From: rasmith1959 at gmail.com (Roy Smith) Date: Thu, 23 Jul 2009 13:36:00 -0500 Subject: [Enigmail] Multiple email addresses In-Reply-To: References: Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Roy Smith wrote: > Taistealaiche wrote: >> Hi, >> I'm not sure if these questions belong on this list so please inform >> me if I'm wrong. >> >> 1) Is it possible, in the case of an organisation, to have one Public >> Key which can be tied to several different email addreses? > > It is possible to have one key with several email addresses, just take a > look at mine. > >> 2) If the above is possible, is it also possible for each email >> address to have a separate passphrase for that key? > > Unfortunately I don't think it's possible to do this. You might be able > to do this with PGP, but then PGP isn't free either. Well it would have leped is I had things set correctly.... - -- Roy Smith Windows XP Pro SP3 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkporZAACgkQsJ43Ti8ZtEZVcwCgzNsYXFMrvr3OSeWBOwWV5jnT QQYAoJeej2NVoMSL3VQrlvAowm6yJskC =AHE9 -----END PGP SIGNATURE----- From rasmith1959 at gmail.com Thu Jul 23 11:43:13 2009 From: rasmith1959 at gmail.com (Roy Smith) Date: Thu, 23 Jul 2009 13:43:13 -0500 Subject: [Enigmail] Multiple email addresses In-Reply-To: References: Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Phil Stracchino wrote: > Roy Smith wrote: >> Taistealaiche wrote: >>> 2) If the above is possible, is it also possible for each email >>> address to have a separate passphrase for that key? >> Unfortunately I don't think it's possible to do this. You might be able >> to do this with PGP, but then PGP isn't free either. > > It's perfectly possible. You just can't have more than one passphrase > per physical copy of the key. If you want multiple people to use the > same key but have different passphrases for it, then they need to have > their own distinct copies of the key. > > (I still don't see why you would want to do this. I'm still unable to > think of a scenario in which this is actually a useful thing to do.) Yeah I thought about that after I had already clicked on send... Not only would there be the problems you mentioned, but others would arise as well. Such as what if you had to remove an address or add one? The same goes for signatures to the key. It would just create a little more work on everyone's part as updates to the key wouldn't be automatic. - -- Roy Smith Windows XP Pro SP3 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkpor0EACgkQsJ43Ti8ZtEaP/QCffnNe4IhkX8BKvHwkuhz2IXa1 eioAnRUg+JoDX+32d2R35Chssx+jy2bd =53xp -----END PGP SIGNATURE----- From alaric at metrocast.net Thu Jul 23 11:49:46 2009 From: alaric at metrocast.net (Phil Stracchino) Date: Thu, 23 Jul 2009 14:49:46 -0400 Subject: [Enigmail] Multiple email addresses In-Reply-To: <4A68AC9E.6010903@earthlights.net> References: <4A68A884.8000900@earthlights.net> <4A68AABF.4080201@metrocast.net> <4A68AC9E.6010903@earthlights.net> Message-ID: <4A68B0CA.30402@metrocast.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Taistealaiche wrote: > Hi Phil, > > On 24/07/2009 6:23 a.m., Phil Stracchino wrote: >> Taistealaiche wrote: >>> Very many thanks for all your replies regarding this. It appears the >>> general consensus is that it isn't possible to have a separate >>> passphrase per user for the one key. Back to the drawing board :) >> Oh, it's perfectly doable, as I said yesterday afternoon. It merely >> requires distributing individual copies of the key and setting a >> different passphrase on each copy. You can't have multiple passphrases >> on a single copy of the key. > >> What I still don't understand is why you would want to do such a thing. > >> Let's approach this in a different way. What is the problem you are >> trying to solve? > > Mainly for access for our clients. In a corporate sense, although > that's not what we are, it would be handy for clients to need to use > only one Public Key which would, for example, have sales@, info@, > manager@, etc, attached to it. Rather than needing a separate key for > each of those individual emails. So if the multiple recipients [at your company] are all using the same "corporate key" anyway, why do they need separate passphrases for it? I don't see the gain. In fact, the whole scheme sounds much more complex than just making the individual public keys available to your clients in the first place. Unless the software they're using is totally broken, or you haven't actually published the keys anywhere, it should retrieve the correct public keys the first time you send them a signed message anyway. - -- Phil Stracchino, CDK#2 DoD#299792458 ICBM: 43.5607, -71.355 alaric at caerllewys.net alaric at metrocast.net phil at co.ordinate.org Renaissance Man, Unix ronin, Perl hacker, Free Stater It's not the years, it's the mileage. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEAREIAAYFAkposMoACgkQ0DfOju+hMklL5ACgjYPE1Hfca6E40xTg7JZnFsFg lbYAoKLBoRkArJ725YnAnjFsOEucWkjJ =i0gC -----END PGP SIGNATURE----- From alaric at metrocast.net Thu Jul 23 11:50:53 2009 From: alaric at metrocast.net (Phil Stracchino) Date: Thu, 23 Jul 2009 14:50:53 -0400 Subject: [Enigmail] Multiple email addresses In-Reply-To: References: Message-ID: <4A68B10D.2020205@metrocast.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Roy Smith wrote: > Phil Stracchino wrote: >> (I still don't see why you would want to do this. I'm still unable to >> think of a scenario in which this is actually a useful thing to do.) > > Yeah I thought about that after I had already clicked on send... Not > only would there be the problems you mentioned, but others would arise > as well. Such as what if you had to remove an address or add one? The > same goes for signatures to the key. It would just create a little more > work on everyone's part as updates to the key wouldn't be automatic. Precisely. It creates more problems than it solves. - -- Phil Stracchino, CDK#2 DoD#299792458 ICBM: 43.5607, -71.355 alaric at caerllewys.net alaric at metrocast.net phil at co.ordinate.org Renaissance Man, Unix ronin, Perl hacker, Free Stater It's not the years, it's the mileage. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEAREIAAYFAkposQ0ACgkQ0DfOju+hMknfUwCfU200BagPP+5qZvHPznsvLwIR NmoAoOAJpTAkFzdugknsELxPGZhYoY3D =/NZj -----END PGP SIGNATURE----- From allen.schultz at gmail.com Thu Jul 23 11:51:35 2009 From: allen.schultz at gmail.com (Allen Schultz) Date: Thu, 23 Jul 2009 12:51:35 -0600 Subject: [Enigmail] Multiple email addresses In-Reply-To: <4A68AC9E.6010903@earthlights.net> References: <4A68A884.8000900@earthlights.net> <4A68AABF.4080201@metrocast.net> <4A68AC9E.6010903@earthlights.net> Message-ID: <4A68B137.7010305@gmail.com> Taistealaiche wrote: > Mainly for access for our clients. In a corporate sense, although > that's not what we are, it would be handy for clients to need to use > only one Public Key which would, for example, have sales@, info@, > manager@, etc, attached to it. Rather than needing a separate key for > each of those individual emails. I hope this would generate some ideas. This was during the security issue in ADKs. A Simple Corporate Solution by vedaal http://www.gossamer-threads.com/lists/gnupg/users/42879?do=post_view_threaded is for the company to generate a gnupg keypair for each employee, have the employee change the passphrase as desired, and have the employees generate their own separate signing keys (not subkeys) then the company can simply inform all employees that any and all encrypted mail sent or received by the company must have a recipient key id that is on the company's 'accepted' list of employee encryption keys, or the corporate mail filter will discard it this way, the employees are responsible for their own signatures, which cannot be forged by the company, and are aware that the company can read all company related e-mail, and no patents are even remotely infringed upon employees who really want to deceive the company, can send encrypted files another way, (cdrw truecrypt containers by snail mail, using gnupg on private home computers etc.), and there is no simple solution to stop it. -- Allen Schultz GPG Key Info: pub 3072R/DAD4736B 2009-05-20 Key fingerprint = 16AD EFE1 D68F C8A8 B086 68CD 1A35 85C7 DAD4 736B uid Allen Schultz (aldaek) uid [jpeg image of size 6128] sub 2048R/F55651E0 2009-05-20 [expires: 2010-05-20] sub 2048R/5687B83E 2009-05-20 [expires: 2010-05-20] -------------- next part -------------- A non-text attachment was scrubbed... Name: allen_schultz.vcf Type: text/x-vcard Size: 589 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 551 bytes Desc: OpenPGP digital signature URL: From FerdinandoBellio at tele2.it Thu Jul 23 11:48:59 2009 From: FerdinandoBellio at tele2.it (Ferdinando Bellio) Date: Thu, 23 Jul 2009 20:48:59 +0200 Subject: [Enigmail] Chiave segreta Message-ID: <4A68B09B.9050000@tele2.it> Vorrei se possibile capire come mai se invio mail con OpenPGP in Thunderbird dal computer che chiamer? 1 e ricevuta sempre dal computer 1 me la riconosce come valida sia per la firma che per la cifrare ma se la apro con un altro pc in cui ? installato lo stesso OpenPGP e Thunderbird mi da messaggio :Errore - serve la chiave segreta per decifrare il messaggio; fai clic sull'icona della chiave per i dettagli . Preciso che la chiave per aprire la mail ? la stessa per i due pc. Se mi risolvete il problema ve ne sarei infinitamente grato. -- --- avast! Antivirus: In partenza messaggio pulito. Virus Database (VPS): 090722-0, 22/07/2009 Controllato il: 23/07/2009 20.49.00 avast! - copyright (c) 1988-2009 ALWIL Software. http://www.avast.com -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Firma x lettere.bmp Type: image/bmp Size: 112254 bytes Desc: not available URL: From John at Mozilla-Enigmail.org Thu Jul 23 12:28:57 2009 From: John at Mozilla-Enigmail.org (John Clizbe) Date: Thu, 23 Jul 2009 14:28:57 -0500 Subject: [Enigmail] Chiave segreta In-Reply-To: <4A68B09B.9050000@tele2.it> References: <4A68B09B.9050000@tele2.it> Message-ID: <4A68B9F9.5060905@Mozilla-Enigmail.org> Ferdinando Bellio wrote: > Vorrei se possibile capire come mai se invio mail con OpenPGP in > Thunderbird dal computer che chiamer? 1 e ricevuta sempre dal computer 1 > me la riconosce come valida sia per la firma che per la cifrare ma se la > apro con un altro pc in cui ? installato lo stesso OpenPGP e Thunderbird > mi da messaggio :Errore - serve la chiave segreta per decifrare il > messaggio; fai clic sull'icona della chiave per i dettagli . Preciso che > la chiave per aprire la mail ? la stessa per i due pc. > Se mi risolvete il problema ve ne sarei infinitamente grato. The usual language for this list is English. Could you please omit the signature graphic? It adds 150kB to what is normally a ~6kB message. How precisely did you move your key to the second machine? Moving just the public part would allow you to verify signed messages, but the secret part needs also to be copied to the second machine if you wish to decrypt messages. -- John P. Clizbe Inet:John (a) Mozilla-Enigmail.org You can't spell fiasco without SCO. hkp://keyserver.gingerbear.net or mailto:pgp-public-keys at gingerbear.net?subject=HELP Q:"Just how do the residents of Haiku, Hawai'i hold conversations?" A:"An odd melody / island voices on the winds / surplus of vowels" -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 679 bytes Desc: OpenPGP digital signature URL: From kilowattradio at comcast.net Sun Jul 26 10:14:50 2009 From: kilowattradio at comcast.net (Keith) Date: Sun, 26 Jul 2009 10:14:50 -0700 Subject: [Enigmail] MACGPG V2 (GNUPG 2) Removal problem with Enigmail Message-ID: <4A6C8F0A.9060603@comcast.net> I had to manually remove the GPG-AGENT V2 for gnupg2 and build and install gnupg v1.4. in MAC OS X Leopard. Now when I attempt to encrypt or sign an email enigmail on Thunderbird 2.0.0.22 it fails. When I go into OpenPGP preferences the applet states that gpg-agent is installed when I have removed it fully from the Applications Menu and the parts left over in various directories. Is there a setting some where in Enigmail or thunderbird that has to be reset or fixed to tell enigmail not to expect to use gpg-agent. Thanks for any help. -- Best Regards, Keith http://home.comcast.net/~kilowattradio/ From shavital at mac.com Sun Jul 26 11:05:22 2009 From: shavital at mac.com (Charly Avital) Date: Sun, 26 Jul 2009 14:05:22 -0400 Subject: [Enigmail] MACGPG V2 (GNUPG 2) Removal problem with Enigmail In-Reply-To: <4A6C8F0A.9060603@comcast.net> References: <4A6C8F0A.9060603@comcast.net> Message-ID: <4A6C9AE2.6010908@mac.com> Keith wrote the following on 7/26/09 1:14 PM: > I had to manually remove the GPG-AGENT V2 for gnupg2 and build and > install gnupg v1.4. in MAC OS X Leopard. Now when I attempt to encrypt > or sign an email enigmail on Thunderbird 2.0.0.22 it fails. When I go > into OpenPGP preferences the applet states that gpg-agent is installed > when I have removed it fully from the Applications Menu and the parts > left over in various directories. Is there a setting some where in > Enigmail or thunderbird that has to be reset or fixed to tell enigmail > not to expect to use gpg-agent. Thanks for any help. > In OpenPGP Preferences: 'Basic' - Please check that the path is correctly set to gpg and not to gpg2 (in Terminal "$ which gpg" should output the correct path to gpg - typically it's "/usr/local/bin/gpg"). No quotation marks. 'Advanced' - Please check that the option 'Use gpg-agent for passphrases' is *not* enabled. Please check that in your ~/.gnupg/gpg.conf file, the option use-agent is *not* enabled. For your information I am running MacGPG2 2.0.12, with gpg agent enabled and running, MacOSX 10.5.7, Thunderbird version 2.0.0.22 (20090605), Enigmail version 0.96.0 (20090717-0949), no problems. For issues related to MacGPG2 specifically, please see: MacGPG2 Project: Wiki: Mailing list: Charly From rjh at sixdemonbag.org Sun Jul 26 11:52:34 2009 From: rjh at sixdemonbag.org (Robert J. Hansen) Date: Sun, 26 Jul 2009 14:52:34 -0400 Subject: [Enigmail] MACGPG V2 (GNUPG 2) Removal problem with Enigmail In-Reply-To: <4A6C8F0A.9060603@comcast.net> References: <4A6C8F0A.9060603@comcast.net> Message-ID: <4A6CA5F2.9050105@sixdemonbag.org> Keith wrote: > I had to manually remove the GPG-AGENT V2 for gnupg2 and build and > install gnupg v1.4. Probably wise. Many of us here are skeptical of GnuPG 2; it seems to add very little that we need, and at the price of a lot of complexity, which we don't need. > Is there a setting some where in Enigmail or thunderbird that has to > be reset or fixed to tell enigmail not to expect to use gpg-agent. > Thanks for any help. Unfortunately, yes. OpenPGP Preferences --> Display expert settings Once you do that, you may need to close and re-open the Preferences window. (Some platforms you do, some don't. This is a Thunderbird weirdness, not an Enigmail weirdness.) OpenPGP Preferences --> Advanced Make sure "Use gpg-agent for passphrases" is unchecked. That should fix it. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 221 bytes Desc: OpenPGP digital signature URL: From kilowattradio at comcast.net Sun Jul 26 14:48:11 2009 From: kilowattradio at comcast.net (Keith) Date: Sun, 26 Jul 2009 14:48:11 -0700 Subject: [Enigmail] MACGPG V2 (GNUPG 2) Removal problem with Enigmail In-Reply-To: <4A6CA5F2.9050105@sixdemonbag.org> References: <4A6C8F0A.9060603@comcast.net> <4A6CA5F2.9050105@sixdemonbag.org> Message-ID: <4A6CCF1B.7010708@comcast.net> Robert J. Hansen wrote: > Keith wrote: >> I had to manually remove the GPG-AGENT V2 for gnupg2 and build and >> install gnupg v1.4. > > Probably wise. Many of us here are skeptical of GnuPG 2; it seems to > add very little that we need, and at the price of a lot of complexity, > which we don't need. > >> Is there a setting some where in Enigmail or thunderbird that has to >> be reset or fixed to tell enigmail not to expect to use gpg-agent. >> Thanks for any help. > > Unfortunately, yes. > > OpenPGP Preferences --> Display expert settings > > Once you do that, you may need to close and re-open the Preferences > window. (Some platforms you do, some don't. This is a Thunderbird > weirdness, not an Enigmail weirdness.) > > OpenPGP Preferences --> Advanced > > Make sure "Use gpg-agent for passphrases" is unchecked. > > That should fix it. > > > OK I missed that all is well now. I needed to add idea cipher support so that is why I rolled back to 1.4 and in the future I will try to build 2.x with idea, I just don't have the time right now to read the docs and install it properly. -- Best Regards, Keith http://home.comcast.net/~kilowattradio/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 250 bytes Desc: OpenPGP digital signature URL: From rjh at sixdemonbag.org Sun Jul 26 15:25:36 2009 From: rjh at sixdemonbag.org (Robert J. Hansen) Date: Sun, 26 Jul 2009 18:25:36 -0400 Subject: [Enigmail] MACGPG V2 (GNUPG 2) Removal problem with Enigmail In-Reply-To: <4A6CCF1B.7010708@comcast.net> References: <4A6C8F0A.9060603@comcast.net> <4A6CA5F2.9050105@sixdemonbag.org> <4A6CCF1B.7010708@comcast.net> Message-ID: > OK I missed that all is well now. I needed to add idea cipher > support so > that is why I rolled back to 1.4 and in the future I will try to build > 2.x with idea, I just don't have the time right now to read the docs > and > install it properly. I'm assuming that you get traffic from PGP 2.6 users who are only able to use IDEA? Because the alternative is ... well ... strange. IDEA is not part of RFC4880 (the OpenPGP Standard). The only time it's mentioned is for interoperability with the now-obsolete RFC1991 (the ClassicPGP Standard). If you have PGP 2.6 correspondents, then yes, you need IDEA support, and I hope you're gently prodding your correspondents to enter the 21st Century. If you don't, then no, you probably don't need IDEA support. IDEA was considered an excellent algorithm in the late 1980s and early 1990s. It has not aged well; better-than-brute-force attacks exist against at least four and a half of its eight rounds. Perhaps more -- I haven't bothered following IDEA cryptanalysis for at least five years or more now. From rjh at sixdemonbag.org Sun Jul 26 18:55:29 2009 From: rjh at sixdemonbag.org (Robert J. Hansen) Date: Sun, 26 Jul 2009 21:55:29 -0400 Subject: [Enigmail] MACGPG V2 (GNUPG 2) Removal problem with Enigmail In-Reply-To: References: <4A6C8F0A.9060603@comcast.net> <4A6CA5F2.9050105@sixdemonbag.org> <4A6CCF1B.7010708@comcast.net> Message-ID: <58615EDB-4D14-4F91-BDB4-4C2F45F5BB02@sixdemonbag.org> > IDEA was considered an excellent algorithm in the late 1980s and > early 1990s. It has not aged well; better-than-brute-force attacks > exist against at least four and a half of its eight rounds. Perhaps > more -- I haven't bothered following IDEA cryptanalysis for at least > five years or more now. Update: according to Wikipedia, the numbers are now up to six of eight rounds are broken. This just goes to show the truth of the old saw: attacks only get better over time. From stefanxe at gmx.net Mon Jul 27 06:51:12 2009 From: stefanxe at gmx.net (Stefan Xenon) Date: Mon, 27 Jul 2009 15:51:12 +0200 Subject: [Enigmail] Enigmail fails with GnuPG2 + OpenPGP Card In-Reply-To: <4A680726.3090403@mozilla-enigmail.org> References: <4A67532D.4010105@gmx.net> <4A680726.3090403@mozilla-enigmail.org> Message-ID: <4A6DB0D0.1010507@gmx.net> Also I experience that the Enigmail option, how long to store the passphrase, does not work with GnuPG. Is it possible to fix it for the next version please? Also I would be interested to know when you schedule to release the next version (roughly)? Patrick Brunschwig schrieb: > Stefan Xenon wrote: >> Hi! >> I use GnuPG2 and tried to generate a key on the OpenPGP Card. >> Unfortunately it failed with the error message "unbekannter Fehler bei >> Schl?sselgenerierung" (unknown error). The Enigmail console tells me the >> following command is executed: > >> C:\Program Files\GNU\GnuPG2\gpg2.exe --charset utf8 --no-tty --status- >> fd 1 --logger-fd 1 --command-fd 0 --with-colons --card-edit > >> It works on the same system when configuring Enigmail to use GnuPG v1. >> So maybe an compatibility issue with GnuPG v2? > > Yes, an incompatibility with GnuPG v2. I have fixed this a few days ago. > > In order to use gpg2, you will need a trunk version of Enigmail. Please > also note that generating keys and administration of GnuPG cards is > broken in Enigmail v0.96.0; it will be fixed in the next version of > Enigmail. > > -Patrick _______________________________________________ Enigmail mailing list Enigmail at mozdev.org https://www.mozdev.org/mailman/listinfo/enigmail From patrick at mozilla-enigmail.org Mon Jul 27 07:10:52 2009 From: patrick at mozilla-enigmail.org (Patrick Brunschwig) Date: Mon, 27 Jul 2009 16:10:52 +0200 Subject: [Enigmail] Enigmail fails with GnuPG2 + OpenPGP Card In-Reply-To: <4A6DB0D0.1010507@gmx.net> References: <4A67532D.4010105@gmx.net> <4A680726.3090403@mozilla-enigmail.org> <4A6DB0D0.1010507@gmx.net> Message-ID: <4A6DB56C.4060206@mozilla-enigmail.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 > Patrick Brunschwig schrieb: >> Stefan Xenon wrote: >>> Hi! >>> I use GnuPG2 and tried to generate a key on the OpenPGP Card. >>> Unfortunately it failed with the error message "unbekannter Fehler bei >>> Schl?sselgenerierung" (unknown error). The Enigmail console tells me the >>> following command is executed: >>> C:\Program Files\GNU\GnuPG2\gpg2.exe --charset utf8 --no-tty --status- >>> fd 1 --logger-fd 1 --command-fd 0 --with-colons --card-edit >>> It works on the same system when configuring Enigmail to use GnuPG v1. >>> So maybe an compatibility issue with GnuPG v2? >> Yes, an incompatibility with GnuPG v2. I have fixed this a few days ago. >> >> In order to use gpg2, you will need a trunk version of Enigmail. Please >> also note that generating keys and administration of GnuPG cards is >> broken in Enigmail v0.96.0; it will be fixed in the next version of >> Enigmail. >> > > Also I experience that the Enigmail option, how long to store the > passphrase, does not work with GnuPG. Is it possible to fix it for the > next version please? > > Also I would be interested to know when you schedule to release the next > version (roughly)? (Please place replies below the rest of the conversations.) With GnuPG 2, gpg-agent must be used (no way to avoid it). Therefore it is not possible to control the duration of how long the passphrase is remembered, since passphrase-remembering is handled by gpg-agent -- it cannot be fixed in Enigmail by any means. If you want to change the passhprase timeout settings, you'll need to create a gpg-agent.conf file in the same directory as your gpg.conf file. The next release will be ready when it's ready. Sorry, I can't be more precise than this. - -Patrick -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEVAwUBSm21a3cOpHodsOiwAQgLuAf+OYOPth/o8VB8XYIorN22KIS1bo3sLi7L MqYcRG5J7DCSEPr7nyzLgflVeERMlOplwVrpTRQe94WTBpPd9UdQ01gLJWto4YlW Vz5EjAs3UKkqACuU7fV0Ni/WiYJcydwl7AlS6M3nfoqhEUBLST6GX1uyRm2b0onN wOhv9GL9pGsNO68VvEwUFBDgINYZ1D0MeyYQNmhPlcaMKfuZ9vjUYq7yuv/R+pRR dB7oL9kONe4ndmEBx2tOemLHhpoCToYX94zGMI1Cqr1fm2mKAlmTQ/dpYns9838K Psahqwx01jCl+D0e4ezpKlUEB2BeszlCnsokkUcC1a7/mUGcTGhdag== =fMH8 -----END PGP SIGNATURE----- From shavital at mac.com Mon Jul 27 07:31:42 2009 From: shavital at mac.com (Charly Avital) Date: Mon, 27 Jul 2009 10:31:42 -0400 Subject: [Enigmail] Enigmail fails with GnuPG2 + OpenPGP Card In-Reply-To: <4A6DB56C.4060206@mozilla-enigmail.org> References: <4A67532D.4010105@gmx.net> <4A680726.3090403@mozilla-enigmail.org> <4A6DB0D0.1010507@gmx.net> <4A6DB56C.4060206@mozilla-enigmail.org> Message-ID: <4A6DBA4E.5020508@mac.com> Patrick Brunschwig wrote the following on 7/27/09 10:10 AM: [...] > With GnuPG 2, gpg-agent must be used (no way to avoid it). Therefore it > is not possible to control the duration of how long the passphrase is > remembered, since passphrase-remembering is handled by gpg-agent -- it > cannot be fixed in Enigmail by any means. > > If you want to change the passhprase timeout settings, you'll need to > create a gpg-agent.conf file in the same directory as your gpg.conf file. > > The next release will be ready when it's ready. Sorry, I can't be more > precise than this. > > -Patrick Stefan Xenon. For your information, this is how I set gpg-agent's passphrase timeout settings in ~/.gnupg/gpg-agent.conf file: default-cache-ttl [value in seconds, as per your choice] max-cache-ttl [value in seconds, as you set above] Charly MacOS 10.5.7 - MacBook Intel C2Duo 2GHz - MacGPG 2.0.12 TB 2.0.0.22+EM 0.96.0 - PGP Key: 0xA57A8EFA From stefanxe at gmx.net Tue Jul 28 00:12:14 2009 From: stefanxe at gmx.net (Stefan Xenon) Date: Tue, 28 Jul 2009 09:12:14 +0200 Subject: [Enigmail] Enigmail fails with GnuPG2 + OpenPGP Card In-Reply-To: <4A6DB56C.4060206@mozilla-enigmail.org> References: <4A67532D.4010105@gmx.net> <4A680726.3090403@mozilla-enigmail.org> <4A6DB0D0.1010507@gmx.net> <4A6DB56C.4060206@mozilla-enigmail.org> Message-ID: <4A6EA4CE.103@gmx.net> If Enigmail can not handle the duration of pass phrase caching along with GnuPG2 , I would propose to detect whether GnuPG v2 is used and to disable such option appropriately (and also displaying the reason in the configuration dialog). This would reduce user's confusion. Also note that GnuPG v2 is supposed to replace v1 in the future so that this will become a more relevant topic. Regards Patrick Brunschwig schrieb: >> Patrick Brunschwig schrieb: >>> Stefan Xenon wrote: >>>> Hi! >>>> I use GnuPG2 and tried to generate a key on the OpenPGP Card. >>>> Unfortunately it failed with the error message "unbekannter Fehler bei >>>> Schl?sselgenerierung" (unknown error). The Enigmail console tells me the >>>> following command is executed: >>>> C:\Program Files\GNU\GnuPG2\gpg2.exe --charset utf8 --no-tty --status- >>>> fd 1 --logger-fd 1 --command-fd 0 --with-colons --card-edit >>>> It works on the same system when configuring Enigmail to use GnuPG v1. >>>> So maybe an compatibility issue with GnuPG v2? >>> Yes, an incompatibility with GnuPG v2. I have fixed this a few days ago. >>> >>> In order to use gpg2, you will need a trunk version of Enigmail. Please >>> also note that generating keys and administration of GnuPG cards is >>> broken in Enigmail v0.96.0; it will be fixed in the next version of >>> Enigmail. >>> >> Also I experience that the Enigmail option, how long to store the >> passphrase, does not work with GnuPG. Is it possible to fix it for the >> next version please? > >> Also I would be interested to know when you schedule to release the next >> version (roughly)? > > (Please place replies below the rest of the conversations.) > > With GnuPG 2, gpg-agent must be used (no way to avoid it). Therefore it > is not possible to control the duration of how long the passphrase is > remembered, since passphrase-remembering is handled by gpg-agent -- it > cannot be fixed in Enigmail by any means. > > If you want to change the passhprase timeout settings, you'll need to > create a gpg-agent.conf file in the same directory as your gpg.conf file. > > The next release will be ready when it's ready. Sorry, I can't be more > precise than this. > > -Patrick _______________________________________________ Enigmail mailing list Enigmail at mozdev.org https://www.mozdev.org/mailman/listinfo/enigmail From patrick at mozilla-enigmail.org Tue Jul 28 00:42:08 2009 From: patrick at mozilla-enigmail.org (Patrick Brunschwig) Date: Tue, 28 Jul 2009 09:42:08 +0200 Subject: [Enigmail] Enigmail fails with GnuPG2 + OpenPGP Card In-Reply-To: <4A6EA4CE.103@gmx.net> References: <4A67532D.4010105@gmx.net> <4A680726.3090403@mozilla-enigmail.org> <4A6DB0D0.1010507@gmx.net> <4A6DB56C.4060206@mozilla-enigmail.org> <4A6EA4CE.103@gmx.net> Message-ID: <4A6EABD0.10909@mozilla-enigmail.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 > Patrick Brunschwig schrieb: >>> Patrick Brunschwig schrieb: >>>> Stefan Xenon wrote: >>>>> Hi! >>>>> I use GnuPG2 and tried to generate a key on the OpenPGP Card. >>>>> Unfortunately it failed with the error message "unbekannter Fehler bei >>>>> Schl?sselgenerierung" (unknown error). The Enigmail console tells me the >>>>> following command is executed: >>>>> C:\Program Files\GNU\GnuPG2\gpg2.exe --charset utf8 --no-tty --status- >>>>> fd 1 --logger-fd 1 --command-fd 0 --with-colons --card-edit >>>>> It works on the same system when configuring Enigmail to use GnuPG v1. >>>>> So maybe an compatibility issue with GnuPG v2? >>>> Yes, an incompatibility with GnuPG v2. I have fixed this a few days ago. >>>> >>>> In order to use gpg2, you will need a trunk version of Enigmail. Please >>>> also note that generating keys and administration of GnuPG cards is >>>> broken in Enigmail v0.96.0; it will be fixed in the next version of >>>> Enigmail. >>>> >>> Also I experience that the Enigmail option, how long to store the >>> passphrase, does not work with GnuPG. Is it possible to fix it for the >>> next version please? >>> Also I would be interested to know when you schedule to release the next >>> version (roughly)? >> (Please place replies below the rest of the conversations.) >> >> With GnuPG 2, gpg-agent must be used (no way to avoid it). Therefore it >> is not possible to control the duration of how long the passphrase is >> remembered, since passphrase-remembering is handled by gpg-agent -- it >> cannot be fixed in Enigmail by any means. >> >> If you want to change the passhprase timeout settings, you'll need to >> create a gpg-agent.conf file in the same directory as your gpg.conf file. >> >> The next release will be ready when it's ready. Sorry, I can't be more >> precise than this. >> Stefan Xenon wrote: > If Enigmail can not handle the duration of pass phrase caching along > with GnuPG2 , I would propose to detect whether GnuPG v2 is used and to > disable such option appropriately (and also displaying the reason in the > configuration dialog). > > This would reduce user's confusion. Also note that GnuPG v2 is supposed > to replace v1 in the future so that this will become a more relevant topic. done in v0.96.0 - -Patrick -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEVAwUBSm6rz3cOpHodsOiwAQiTPwf7BQyN2v+yuTIz/V3PHj0Z2f0qRKUAI/jx mHuCF7z8Wua2OHPLJa+OOYivFM5tt35uPA0Z2J5DgLpEm6wY83TKw9mjOUtYr6PW yzzs7g+jxxAldEqGeb9kAty0hLNSkmuS/j9IJI3/lYh2h0b7QR1jgYEl+L/0Vaw0 /yb4x2ltuwGXiFUvn6SHXPhIA/ht0nEa2BtZyUwU4hU8+m+M3Rucoit9+9VkENeZ RHdR7E0yoFLjK9HWMn+R9hsO0l5hv6xGU3PYsRdPmGMdIvi/ZBh4Bd0KgB1JmT6w M2mU5ITuCJx3UForq3Xdqyg9UMu8nc9LhmtbX0EMcprVtixH43ophg== =7w0W -----END PGP SIGNATURE----- From stefanxe at gmx.net Tue Jul 28 01:16:05 2009 From: stefanxe at gmx.net (Stefan Xenon) Date: Tue, 28 Jul 2009 10:16:05 +0200 Subject: [Enigmail] Enigmail fails with GnuPG2 + OpenPGP Card In-Reply-To: <4A6EABD0.10909@mozilla-enigmail.org> References: <4A67532D.4010105@gmx.net> <4A680726.3090403@mozilla-enigmail.org> <4A6DB0D0.1010507@gmx.net> <4A6DB56C.4060206@mozilla-enigmail.org> <4A6EA4CE.103@gmx.net> <4A6EABD0.10909@mozilla-enigmail.org> Message-ID: <4A6EB3C5.3080000@gmx.net> I am using v0.96.0 and for me it ist not implemented as described. In the attached screenshot you can see that I use GnuPG v2 but the option to configure the duration is still active. Let me describe my suggestion again: As I understood, Enigmail can not define the duration of pass phrase caching when using GnuPG v2, but it works with v1. Because of this when GnuPG v2 is used the option to configure the duration should be disabled (because it doesn't work anyway). Instead it should be enabled when using GnuPG v1 (because it works with v1). Just my two cents... Patrick Brunschwig schrieb: >> Patrick Brunschwig schrieb: >>>> Patrick Brunschwig schrieb: >>>>> Stefan Xenon wrote: >>>>>> Hi! >>>>>> I use GnuPG2 and tried to generate a key on the OpenPGP Card. >>>>>> Unfortunately it failed with the error message "unbekannter Fehler bei >>>>>> Schl?sselgenerierung" (unknown error). The Enigmail console tells me the >>>>>> following command is executed: >>>>>> C:\Program Files\GNU\GnuPG2\gpg2.exe --charset utf8 --no-tty --status- >>>>>> fd 1 --logger-fd 1 --command-fd 0 --with-colons --card-edit >>>>>> It works on the same system when configuring Enigmail to use GnuPG v1. >>>>>> So maybe an compatibility issue with GnuPG v2? >>>>> Yes, an incompatibility with GnuPG v2. I have fixed this a few days ago. >>>>> >>>>> In order to use gpg2, you will need a trunk version of Enigmail. Please >>>>> also note that generating keys and administration of GnuPG cards is >>>>> broken in Enigmail v0.96.0; it will be fixed in the next version of >>>>> Enigmail. >>>>> >>>> Also I experience that the Enigmail option, how long to store the >>>> passphrase, does not work with GnuPG. Is it possible to fix it for the >>>> next version please? >>>> Also I would be interested to know when you schedule to release the next >>>> version (roughly)? >>> (Please place replies below the rest of the conversations.) >>> >>> With GnuPG 2, gpg-agent must be used (no way to avoid it). Therefore it >>> is not possible to control the duration of how long the passphrase is >>> remembered, since passphrase-remembering is handled by gpg-agent -- it >>> cannot be fixed in Enigmail by any means. >>> >>> If you want to change the passhprase timeout settings, you'll need to >>> create a gpg-agent.conf file in the same directory as your gpg.conf file. >>> >>> The next release will be ready when it's ready. Sorry, I can't be more >>> precise than this. >>> > Stefan Xenon wrote: >> If Enigmail can not handle the duration of pass phrase caching along >> with GnuPG2 , I would propose to detect whether GnuPG v2 is used and to >> disable such option appropriately (and also displaying the reason in the >> configuration dialog). > >> This would reduce user's confusion. Also note that GnuPG v2 is supposed >> to replace v1 in the future so that this will become a more relevant > topic. > > > done in v0.96.0 > > -Patrick _______________________________________________ Enigmail mailing list Enigmail at mozdev.org https://www.mozdev.org/mailman/listinfo/enigmail -------------- next part -------------- A non-text attachment was scrubbed... Name: preferences.png Type: image/png Size: 4409 bytes Desc: not available URL: From patrick at mozilla-enigmail.org Tue Jul 28 02:24:24 2009 From: patrick at mozilla-enigmail.org (Patrick Brunschwig) Date: Tue, 28 Jul 2009 11:24:24 +0200 Subject: [Enigmail] Enigmail fails with GnuPG2 + OpenPGP Card In-Reply-To: <4A6EB3C5.3080000@gmx.net> References: <4A67532D.4010105@gmx.net> <4A680726.3090403@mozilla-enigmail.org> <4A6DB0D0.1010507@gmx.net> <4A6DB56C.4060206@mozilla-enigmail.org> <4A6EA4CE.103@gmx.net> <4A6EABD0.10909@mozilla-enigmail.org> <4A6EB3C5.3080000@gmx.net> Message-ID: <4A6EC3C8.4030207@mozilla-enigmail.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Stefan Xenon wrote: > I am using v0.96.0 and for me it ist not implemented as described. In > the attached screenshot you can see that I use GnuPG v2 but the option > to configure the duration is still active. > > Let me describe my suggestion again: As I understood, Enigmail can not > define the duration of pass phrase caching when using GnuPG v2, but it > works with v1. Because of this when GnuPG v2 is used the option to > configure the duration should be disabled (because it doesn't work > anyway). Instead it should be enabled when using GnuPG v1 (because it > works with v1). > > Just my two cents... The problem is that while you are defining the path to gpg, it's not possible to know if gpg2 is used or not, so the option cannot be just disabled at this moment. The check for gpg-agent is done once you click OK. You'll get a warning dialog saying that the passphrase timeout might not be respected. If you don't get that dialog, then you have probably seen that dialog before and clicked on "do not show this message again". The above is how the process /should/ work. It could be however, that things behave differently on Windows, since gpg-agent is started automatically by gpg2; I must admit I never checked this since I hardly use Windows... - -Patrick -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEVAwUBSm7Dx3cOpHodsOiwAQijKQf+NONQTCRdt+B5ze3HuPkUobf8Oh+Y0XR+ KouLcT7xFhQGrXOBBm6h2zRKKw0KKfxE51wv2vWCnEsVBmaKpJp5Ea8D+t+5ZdgS u5rMcKsKWbje6Ir5V+PWX29nd1xc7P7t5WX7rn1BV8qeovoGIPiJGqwIl4I4lw9b dGHQ6Ef+KPBmPRlNmJ2KS+lAO8o+aH0nmtlzzPqhcZ3/jrH4DiYJO0/JKgyBKDl5 gRGQK/4I5MSVKVT/USED2NpyN/XJTUhv9ZEbk/wWjrBahmFjpLw3RDX24bzQl655 /lUNJ3uG1jdnJExXOic4ukD+e3vkzBTwZTQ3EG7SSVFBGZ+pFpkFoQ== =ZN3x -----END PGP SIGNATURE----- From olav at mozilla-enigmail.org Tue Jul 28 03:06:53 2009 From: olav at mozilla-enigmail.org (Olav Seyfarth) Date: Tue, 28 Jul 2009 12:06:53 +0200 Subject: [Enigmail] Enigmail fails with GnuPG2 + OpenPGP Card In-Reply-To: <4A6EC3C8.4030207@mozilla-enigmail.org> References: <4A67532D.4010105@gmx.net> <4A680726.3090403@mozilla-enigmail.org> <4A6DB0D0.1010507@gmx.net> <4A6DB56C.4060206@mozilla-enigmail.org> <4A6EA4CE.103@gmx.net> <4A6EABD0.10909@mozilla-enigmail.org> <4A6EB3C5.3080000@gmx.net> <4A6EC3C8.4030207@mozilla-enigmail.org> Message-ID: <4A6ECDBD.8060109@mozilla-enigmail.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi *, > The check for gpg-agent is done once you click OK. You'll get a warning > dialog saying that the passphrase timeout might not be respected. If you > don't get that dialog, then you have probably seen that dialog before > and clicked on "do not show this message again". this exactly what happens on my Windows installation. > The above is how the process /should/ work. It could be however, that > things behave differently on Windows, since gpg-agent is started > automatically by gpg2; I must admit I never checked this since I hardly > use Windows... Works perfectly fine for me on WXPPro and W7RC. Olav P.S.: Stefan: Please don't top-post and cite all but only what's necessary to answer shortly. Readers have read and mostly will still have all previous posts. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEAREIAAYFAkpuzboACgkQL/NBt8fdKe3DPwCgq4XsuMI9gUPBKHzVqvsQqJM3 6DsAn0K2BTS610QV0iTS9G7albwX6TrF =vldA -----END PGP SIGNATURE----- From erico.mendonca at gmail.com Tue Jul 28 07:54:45 2009 From: erico.mendonca at gmail.com (=?ISO-8859-1?Q?Erico_Mendon=E7a?=) Date: Tue, 28 Jul 2009 11:54:45 -0300 Subject: [Enigmail] Enigmail fails with GnuPG2 + OpenPGP Card In-Reply-To: <4A6EC3C8.4030207@mozilla-enigmail.org> References: <4A67532D.4010105@gmx.net> <4A680726.3090403@mozilla-enigmail.org> <4A6DB0D0.1010507@gmx.net> <4A6DB56C.4060206@mozilla-enigmail.org> <4A6EA4CE.103@gmx.net> <4A6EABD0.10909@mozilla-enigmail.org> <4A6EB3C5.3080000@gmx.net> <4A6EC3C8.4030207@mozilla-enigmail.org> Message-ID: On Tue, Jul 28, 2009 at 6:24 AM, Patrick Brunschwig < patrick at mozilla-enigmail.org> wrote: > > The problem is that while you are defining the path to gpg, it's not > possible to know if gpg2 is used or not, so the option cannot be just > disabled at this moment. > > Actually there is: try to run it with the option "--version" and fetch the first line. Here's the output for both: [slaughter at slaughterhouse ~]$ gpg --version gpg (GnuPG) 1.4.9 Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Home: ~/.gnupg Algoritmos suportados: Chave p?blica: RSA, RSA-E, RSA-S, ELG-E, DSA Cifra: 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH Dispers?o: MD5, SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224 Compress?o: Uncompressed, ZIP, ZLIB, BZIP2 [slaughter at slaughterhouse ~]$ gpg2 --version gpg (GnuPG) 2.0.11 libgcrypt 1.4.4 Copyright (C) 2009 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Home: ~/.gnupg Algoritmos suportados: Chave p?blica: RSA, ELG, DSA Cifra: 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH Dispers?o: MD5, SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224 Compress?o: Uncompressed, ZIP, ZLIB, BZIP2 -- -- Erico -------------- next part -------------- An HTML attachment was scrubbed... URL: From patrick at mozilla-enigmail.org Tue Jul 28 08:28:00 2009 From: patrick at mozilla-enigmail.org (Patrick Brunschwig) Date: Tue, 28 Jul 2009 17:28:00 +0200 Subject: [Enigmail] Enigmail fails with GnuPG2 + OpenPGP Card In-Reply-To: References: <4A67532D.4010105@gmx.net> <4A680726.3090403@mozilla-enigmail.org> <4A6DB0D0.1010507@gmx.net> <4A6DB56C.4060206@mozilla-enigmail.org> <4A6EA4CE.103@gmx.net> <4A6EABD0.10909@mozilla-enigmail.org> <4A6EB3C5.3080000@gmx.net> <4A6EC3C8.4030207@mozilla-enigmail.org> Message-ID: <4A6F1900.1020504@mozilla-enigmail.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Erico Mendon?a wrote: > > > On Tue, Jul 28, 2009 at 6:24 AM, Patrick Brunschwig > > wrote: > > > The problem is that while you are defining the path to gpg, it's not > possible to know if gpg2 is used or not, so the option cannot be just > disabled at this moment. > > > > Actually there is: try to run it with the option "--version" and fetch > the first line. > > Here's the output for both: > > > [slaughter at slaughterhouse ~]$ gpg --version Right, that's what I do --but I don't want to do this _before_ the user clicks on OK. - -Patrick -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEVAwUBSm8Y/ncOpHodsOiwAQgcRggApeI7GB49n5t0d8rr9qYWUoLJLGSKOpyz P5WjiXs/on4rRB3EM8HVV2LCaVHYa7xGedh3WV7xZlWLOG4R129jDrC9EFduCK3B xDH5+roYtRdLWcKp0fTrc29xwLyEViZmMO5FA77Zq0ok7LPxB3jIeN2jkh7DX1KY tnqYYkGlP7wcka+Jz/Ypl65+lS1rMzmrv3OlDsX8Le2uoVEnB3bTRL7KOOUJSPu1 YG8IodpMmS9ExLD2Ug4Ier52oZanC9nweQGktr0dBmodKKJkKeRBK5KijagrkIf0 oooKWg/uapRSPxjlUKGJ0oxxGUEP5bYRzucdsg2erAolq7wvM786Wg== =SxLq -----END PGP SIGNATURE----- From erico.mendonca at gmail.com Tue Jul 28 08:38:49 2009 From: erico.mendonca at gmail.com (=?ISO-8859-1?Q?Erico_Mendon=E7a?=) Date: Tue, 28 Jul 2009 12:38:49 -0300 Subject: [Enigmail] Enigmail fails with GnuPG2 + OpenPGP Card In-Reply-To: <4A6F1900.1020504@mozilla-enigmail.org> References: <4A67532D.4010105@gmx.net> <4A680726.3090403@mozilla-enigmail.org> <4A6DB0D0.1010507@gmx.net> <4A6DB56C.4060206@mozilla-enigmail.org> <4A6EA4CE.103@gmx.net> <4A6EABD0.10909@mozilla-enigmail.org> <4A6EB3C5.3080000@gmx.net> <4A6EC3C8.4030207@mozilla-enigmail.org> <4A6F1900.1020504@mozilla-enigmail.org> Message-ID: On Tue, Jul 28, 2009 at 12:28 PM, Patrick Brunschwig < patrick at mozilla-enigmail.org> wrote: > > > > Actually there is: try to run it with the option "--version" and fetch > > the first line. > > > > Here's the output for both: > > > > > > [slaughter at slaughterhouse ~]$ gpg --version > > > Right, that's what I do --but I don't want to do this _before_ the user > clicks on OK. > > It may sound stupid and inefficient, but some programs do it like this: 1. Monitor what is being typed on the field. 2. If the user stops typing for more than 2 seconds, try to check if the binary exists (in our case, run it with --version) 3. update the status line (e.g. "Found GPG version x.x" or "invalid executable") 4. repeat until success. Or make the field "uneditable" and add a "Browse..." button to it. The check will be made when the user ends the file selection dialog. -- -- Erico -------------- next part -------------- An HTML attachment was scrubbed... URL: From patrick at mozilla-enigmail.org Tue Jul 28 08:50:22 2009 From: patrick at mozilla-enigmail.org (Patrick Brunschwig) Date: Tue, 28 Jul 2009 17:50:22 +0200 Subject: [Enigmail] Enigmail fails with GnuPG2 + OpenPGP Card In-Reply-To: References: <4A67532D.4010105@gmx.net> <4A680726.3090403@mozilla-enigmail.org> <4A6DB0D0.1010507@gmx.net> <4A6DB56C.4060206@mozilla-enigmail.org> <4A6EA4CE.103@gmx.net> <4A6EABD0.10909@mozilla-enigmail.org> <4A6EB3C5.3080000@gmx.net> <4A6EC3C8.4030207@mozilla-enigmail.org> <4A6F1900.1020504@mozilla-enigmail.org> Message-ID: <4A6F1E3E.6020205@mozilla-enigmail.org> Erico Mendon?a wrote: > > > On Tue, Jul 28, 2009 at 12:28 PM, Patrick Brunschwig > > wrote: > > > > > Actually there is: try to run it with the option "--version" and fetch > > the first line. > > > > Here's the output for both: > > > > > > [slaughter at slaughterhouse ~]$ gpg --version > > > Right, that's what I do --but I don't want to do this _before_ the user > clicks on OK. > > > > It may sound stupid and inefficient, but some programs do it like this: > > 1. Monitor what is being typed on the field. > 2. If the user stops typing for more than 2 seconds, try to check if the > binary exists (in our case, run it with --version) > 3. update the status line (e.g. "Found GPG version x.x" or "invalid > executable") > 4. repeat until success. Believe it or not, but I considered this option -- and decided against it for various reasons. > Or make the field "uneditable" and add a "Browse..." button to it. The > check will be made when the user ends the file selection dialog. There is a text entry field and a "Browse ..." button on the dialog. -Patrick From kyshk at bc.iij4u.or.jp Wed Jul 29 09:10:47 2009 From: kyshk at bc.iij4u.or.jp (kyshk at bc.iij4u.or.jp) Date: Thu, 30 Jul 2009 01:10:47 +0900 Subject: [Enigmail] Unusable Japanese language. (Was Re: [ANN] Enigmail v0.96.0 available In-Reply-To: <4A65C547.5090200@bc.iij4u.or.jp> References: <4A6046E1.4070009@mozilla-enigmail.org> <4A65C547.5090200@bc.iij4u.or.jp> Message-ID: <4A707487.70504@bc.iij4u.or.jp> extensions.enigmail.warnIso2022jp process deleted. and compulsory change from ISO-2022-JP to UTF-8. it's not in Changelog. Please check the your source code. At Tue Jul 21 2009 22:40:23 GMT+0900 , kyshk at bc.iij4u.or.jp wrote: > Hi! > Enigmail is always dependable. > > I tried the Enigmail 0.96.0 but It is unusable Japanese language. It can > not send ISO-2022-JP encode encrypt message. > > bad Thunderbird - Enigmail encode linkage. > (Enigmail 0.95.7 is OK) > > > ,----[ example ]- send non PGP/MIME ISO-2022-JP encrypt message > | X-Enigmail-Version: 0.96.0 > | Content-Type: text/plain; charset=UTF-8 > | Content-Transfer-Encoding: 8bit > | Status: U > | > | -----BEGIN PGP MESSAGE----- > | Charset: ISO-2022-JP > | Version: GnuPG v1.4.8 (MingW32) > | Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > `---- > > > ,----[ not ]- > | Content-Type: text/plain; charset=UTF-8 > | Content-Transfer-Encoding: 8bit > `---- > > ,----[ but ]- > | Content-Type: text/plain; charset=ISO-2022-JP > | Content-Transfer-Encoding: 7bit > `---- > > use: > Thunderbird 2.0.0.22 (20090605) > Enigmail 0.96.0 (20090717-0949) > settings: > --rfc2440 > extensions.enigmail.warnIso2022jp=2 > > source message encoding is ISO-2022-JP > > 1.non PGP/MIME encrypt :UTF-8 (bad) > 2.non PGP/MIME signed :ISO-2022-JP (good) > 3.non PGP/MIME signed+encrypt :UTF-8 (bad) > 4.PGP/MIME encrypt :UTF-8 (bad) > 5.PGP/MIME signed :UTF-8 (bad) > 6.PGP/MIME signed+encrypt :UTF-8 (bad) > > message(1,3,4,5,6) maybe can not read other MUA. (mojibake) > Content-Type header be distinct from contents. > > Thunderbird 2.0.0.22 can not accurate encode. > (wrong Content-Type header) > Enigmail ignore [extensions.enigmail.warnIso2022jp] param. > > and Japanese standard encrypt(or signed) message is NO UTF-8 and NO > quoted-printable. > -- > kiyo > _______________________________________________ > Enigmail mailing list > Enigmail at mozdev.org > https://www.mozdev.org/mailman/listinfo/enigmail > From cherock at hughes.net Thu Jul 30 19:33:56 2009 From: cherock at hughes.net (Clois Beckwith) Date: Thu, 30 Jul 2009 21:33:56 -0500 Subject: [Enigmail] A newbie to encryption, needs a test buddy Message-ID: <4A725814.6030906@hughes.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 A newbie to encryption needs a test buddy or buddies. I need a few individuals that can help me get my e-mail signing and encryption from baby steps to being able to function as an adult. Any Takers? Just to give you a little history as to why I am here. I read that all e-mail sent across the internet becomes "Public Domain" after 90 days, meaning anybody and everybody can intercept and read anybodies e-mail. This disturbs me. So I want to get a firm understanding of encryption and signing under my belt so I am comfortable with doing it on my machine and assisting others to do as well. I personally don't like the fact that someone could be intercepting and reading my personal e-mail without my knowledge. So I am game to prevent that from happening. Just e-mail me back. I will sign this document, if you would send me your public keys, or give me the 8 digit key number or tell me what KeyServer you have it on I will play with the servers. I will also attach my key and tell you what the number of my key is on this e-mail, if you would like to play.... Key number is 0x3590E2BC My public key attached. Thanks for any help that you can provide. I appreciate everyones time and I don't want to abuse your time, either.... Sincerely, Clois Beckwith -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAkpyWBQACgkQGJdJnzWQ4rxCEwCfaP7PaMpS8pldNvxS1yFo1oA6 md0AoNnF97mT5ExtlGyiQlJ3y6qsSiLE =sG7s -----END PGP SIGNATURE----- -------------- next part -------------- A non-text attachment was scrubbed... Name: 0x3590E2BC.asc Type: application/pgp-keys Size: 2405 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 0x3590E2BC.asc.sig Type: application/pgp-signature Size: 72 bytes Desc: not available URL: From rjh at sixdemonbag.org Thu Jul 30 19:58:08 2009 From: rjh at sixdemonbag.org (Robert J. Hansen) Date: Thu, 30 Jul 2009 22:58:08 -0400 Subject: [Enigmail] A newbie to encryption, needs a test buddy In-Reply-To: <4A725814.6030906@hughes.net> References: <4A725814.6030906@hughes.net> Message-ID: <298CB1AD-55C4-49BA-BC0F-CD280AA25FD5@sixdemonbag.org> > A newbie to encryption needs a test buddy or buddies. I need a few > individuals that can help me get my e-mail signing and encryption > from > baby steps to being able to function as an adult. Any Takers? While some people here will probably volunteer, you will have better luck asking on the PGP-Basics group over at Yahoo! Groups. http://tech.groups.yahoo.com/group/PGP-Basics/ > Just to give you a little history as to why I am here. I read that all > e-mail sent across the internet becomes "Public Domain" after 90 days, > meaning anybody and everybody can intercept and read anybodies e-mail. This is not true. It's so far from the truth that, if I were you, I would be genuinely angry at whoever told me this. In the United States there's a lot of federal law which makes it a federal offense to intercept email or to, without proper authorization, access it while it's in storage at an ISP; most other countries have similar laws. For an example of just one applicable U.S. law, see the Stored Communications Act (18 USC 2701 through to 18 USC 2712). You can read an overview of it at: http://en.wikipedia.org/wiki/Stored_Communications_Act Once more, whoever told you this was either grossly ignorant or was outright lying to you. -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 187 bytes Desc: This is a digitally signed message part URL: From jmoore3rd at bellsouth.net Thu Jul 30 20:24:49 2009 From: jmoore3rd at bellsouth.net (John W. Moore III) Date: Thu, 30 Jul 2009 23:24:49 -0400 Subject: [Enigmail] A newbie to encryption, needs a test buddy In-Reply-To: <298CB1AD-55C4-49BA-BC0F-CD280AA25FD5@sixdemonbag.org> References: <4A725814.6030906@hughes.net> <298CB1AD-55C4-49BA-BC0F-CD280AA25FD5@sixdemonbag.org> Message-ID: <4A726401.3010701@bellsouth.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Robert J. Hansen wrote: > This is not true. It's so far from the truth that, if I were you, I > would be genuinely angry at whoever told me this. In the United States > there's a lot of federal law which makes it a federal offense to > intercept email or to, without proper authorization, access it while > it's in storage at an ISP; most other countries have similar laws. > > For an example of just one applicable U.S. law, see the Stored > Communications Act (18 USC 2701 through to 18 USC 2712). You can read > an overview of it at: > > http://en.wikipedia.org/wiki/Stored_Communications_Act > > Once more, whoever told you this was either grossly ignorant or was > outright lying to you. I cannot find fault with Robert's legal citations. I can & will point out the nebulous phrase 'proper authorization' and ask anyone if they can succinctly and accurately define just what it constitutes in the age of the Patriot Act and the routine tasks performed by System Engineers. While I seriously doubt that anyone's Email is 'thrown open to the Public' at any time; I am confident that everyone's Email is exposed to thousands of eyes at any given time. Even Google, with Gmail, electronically 'scans' the body of Email for 'clues' on which ads to target toward the recipient. JOHN ;) Timestamp: Thursday 30 Jul 2009, 23:24 --400 (Eastern Daylight Time) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10-svn5085: (MingW32) Comment: Public Key at: http://tinyurl.com/8cpho Comment: Gossamer Spider Web of Trust: http://www.gswot.org Comment: Personal Web Page: http://tinyurl.com/yzhbhx iQEcBAEBCgAGBQJKcmP9AAoJEBCGy9eAtCsPQ78H/0Zep7ODVaa0qyQIA6GBNhMB vDKBbg6+0g1k40TJUjgqbayXecMgEGkoHGtVU6acFyKa+tMv9DrmBkZmkIdPNJyz fJqukO/E7nBcoD6WHuS2aXPONY4ILaqgOdTgjAfX5Y68OJXu1W82KX2yNVQiM6kg SUSgfBFbkgAJaZMyUID5+dbV8ufZwNmreBFR1hprNhIQ5K/UAXlOo3Zm9o6Yzf70 hACLgJBgiJf+3iCMLxDrbkFjHSrAZuHnPv7B6DBZc6MSxcUDobsSsIDdKjGk3j4+ yc88mQ4tgMh7ctQ4Qrctcaoc6vLoECVFoD0quUKoAZO2l/YlSX9mEqe7tE7n42A= =3nxp -----END PGP SIGNATURE----- From allen.schultz at gmail.com Thu Jul 30 21:54:59 2009 From: allen.schultz at gmail.com (Allen Schultz) Date: Thu, 30 Jul 2009 22:54:59 -0600 Subject: [Enigmail] A newbie to encryption, needs a test buddy In-Reply-To: <298CB1AD-55C4-49BA-BC0F-CD280AA25FD5@sixdemonbag.org> References: <4A725814.6030906@hughes.net> <298CB1AD-55C4-49BA-BC0F-CD280AA25FD5@sixdemonbag.org> Message-ID: <3f34f8420907302154n447f1fb9rcc5c470e790b03d6@mail.gmail.com> On Thu, Jul 30, 2009 at 8:58 PM, Robert J. Hansen wrote: > This is not true. ?It's so far from the truth that, if I were you, I would > be genuinely angry at whoever told me this. ?In the United States there's a > lot of federal law which makes it a federal offense to intercept email or > to, without proper authorization, access it while it's in storage at an ISP; > most other countries have similar laws. Yes, while that is true, the owner of the equipment is responsible for any data/programs on that computer, which requires them to review/audit every once in awhile. Allen From allen.schultz at gmail.com Thu Jul 30 21:59:42 2009 From: allen.schultz at gmail.com (Allen Schultz) Date: Thu, 30 Jul 2009 22:59:42 -0600 Subject: [Enigmail] A newbie to encryption, needs a test buddy In-Reply-To: <298CB1AD-55C4-49BA-BC0F-CD280AA25FD5@sixdemonbag.org> References: <4A725814.6030906@hughes.net> <298CB1AD-55C4-49BA-BC0F-CD280AA25FD5@sixdemonbag.org> Message-ID: <3f34f8420907302159q784d2b22j85e3ba3f8139fc85@mail.gmail.com> On Thu, Jul 30, 2009 at 8:58 PM, Robert J. Hansen wrote: > Stored Communications Act Does this protect data in-transition? There are a lot of packet capture/watcher tools for use to keep malicious use of equipment down, e-mails are still clear-text on unsecured connections while in transition. Someone just has to be connected to the network where the e-mail is connected to capture said e-mail along with thousands of other packets. Allen From dgboles at gmail.com Thu Jul 30 22:06:18 2009 From: dgboles at gmail.com (David Boles) Date: Fri, 31 Jul 2009 01:06:18 -0400 Subject: [Enigmail] A newbie to encryption, needs a test buddy In-Reply-To: <4A725814.6030906@hughes.net> References: <4A725814.6030906@hughes.net> Message-ID: <4A727BCA.9050603@gmail.com> Clois Beckwith wrote: > A newbie to encryption needs a test buddy or buddies. I need a few > individuals that can help me get my e-mail signing and encryption from > baby steps to being able to function as an adult. Any Takers? > > Just to give you a little history as to why I am here. I read that all > e-mail sent across the internet becomes "Public Domain" after 90 days, > meaning anybody and everybody can intercept and read anybodies e-mail. > This disturbs me. So I want to get a firm understanding of encryption > and signing under my belt so I am comfortable with doing it on my > machine and assisting others to do as well. I personally don't like the > fact that someone could be intercepting and reading my personal e-mail > without my knowledge. > > So I am game to prevent that from happening. Just e-mail me back. I will > sign this document, if you would send me your public keys, or give me > the 8 digit key number or tell me what KeyServer you have it on I will > play with the servers. > > I will also attach my key and tell you what the number of my key is on > this e-mail, if you would like to play.... > > Key number is 0x3590E2BC > My public key attached. > > Thanks for any help that you can provide. I appreciate everyones time > and I don't want to abuse your time, either.... > Sincerely, Clois Beckwith > > > > Hi Clois, Let me suggest that you enable PGP/MIME if you are going to sign message to mailing lists. It looks neater and the list members will like it better. This message will only be signed. If you like you can return email me encrypted using the key that I signed this with. And if you like I will send you an encrypted email in return. -- David -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From rjh at sixdemonbag.org Thu Jul 30 22:12:22 2009 From: rjh at sixdemonbag.org (Robert J. Hansen) Date: Fri, 31 Jul 2009 01:12:22 -0400 Subject: [Enigmail] A newbie to encryption, needs a test buddy In-Reply-To: <3f34f8420907302159q784d2b22j85e3ba3f8139fc85@mail.gmail.com> References: <4A725814.6030906@hughes.net> <298CB1AD-55C4-49BA-BC0F-CD280AA25FD5@sixdemonbag.org> <3f34f8420907302159q784d2b22j85e3ba3f8139fc85@mail.gmail.com> Message-ID: > Does this protect data in-transition? I'm not a lawyer. I can point you to 18 USC 1030 and say "read that for yourself and see if you think it covers what you're talking about," but that's as far as my ability to give legal advice goes. Any legal advice you get for free on the internet is dangerous and not worth what you paid for it. From oberon at q.com Thu Jul 30 23:30:19 2009 From: oberon at q.com (Oberon) Date: Fri, 31 Jul 2009 01:30:19 -0500 Subject: [Enigmail] A newbie to encryption, needs a test buddy In-Reply-To: <4A726401.3010701@bellsouth.net> References: <4A725814.6030906@hughes.net> <298CB1AD-55C4-49BA-BC0F-CD280AA25FD5@sixdemonbag.org> <4A726401.3010701@bellsouth.net> Message-ID: On 7/30/2009 10:24 PM, John W. Moore III wrote: > I cannot find fault with Robert's legal citations. I can & will point > out the nebulous phrase 'proper authorization' and ask anyone if they > can succinctly and accurately define just what it constitutes in the age > of the Patriot Act and the routine tasks performed by System Engineers. > While I seriously doubt that anyone's Email is 'thrown open to the > Public' at any time; I am confident that everyone's Email is exposed to > thousands of eyes at any given time. Even Google, with Gmail, > electronically 'scans' the body of Email for 'clues' on which ads to > target toward the recipient. This seems a lot like what we had a few years ago when people became concerned about the lack of security when using cordless phones. The government's response was to pass a law against eavesdropping on such calls, and then more or less said, "There, now you don't have to worry. Cordless phones are now secure." It boggles the mind that anyone with an IQ above room temperature would not see through that move, but it seems to have worked. -- MURPHY'S LAW OF SEX: Never stand between a fire hydrant and a dog. ----------------------------------------------------------- This mail is from The Old Sinner, a.k.a The Beast 333. (Not evil, just a little bit naughty.) This mail is a natural product. Slight variations in grammar and spelling can be expected and in no way diminish the intent of the message. ----------------------------------------------------------- From patrick at mozilla-enigmail.org Fri Jul 31 00:23:03 2009 From: patrick at mozilla-enigmail.org (Patrick Brunschwig) Date: Fri, 31 Jul 2009 09:23:03 +0200 Subject: [Enigmail] Unusable Japanese language. (Was Re: [ANN] Enigmail v0.96.0 available In-Reply-To: <4A707487.70504@bc.iij4u.or.jp> References: <4A6046E1.4070009@mozilla-enigmail.org> <4A65C547.5090200@bc.iij4u.or.jp> <4A707487.70504@bc.iij4u.or.jp> Message-ID: <4A729BD7.6040309@mozilla-enigmail.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 kyshk at bc.iij4u.or.jp wrote: > At Tue Jul 21 2009 22:40:23 GMT+0900 , > kyshk at bc.iij4u.or.jp wrote: >> Hi! >> Enigmail is always dependable. >> >> I tried the Enigmail 0.96.0 but It is unusable Japanese language. It can >> not send ISO-2022-JP encode encrypt message. >> >> bad Thunderbird - Enigmail encode linkage. >> (Enigmail 0.95.7 is OK) >> >> >> ,----[ example ]- send non PGP/MIME ISO-2022-JP encrypt message >> | X-Enigmail-Version: 0.96.0 >> | Content-Type: text/plain; charset=UTF-8 >> | Content-Transfer-Encoding: 8bit >> | Status: U >> | >> | -----BEGIN PGP MESSAGE----- >> | Charset: ISO-2022-JP >> | Version: GnuPG v1.4.8 (MingW32) >> | Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ >> `---- >> >> >> ,----[ not ]- >> | Content-Type: text/plain; charset=UTF-8 >> | Content-Transfer-Encoding: 8bit >> `---- >> >> ,----[ but ]- >> | Content-Type: text/plain; charset=ISO-2022-JP >> | Content-Transfer-Encoding: 7bit >> `---- >> >> use: >> Thunderbird 2.0.0.22 (20090605) >> Enigmail 0.96.0 (20090717-0949) >> settings: >> --rfc2440 >> extensions.enigmail.warnIso2022jp=2 >> >> source message encoding is ISO-2022-JP >> >> 1.non PGP/MIME encrypt :UTF-8 (bad) >> 2.non PGP/MIME signed :ISO-2022-JP (good) >> 3.non PGP/MIME signed+encrypt :UTF-8 (bad) >> 4.PGP/MIME encrypt :UTF-8 (bad) >> 5.PGP/MIME signed :UTF-8 (bad) >> 6.PGP/MIME signed+encrypt :UTF-8 (bad) >> >> message(1,3,4,5,6) maybe can not read other MUA. (mojibake) >> Content-Type header be distinct from contents. >> >> Thunderbird 2.0.0.22 can not accurate encode. >> (wrong Content-Type header) >> Enigmail ignore [extensions.enigmail.warnIso2022jp] param. >> >> and Japanese standard encrypt(or signed) message is NO UTF-8 and NO >> quoted-printable. >> -- >> kiyo > > extensions.enigmail.warnIso2022jp process deleted. > and compulsory change from ISO-2022-JP to UTF-8. > > it's not in Changelog. > Please check the your source code. I have rewritten the sending function of Enigmail for v0.96.0. In older versions of Enigmail, I used to modify the standard Thunderbird sending function to embed the encryption feature, which allowed me to work around character set conversion issues of Thunderbird. In order to have a clean internal interface and be compatible with other extensions, I'm not doing this anymore ; Enigmail now uses the standard Thunderbird message sending function. The only modification I made to it is to backport a change from Thunderbird 3 which allows Enigmail to properly register its hooks in the send mail process. In order to be compliant with OpenPGP, the character set ISO-2022-JP cannot be used since messages in this charset violate the PGP/MIME standard. Given that I don't modify the message sending function anymore, I cannot force Thunderbird to not convert to ISO-2022-JP anymore. - -Patrick -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEVAwUBSnKb1XcOpHodsOiwAQg2xAgAuS6LlS7D1rbILQJCXIMqMyMChDVQWQaU P9i3jrGs1YTUEQlbtxO9gyq/7ws8uyo51gVDnOo80TIx4piSC93wnUCswAgJO/ok V4ZAR97tsZhX23U5xYUyHCOAfn5/Vp7Jca0te8OBjLs0gBMiUV2PfuvnxyFwTKEz 4JIkScS12ImAQvrijTH7GXQVAUHzGe0v2IGSguK2qmxr7N1l7PpQsZ650s6JvnXQ EkB/JR76w3vbrqLEJnB4vwgi+TvjLFPEaBvZ0JC91mZPn/XF42xQ3buQ/KR2lPjo PX83JHaYuBncgHY96C5MrLoidV2XfQRy3CdUYfDHE4Oy5T3RNVNyZA== =vZE+ -----END PGP SIGNATURE----- From rjh at sixdemonbag.org Fri Jul 31 05:53:41 2009 From: rjh at sixdemonbag.org (Robert J. Hansen) Date: Fri, 31 Jul 2009 08:53:41 -0400 Subject: [Enigmail] A newbie to encryption, needs a test buddy In-Reply-To: References: <4A725814.6030906@hughes.net> <298CB1AD-55C4-49BA-BC0F-CD280AA25FD5@sixdemonbag.org> <4A726401.3010701@bellsouth.net> Message-ID: <8AA07DC3-C95E-4553-8753-B8B682F30D77@sixdemonbag.org> > Cordless phones are now secure." It boggles the mind that anyone with > an IQ above room temperature would not see through that move, but it > seems to have worked. Perhaps. This does not change the fact, though: the idea that emails fall into the public domain after 90 days and may be read and shared by anyone is one hundred percent wrong. From ldc at lrcressy.com Fri Jul 31 06:08:00 2009 From: ldc at lrcressy.com (LeRoy) Date: Fri, 31 Jul 2009 09:08:00 -0400 Subject: [Enigmail] A newbie to encryption, needs a test buddy In-Reply-To: <298CB1AD-55C4-49BA-BC0F-CD280AA25FD5@sixdemonbag.org> References: <4A725814.6030906@hughes.net> <298CB1AD-55C4-49BA-BC0F-CD280AA25FD5@sixdemonbag.org> Message-ID: <4A72ECB0.9080009@lrcressy.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Robert J. Hansen wrote: >> A newbie to encryption needs a test buddy or buddies. I need a few >> individuals that can help me get my e-mail signing and encryption from >> baby steps to being able to function as an adult. Any Takers? > > While some people here will probably volunteer, you will have better > luck asking on the PGP-Basics group over at Yahoo! Groups. > > http://tech.groups.yahoo.com/group/PGP-Basics/ > >> Just to give you a little history as to why I am here. I read that all >> e-mail sent across the internet becomes "Public Domain" after 90 days, >> meaning anybody and everybody can intercept and read anybodies e-mail. > > This is not true. It's so far from the truth that, if I were you, I > would be genuinely angry at whoever told me this. In the United States > there's a lot of federal law which makes it a federal offense to > intercept email or to, without proper authorization, access it while > it's in storage at an ISP; most other countries have similar laws. > > For an example of just one applicable U.S. law, see the Stored > Communications Act (18 USC 2701 through to 18 USC 2712). You can read > an overview of it at: > > http://en.wikipedia.org/wiki/Stored_Communications_Act > > Once more, whoever told you this was either grossly ignorant or was > outright lying to you. > > One of the things that you need to acknowledge is that email can hop up to 30 different servers prior to even getting to your mail server. That being said, mail can be sniffed at every one of those hops. I have seen legal notes attached to the bottom of emails stating that this email can contain confidential information etc. This is really stupid for any message that is sent that contains any confidential or secret info should be encrypted with a strong encryption. Thus when the message is read by someone who is not the intended recipient, there is no damage done. As far as key servers are concerned once you post your key on one it will be available on all of them. GnuPG is not only useful for signing and encrypting email, but you can use it to encrypt files on your system. Like I maintain a password file with credit cards, banks and every supplier I deal with. This file is encrypted with a 4096 bit key and a good passphrase. Also if you use a laptop it is useful to encrypt the home, tmp, and swap partitions thus making booting a bear, but if your laptop is stolen your confidential info will not be available to the thieves. I think I have gone on long enough ;-) - -- Rev. LeRoy D. Cressy mailto:leroy at lrcressy.com /\_/\ http://lrcressy.com ( o.o ) Phone: 215-535-4037 > ^ < Cell: 267-307-3527 gpg fingerprint: 62DE 6CAB CEE1 B1B3 359A 81D8 3FEF E6DA 8501 AFEA For info on enigmail: http://lrcressy.com/linux/mozilla.pdf For info on gpg: http://www.gnupg.org/ Jesus saith unto him, I am the way, the truth, and the life: no man cometh unto the Father, but by me. (John 14:6) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iQEVAwUBSnLssKuxGqN1iGbbAQKRKwf/Sl86XjrUOANluNaQ4paUQP5nhFTG/DYD jeLR7jXfBLx7M05xjmmvWtWC1c7fnB4CmdU1ZEFTFM1S+RNuQRIu+KEFhSNLjUts GeCA95ZY5ecV3Hned5XUugbGHcX0WRgNVLcpDG3eBT0/rJklkKByVv1Tqa2MxYe5 euKW+BDGXIaLl8m9W8jwb6P9ZUnKrWLnCL1ksLUlGcX6mDHWQKmDrC7Vz0oxZJAl moM7BLyH5EdyS2COXnXjFk74fH/npP+orIp/vA6uzdT1oxwx//6egbJ6MkF1WDU7 0lvOg/tMJd74GYteDymsRV4+jYErS22YVaRvte/1HWEgvDNiVNqjSA== =yeUJ -----END PGP SIGNATURE----- From alaric at metrocast.net Fri Jul 31 07:46:45 2009 From: alaric at metrocast.net (Phil Stracchino) Date: Fri, 31 Jul 2009 10:46:45 -0400 Subject: [Enigmail] Unusable Japanese language. (Was Re: [ANN] Enigmail v0.96.0 available In-Reply-To: <4A729BD7.6040309@mozilla-enigmail.org> References: <4A6046E1.4070009@mozilla-enigmail.org> <4A65C547.5090200@bc.iij4u.or.jp> <4A707487.70504@bc.iij4u.or.jp> <4A729BD7.6040309@mozilla-enigmail.org> Message-ID: <4A7303D5.9080400@metrocast.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Patrick Brunschwig wrote: > In order to be compliant with OpenPGP, the character set ISO-2022-JP > cannot be used since messages in this charset violate the PGP/MIME > standard. OK, now I'm curious. Why does ISO-2022-CP charset violate the PGP/MIME standard? Is there a technical reason, was it arbitrarily excluded as a permissible charset, or was it just never written in? - -- Phil Stracchino, CDK#2 DoD#299792458 ICBM: 43.5607, -71.355 alaric at caerllewys.net alaric at metrocast.net phil at co.ordinate.org Renaissance Man, Unix ronin, Perl hacker, Free Stater It's not the years, it's the mileage. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEAREIAAYFAkpzA9UACgkQ0DfOju+hMkkzNQCguLkAw0jfmaB2wn1NhEM2JlwT pMUAoKfemomLdUGJpum3fTZomn42t1c3 =q5MN -----END PGP SIGNATURE----- From federalhillrent at yahoo.com Fri Jul 31 11:06:30 2009 From: federalhillrent at yahoo.com (FederalHill) Date: Fri, 31 Jul 2009 11:06:30 -0700 (PDT) Subject: [Enigmail] A newbie to encryption, needs a test buddy In-Reply-To: <8AA07DC3-C95E-4553-8753-B8B682F30D77@sixdemonbag.org> Message-ID: <872519.64942.qm@web36308.mail.mud.yahoo.com> It is my understanding that email records are retained by the email provider for two years at the request by the govt. --- On Fri, 7/31/09, Robert J. Hansen wrote: > From: Robert J. Hansen > Subject: Re: [Enigmail] A newbie to encryption, needs a test buddy > To: oberon at q.com, "Enigmail user discussion list" > Date: Friday, July 31, 2009, 8:53 AM > > Cordless phones are now > secure."? It boggles the mind that anyone with > > an IQ above room temperature would not see through > that move, but it > > seems to have worked. > > Perhaps.? This does not change the fact, though: the > idea that emails fall into the public domain after 90 days > and may be read and shared by anyone is one hundred percent > wrong. > > _______________________________________________ > Enigmail mailing list > Enigmail at mozdev.org > https://www.mozdev.org/mailman/listinfo/enigmail > From rjh at sixdemonbag.org Fri Jul 31 11:36:02 2009 From: rjh at sixdemonbag.org (Robert J. Hansen) Date: Fri, 31 Jul 2009 14:36:02 -0400 Subject: [Enigmail] A newbie to encryption, needs a test buddy In-Reply-To: <872519.64942.qm@web36308.mail.mud.yahoo.com> References: <872519.64942.qm@web36308.mail.mud.yahoo.com> Message-ID: <891402C6-00FA-4D31-9582-FB3EEC6633D1@sixdemonbag.org> > It is my understanding that email records are retained by the email > provider for two years at the request by the govt. Without substantiation, this deserves no more credit than any other rumor floating around the internet. To substantiate it, two questions need to be answered: * Which government does this? * Which law allows them to do this? Facts are always welcome on this list, but the world has enough rumor in it without us adding to the problem. From adam at e-ignite.co.uk Fri Jul 31 14:09:21 2009 From: adam at e-ignite.co.uk (Adam Gould) Date: Fri, 31 Jul 2009 22:09:21 +0100 Subject: [Enigmail] A newbie to encryption, needs a test buddy In-Reply-To: <891402C6-00FA-4D31-9582-FB3EEC6633D1@sixdemonbag.org> References: <872519.64942.qm@web36308.mail.mud.yahoo.com> <891402C6-00FA-4D31-9582-FB3EEC6633D1@sixdemonbag.org> Message-ID: On Fri, Jul 31, 2009 at 7:36 PM, Robert J. Hansen wrote: >> >> It is my understanding that email records are retained by the email provider for two years at the request by the govt. > > Without substantiation, this deserves no more credit than any other rumor floating around the internet. ?To substantiate it, two questions need to be answered: > > * Which government does this? > * Which law allows them to do this? > > Facts are always welcome on this list, but the world has enough rumour in it without us adding to the problem. Unfortunately, this is more than just rumour. The UK government have a number of powers under the Regulatory Investigatory Powers Act 2000 (RIPA) and the Interception Modernisation Programme (IMP) whereby certain details from virtually all communications including email and telephone calls are recorded and stored by the ISP (Internet Service Provider - sorry, don't mean to patronise, but wanted to be clear what I meant in an acronym-laden email!) which can then be reviewed by the government or law enforcement agencies and even by local council authorities under certain circumstances following a valid request. With regards to the monitoring of email communications, the actual content of the mail is not stored, but details including (but not limited to) the originator's email address, the recipient's email address, the date, time, and originating IP address are all monitored and logged. These records are stored for up to two years and the justification given by the UK government for this wide-scale invasion of privacy is the prevention of serious crime and terrorism. There are many articles covering both RIPA and IMP available on the web: The full text of the RIPA is available at http://www.opsi.gov.uk/acts/acts2000/ukpga_20000023_en_1 but this is fairly technical. A few more "reader-friendly" articles from various other tech-related websites are linked below for anyone who would like to read more. http://news.bbc.co.uk/1/hi/uk/7819230.stm http://www.theregister.co.uk/2009/04/27/imp_consultation/ http://www.theregister.co.uk/2009/06/19/imp_ispa/ http://news.zdnet.co.uk/hardware/0,1000000091,2118813,00.htm http://www.openrightsgroup.org/orgwiki/index.php/Intercept_Modernisation I hope this helps set out the facts versus the rumours. Adam -- Communicate Securely: e-ignite.co.uk From rjh at sixdemonbag.org Fri Jul 31 14:20:21 2009 From: rjh at sixdemonbag.org (Robert J. Hansen) Date: Fri, 31 Jul 2009 17:20:21 -0400 Subject: [Enigmail] A newbie to encryption, needs a test buddy In-Reply-To: References: <872519.64942.qm@web36308.mail.mud.yahoo.com> <891402C6-00FA-4D31-9582-FB3EEC6633D1@sixdemonbag.org> Message-ID: <1E404185-3A01-4F30-9BFC-6566BEFF38FE@sixdemonbag.org> > Unfortunately, this is more than just rumour. For some governments and some laws, yes; however, _without qualification_, statements such as this contribute nothing to the discussion except to give an unreasoning and uninformed sense of fear. With the qualification (and substantiation) of "we're talking about the United Kingdom and RIPA," then yes, we're now entering the realm of fact. From dkg at fifthhorseman.net Fri Jul 31 15:02:22 2009 From: dkg at fifthhorseman.net (Daniel Kahn Gillmor) Date: Fri, 31 Jul 2009 18:02:22 -0400 Subject: [Enigmail] A newbie to encryption, needs a test buddy In-Reply-To: <1E404185-3A01-4F30-9BFC-6566BEFF38FE@sixdemonbag.org> References: <872519.64942.qm@web36308.mail.mud.yahoo.com> <891402C6-00FA-4D31-9582-FB3EEC6633D1@sixdemonbag.org> <1E404185-3A01-4F30-9BFC-6566BEFF38FE@sixdemonbag.org> Message-ID: <4A7369EE.4070704@fifthhorseman.net> On 07/31/2009 05:20 PM, Robert J. Hansen wrote: > For some governments and some laws, yes; however, _without > qualification_, statements such as this contribute nothing to the > discussion except to give an unreasoning and uninformed sense of fear. > > With the qualification (and substantiation) of "we're talking about the > United Kingdom and RIPA," then yes, we're now entering the realm of fact. Given that most users sending mail to arbitrary others don't actually know whether that particular mail is being routed through the UK or not, i believe there's still a rather large "uninformed" fear out there, and rightly so. Demonstrating that any particular communications channel does *not* pass through the worst-case legal jurisdiction can be a fairly costly (if not impossible) operation. That there exists a worst-case legal jurisdiction is sadly not particularly surprising. --dkg -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 890 bytes Desc: OpenPGP digital signature URL: From jmoore3rd at bellsouth.net Fri Jul 31 16:49:10 2009 From: jmoore3rd at bellsouth.net (John W. Moore III) Date: Fri, 31 Jul 2009 19:49:10 -0400 Subject: [Enigmail] A newbie to encryption, needs a test buddy In-Reply-To: <4A7369EE.4070704@fifthhorseman.net> References: <872519.64942.qm@web36308.mail.mud.yahoo.com> <891402C6-00FA-4D31-9582-FB3EEC6633D1@sixdemonbag.org> <1E404185-3A01-4F30-9BFC-6566BEFF38FE@sixdemonbag.org> <4A7369EE.4070704@fifthhorseman.net> Message-ID: <4A7382F6.3030700@bellsouth.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Daniel Kahn Gillmor wrote: > Demonstrating that any particular communications channel does *not* pass > through the worst-case legal jurisdiction can be a fairly costly (if not > impossible) operation. > > That there exists a worst-case legal jurisdiction is sadly not > particularly surprising. Last Report I read stated that 95% of _all_ Email sent passed over a U.S. circuit at some point in its journey. The greatest protection against NSA at this time is the physical lack of ability to analyze this much data. NSA is literally drowning in new data and cannot build storage facilities fast enough. Once the UK/USA Agreement is considered the actual number of Emails passing through analytical checkpoints rises to 99% with only completely closed systems being immune. JOHN ;) Timestamp: Friday 31 Jul 2009, 19:48 --400 (Eastern Daylight Time) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10-svn5099: (MingW32) Comment: Public Key at: http://tinyurl.com/8cpho Comment: Gossamer Spider Web of Trust: http://www.gswot.org Comment: Personal Web Page: http://tinyurl.com/yzhbhx iQEcBAEBCgAGBQJKc4LxAAoJEBCGy9eAtCsPRJ4H/RHTorc4THCfFfSLW2WcWW8Y 30JCrTa1gqSEZvvPjWIjZJelqYvm3PwQBBj0TUW7CcZQsIKn9b6iJMfuufxUmSQ/ 2WAfz5xepUJ/hI/BIXXbqfU9IOTgWsWyjRJIorWCuYjPrjWj3K6Hn4t/DnMEDilB VG8A1rJ1kFIbISHUIUs3NxdK4g0ubBPSmQjbUYgvM60W688vlZZ7TXMHbdiHSXj9 CvXgtOGmS119JlTgfDyJCTrApg8M0mXat/URKhaHQ7qr3snM79UC41r8+pKVAu4l COg8C9XymrkWyWWiRsxi+XP99rwMdTNytjGD7M3CM4fXch/8g+o1IDXRXRH4pOg= =a34o -----END PGP SIGNATURE-----