Re: [Enigmail] new nightly built with several updates
Am 16.06.2014 09:20, Kosuke Kaizuka schrieb/wrote: >> I just fixed it and pushed it so that it should be in the next >> master (in Monday or Tuesday). > > Thanks, I understood. > > https://sourceforge.net/p/enigmail/source/ci/7421a268856dac582c38e7e83d0318c9ca08c35c/ > No need to backout the changes for signYes and signNo? > Oh yes, of course. Changed SignYes and SignNo back. Pushed into master. Thanks a lot Nico -- Nicolai M. Josuttis www.josuttis.de mailto:n...@enigmail.net ___ enigmail-users mailing list enigmail-users@enigmail.net To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
Re: [Enigmail] new nightly built with several updates
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 >> 2. What does %S in signYes and signNo in enigmail.properties >> stand for? Only "Message will be signed" or "Message will not be >> signed" is shown in compose window OpenPGP menu. >> >> signYes=Message will be signed %S signNo=Message will not be >> signed %S >> > Oops, I just saw that this is an old label I changed, which I > should not do. I should have introduced a new label instead. The > new label will probably be: signYesWithOptionalDetails > signNoWithOptionalDetails and the meaning of the %S is to > optionally place some details about why the message is (not) > signed. The only supported detail for that is so far: > signDueToEncryptionMode=(due to encryption mode) So that a > resulting message might be: Message will be signed (due to > encryption mode) There might be more details come sooner or later > (to better explain resulting signing/encryption). > > I just fixed it and mushed it so that it should be in the next > master (ion Monday or Tuesday). Thanks, I understood. https://sourceforge.net/p/enigmail/source/ci/7421a268856dac582c38e7e83d0318c9ca08c35c/ No need to backout the changes for signYes and signNo? - -- Kosuke Kaizuka Hi Nicolai, On Sun, 15 Jun 2014 23:02:49 +0200, Nicolai Josuttis (enigmail) wrote: -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (MingW32) iQIcBAEBCgAGBQJTnprPAAoJEFI91dNOjkjZmnAP/3ef2w4zcZDzAu34we7+i4mM xGO+N5t79SN24uzx+jfagCT5BcPl8CL0/TAe79HDFfNmsEfkskqGHGE7hU7i6DdB QmdDUp8KQ4uc/qoFHwt0OoEuCv6YaG9KZCMIFEsSeW66h/ppAh6QKkjbob4EFHfF BI+kPYaFt3fwioacT4Ed7rJhY/Eg8qhIOvLnI9XX/RhHu/SVTVuERnE8JlndGW0G /+Z3eMEe/enyUKF5XZOJkqRI2E+Rqi6llx/w3+hm1y4ERm5j2MFVdyKjLBhIX9gI qBJTcC7D0Q6DISVZkCBzxTReKQqGaHFk9hH3hr3sfQTFhL0lZx6MJv+WMPYUYE3h C6ebyZ9NY2tIC3kPl1K2cvZGXvt3KDhZNOTNhrNKi5ul5Xvl20DGq8ZRTDg6yjzN mFwnyGCfATeQQrErGbWp+u62JnBBNS/N6Hfbt6RS5YKZBg87FhfHVz82PGqDdwod BaUfFq2XxZ28R338ZmPSjwYRN+Ky91Y8XhVx5/8u9xIOQdNJKxWkzEgL7MnMA0ka XbPCuIIJChwU9xp1QkeszmzCiTaMWz7h+zuYz8Vo01uAS4EoNdh883meZdQhhtmD wbm1cHJHk9FKUt0AdPF7iq8sml07x20r7iehlhBMuSJO2rcV9hVJQIDKzvND2SuG sgeGhC4de9zefNu8eXNZ =lMML -END PGP SIGNATURE- ___ enigmail-users mailing list enigmail-users@enigmail.net To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
Re: [Enigmail] new nightly built with several updates
Hi Kosuke Kaizuka, thanks for the quick feedback. Am 15.06.2014 18:40, Kosuke Kaizuka schrieb/wrote: > Hi Nicolai, > > > Hi Nicolai, > > I have tried Enigmail nightly 2014-06-15 with Thunderbird 31.0b1 on > Win7, and new features seem to work fine. > > During preparation of ja-JP localization on my local, I got several > questions about locale files. > > 1. enigmail.defaultSignPlainMsg.label is duplicated in enigmail.dtd > line 220 and 228. Also, this entity seems not to be used at all. > I didn't check which labels are no longer needed yet. > > 2. What does %S in signYes and signNo in enigmail.properties stand > for? Only "Message will be signed" or "Message will not be signed" is > shown in compose window OpenPGP menu. > > signYes=Message will be signed %S > signNo=Message will not be signed %S > Oops, I just saw that this is an old label I changed, which I should not do. I should have introduced a new label instead. The new label will probably be: signYesWithOptionalDetails signNoWithOptionalDetails and the meaning of the %S is to optionally place some details about why the message is (not) signed. The only supported detail for that is so far: signDueToEncryptionMode=(due to encryption mode) So that a resulting message might be: Message will be signed (due to encryption mode) There might be more details come sooner or later (to better explain resulting signing/encryption). I just fixed it and mushed it so that it should be in the next master (ion Monday or Tuesday). Best Nico > > ___ > enigmail-users mailing list > enigmail-users@enigmail.net > To unsubscribe or make changes to your subscription click here: > https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net > > -- Nicolai M. Josuttis www.josuttis.de mailto:n...@enigmail.net ___ enigmail-users mailing list enigmail-users@enigmail.net To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
Re: [Enigmail] new nightly built with several updates
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi Nicolai, I have tried Enigmail nightly 2014-06-15 with Thunderbird 31.0b1 on Win7, and new features seem to work fine. During preparation of ja-JP localization on my local, I got several questions about locale files. 1. enigmail.defaultSignPlainMsg.label is duplicated in enigmail.dtd line 220 and 228. Also, this entity seems not to be used at all. 2. What does %S in signYes and signNo in enigmail.properties stand for? Only "Message will be signed" or "Message will not be signed" is shown in compose window OpenPGP menu. signYes=Message will be signed %S signNo=Message will not be signed %S - -- Kosuke Kaizuka -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (MingW32) iQIcBAEBCgAGBQJTncxnAAoJEFI91dNOjkjZU1IQAMCFkkgKNFAao6aDf5luyEhh XCqx7J/Jdql1TiyQkUo9ScybqGjrjmIJCuBwGmwJraGl5GRs2XDe4cwHSh2mc9hk cynQEpoU9R+8qiA+W3NKMzVYN/NjOKsk7A592D2Zndcn7lzRbn9ANvpHVejbyIcA 6PXZatdtgwzHAIH6GDqRiLNnFNt/aBy4GAVLUIRHnMP5szlAEk9OCpNjiK78s0rK lKtR9gcbNGszdz6Pbd7iMmU9uc/vVEFu0G7BC3wv5ua9w4wmbYRYZXt9FbemqnLv nu9d73s8SuzJP96W7Ev+qpMtCpQRsT1xMY9kAwyCP5/vYt6NLnObPstnwNXteuY0 N8GIEO5OTNYP1sYenk304aPhtM2ZUQ7OHjx2FlgWnjbPwv6u0Chzy5+S8TvyO59S 3+Xbs8M34kMgWqKb+as61H7njs6JgMNpsBxEdz2vfRvxHTr7aeBf66+rf/KZdvXf sNrCJ/J+m10qB0gxYlSdz2dgjcH3KbviTvlslJYE/CO1UyzMztUyIySDsrK7T6qr XzMsafVWcQj+ICdYTlWyiv/rDzBvHL50vGwldPFpooYSFw81ytGKdFWvT3yRfSf4 q0Yrht9lWN7aTQn9MuE9wcRzPhg+M85TkJNbUQ/xE10TeX6Sj9Z4LVyxdBx62yk1 o9uIJGfG/aOwbUF5PT4j =Hyk7 -END PGP SIGNATURE- ___ enigmail-users mailing list enigmail-users@enigmail.net To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
Re: [Enigmail] new nightly built with several updates
Thanks Philip, That's exactly the kind of feedback I wanted to have to fix final flaws. Please allow me to look at details later (currently traveling) and may be I ask for details then personally. Best Nico Am 15.06.2014 14:06, Philip Jackson schrieb/wrote: > Hi Nico, > > Looks good at first glance. Time will tell how it performs. > > > On 15/06/14 09:49, Nicolai Josuttis (enigmail) wrote: > >> - In the account specific menu you can now select the >> general defaults for signing/encryption/pgpmime >> - The decision to automatically sign when the >> email is (not) encrypted now is processed FINALLY >> after applying all defaults/rules/manual-settings >> It therefore has new labels. > > I find this explanation a little difficult to understand but what I take from > what you have written is the following : > > In the account specific settings of Thunderbird, in the OpenPGP Options, if I > select (tick) the check box 'Automatically sign finally non-encrypted > messages' > this action will be applied as an final (ultimate) action after all other > defaults/rules/manual settings have been applied. > > So if all other actions work to declare that a particular email should not be > signed, then this option will ensure that it is signed anyway. > > But an initial test proves that it doesn't work that way. If in the write > window, I select OpenPGP/Message will be signed/Force not to sign : then the > message is sent unsigned. > > So it seems that I have misunderstood your quoted text above. Perhaps it is > the > use of the word 'finally' that is ambiguous ? > > Perhaps we could suggest something more clear if you say what message you > intended to convey. > > Best regards, > Philip > > ps. for this message, it should be signed by default. My initial attempt at > clicking the send button produced an error "Bad pass phrase" "send failed". > > I wasn't even invited to enter a passphrase. So I have disabled signing to > get > this message away. I don't yet understand if this is an effect of the latest > nightly build. > > > > ___ > enigmail-users mailing list > enigmail-users@enigmail.net > To unsubscribe or make changes to your subscription click here: > https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net > -- Nicolai M. Josuttis www.josuttis.de mailto:n...@enigmail.net ___ enigmail-users mailing list enigmail-users@enigmail.net To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
Re: [Enigmail] new nightly built with several updates
Hi Nico, Looks good at first glance. Time will tell how it performs. On 15/06/14 09:49, Nicolai Josuttis (enigmail) wrote: > - In the account specific menu you can now select the > general defaults for signing/encryption/pgpmime > - The decision to automatically sign when the > email is (not) encrypted now is processed FINALLY > after applying all defaults/rules/manual-settings > It therefore has new labels. I find this explanation a little difficult to understand but what I take from what you have written is the following : In the account specific settings of Thunderbird, in the OpenPGP Options, if I select (tick) the check box 'Automatically sign finally non-encrypted messages' this action will be applied as an final (ultimate) action after all other defaults/rules/manual settings have been applied. So if all other actions work to declare that a particular email should not be signed, then this option will ensure that it is signed anyway. But an initial test proves that it doesn't work that way. If in the write window, I select OpenPGP/Message will be signed/Force not to sign : then the message is sent unsigned. So it seems that I have misunderstood your quoted text above. Perhaps it is the use of the word 'finally' that is ambiguous ? Perhaps we could suggest something more clear if you say what message you intended to convey. Best regards, Philip ps. for this message, it should be signed by default. My initial attempt at clicking the send button produced an error "Bad pass phrase" "send failed". I wasn't even invited to enter a passphrase. So I have disabled signing to get this message away. I don't yet understand if this is an effect of the latest nightly build. 0x23543A63.asc Description: application/pgp-keys ___ enigmail-users mailing list enigmail-users@enigmail.net To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
[Enigmail] new nightly built with several updates
Hi all, last night a new nightly build version of enigmail was built, which contains several changes and fixes. You can find it at: https://www.enigmail.net/download/nightly.php To try it out: - DOWNLOAD the file enigmail-nightly-all.xpi https://www.enigmail.net/download/nightly/enigmail-nightly-all.xpi INTO A LOCAL FILE (don't load it directly into your firefox browser) - In Thunderbird choose Extras -> Add-Ons-Manager select the configure icon on the top right -> install Add-On from file and select the stored file - press install now - restart thunderbird The changes are: - New handling of default/rules/final-decisions for encryption/signing/pgp-mime - new account-defaults - new key selection properties - new compose menu entries (both pulldown and popup menues) - new status bar button icon look&feel See a summary of the new behavior below - We have a workaround now to try to handle PGP/Mime emails screwed up by a Exchange Server <=2010. see https://sourceforge.net/p/enigmail/forum/support/thread/4add2b69/ To summarize how encryption/signing/pgpmime is handled now: - In the account specific menu you can now select the general defaults for signing/encryption/pgpmime - The decision to automatically sign when the email is (not) encrypted now is processed FINALLY after applying all defaults/rules/manual-settings It therefore has new labels. - Note: If no automatic signing is selected, signing is not bundled to encryption - You now have a button there to jump to the global settings - In the preferences -> key selection you can now simply turn on or off the possible steps of the key handling individually. This replaces a radio boy where you could only choose one of a couple of options, where the consequence were not always clear. The recommended default settings are: - use recipient-rules - use keys from key manager - start manual key selection if keys are missing - With the status bar icons you can now FINALLY choose to sign/encrypt or not to sign/encrypt (which means after hitting these buttons, rules/defaults no longer count to decide whether to sign/encrypt, even if additional recipients are added while composing) - With the compose menu entries you can do the same PLUS - see the current status of the email - switch back to process defaults and rules I am happy about any feedback. -- Nicolai M. Josuttis www.josuttis.de mailto:n...@enigmail.net ___ enigmail-users mailing list enigmail-users@enigmail.net To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net
