Fri, Sep 17
The changes do not seem to touch anything I've mentoned in (1)?
Tue, Sep 14
Mon, Sep 13
Yes, --no-keyring should enough for the subset of gpg commands which do not need keys.
Sun, Sep 12
Wed, Sep 8
Fri, Sep 3
I think the behavior makes perfect sense for Unix but the default delimiter for .txt in Windows is \r\n.
The OP wants to do symmetric encryption. This isn't about the passphrase that protects a key.
Yes, we read up to the first LF. This has been the traditional way of PGP2 and is still used by mail programs like Mutt.
Thu, Sep 2
I'm guessing gpg in Unix has stripped the \n if present? I don't have access to a real Unix system at the moment.
I see that problem but gpg has traditionally not interpreted the passphrase in any way. Right, for Windows we could strip the CR but I fear that this might break other users scripts/passphrases. However there should be a warning in the manual.
Aug 26 2021
I have rather created D536 as IMO the timeout should be changed, not the documentation.
Aug 25 2021
Aug 13 2021
May 27 2021
Apr 4 2021
Mar 14 2021
Mar 9 2021
Actually we considerto remove this feature from the GUI because with the global config we have a more versatile feature now.
Feb 10 2021
Won't be done because the expectations of users are different on whether they use ssh-agent or gpg-agent. And it breaks scripts
Feb 9 2021
Done. FWIW. in 2.3 symcryptrun will be removed entirely.
Jan 29 2021
See also https://gitlab.com/openpgp-wg/webkey-directory/-/issues/3 which is the same issue.
Jan 26 2021
Sorry, we won't apply such changes. A couple of years we did this and all we earned were a few extra bugs aqnd useless diffs. Further many of those changes are in files which will be updated from upstream time to time and your chnages would be lost.
OK, I only edited documents and notes, no code changes.
Thanks. However, we need to go over the list one by one to decide this. For example
"http://gnupg.org/.well-known/openpgpkey/hu/12345678" is actually expected to return a 404 and test code may very well use http:
Jan 19 2021
Jan 15 2021
This ambiguity appears to be the cause of a recent epic (and to me, largely incomprehensible) thread on gnupg-users. It would be great to have the WKD guidance about fallback strategy be much more explicit. Any room for ambiguity here leads to different outcomes from different WKD clients, and quite a bit of confused discussion by their users.
Dec 23 2020
May I ask that how to get a new complete clean po file.
I'm not familiar with gettext.
The old one is confusing, and I think maybe I should completely clean the messy.
Really a big project.
Frankly, I more or less forgot about these help files. The German version for sure needs an update as weel.
Please and thanks, I imitated the English edition format :-)
- Remove a comment for use case of the file
- If needed, we could have support of another locale(s) with Chinese language: zh_HK, zh_SG, etc.
- It is not us, but it's users who decide which locale is better for them
- E.g., my friend in Düsseldorf uses ja_JP locale
- So, it's technically better not to address restriction in a translation
for that, I think you best keep that.
Use a locale to distinguish Chinese users always cause problems.
There isn't a big difference between the written language. And small region always lack translations.
Singapore's users who use simplified Chinese always use zh_CN if there is no a specific zh_SG.
And the traditional Chinese users from HK SAR and MC SAR sometimes use the translation for Taiwan Province.
So when translate it, the tip remiand you must consider all the users from anywhere.
Please note that many error messages are defined in: https://dev.gnupg.org/source/libgpg-error/browse/master/po/zh_CN.po
For D515, I will also apply it to master.
Applied D514 to master, with an editorial change (removing extra space before newline).
Dec 21 2020
also update doc/help.zh_TW.txt by the way
D515: update gnupg doc/help.zh_TW.txt
upload the v2 patch and create a revision
D514: update gnupg doc/help.zh_CN.txt
waiting for review
Please not that you can use this interface: https://dev.gnupg.org/differential/
I think that it is better when you update your patch. You can just refer a patch from this task by:
If translated, 'keygrip' should be different word to 'fingerprint', because 'fingerprint' is used as a technical term of OpenPGP.