-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hello,
thanks for this feedback.
As a programmer I fully agree.
We (programmers and translators) have the same goal here,
because the current mess is a problem for programming and
maintenance of the code.
We didn't though have enough time to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 03.07.14 07:48, Kosuke Kaizuka wrote:
You mean to change to pool.sks-keyservers.net, keys.gnupg.net,
pgp.mit.edu? Good choice.
These were the keyservers which did work when testing this change in
january.
I'm also considering that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 01.07.14 21:51, Daniel Kahn Gillmor wrote:
On 06/30/2014 12:01 PM, Patrick Brunschwig wrote:
On 30.06.14 12:49, Kosuke Kaizuka wrote:
- enigmail.keyservers.sample does not include
pool.sks-keyservers.net
Yes, we removed it.
why? the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 30.06.14 18:39, Kosuke Kaizuka wrote:
-- enigmail.seeAccountSettings.label says (see Account
Settings - OpenPGP Security)
2. help/messenger.html
- line 31 and 33 do not follow re-labeling OpenPGP to Enigmail
- line 46 Enigmail -gt;
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi Patrick,
I have found several problems of locale files.
1. enigmail.dtd
- - enigmail.keyservers.sample does not include pool.sks-keyservers.net
- - enigmail.amPrefTitle.label OpenPGP Options should be OpenPGP
Security
- -- The title in the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 30.06.14 12:49, Kosuke Kaizuka wrote:
Hi Patrick,
I have found several problems of locale files.
1. enigmail.dtd
- enigmail.keyservers.sample does not include
pool.sks-keyservers.net
Yes, we removed it.
-
