The behaviour might have changed a bit because of the ldap: prefix i use now, or i have missed this case the last time:
Given some cert on the "download" server, I can find it, if dirmngr.conf contains only the "download" server, or if the "download" server is listed first:
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Today
Independent of keyserver order in dirmngr.conf, --search-keys still offers keys from the upload server, but the download fails:
For "Although the upload server is used for upload, the gpg message still displays the first keyserver" see T8025
in Gpg4win-5.0.0-beta479
I think we won't fix that for 2.2
Tested with gpg4win-5.0.0-beta479 @ win11
@tfry tested this, and it seems fine.
Yesterday
Wed, Jan 7
completed: draft all gpg key function names
I decided to prioritize developer experience and provide simplified, high-level functional abstractions instead of maintaining 1:1 parity with the underlying gpgme library functions. See example in T8021
Traditionally we have considered expired and revoked more or less similar. The idea is that an expired key might have been compromised but the owner did not found a way to revoke it. We may want to change this policy because some users don't care too much about expired keys (cf. T7990) .
I may have misinterpreted what The GnuPG UI Server Protocol is. Instead, I will provide high-level functions to all of gpgme's underlying features
Tue, Jan 6
Frankly, he OpenSSH support for Windows was experimental and I have never tested it. If it can be confirmed that this really works and is useful, it will be easy to add the opeion to gpgconf.
Regarding my comment T1825#191055 : The mane page has long been updated and gpgme support is also available. For the symmetric session key, see the feature request T8016
Looks good to me on gpg4win-5.0.0-beta479 @ win11:
- gpg --show-only-session-key --decrypt FILE shows only the session key
- gpg --add-recipients -r UID1 FILE adds recipients (tested with one or more uids)
- gpg --change-recipients -r UID FILE changes the recipients (tested with one or more uids)
Frankly, he OpenSSH support for Windows was experimental and I have never tested it. If it can be confirmed that this really works and is useful, it will be easy to add the opeion to gpgconf. Note that the gpgconf option feature handles only a subset of all options on purpose.
Mon, Jan 5
The problem was the keyserver configuration, which does not include a scheme (ldap:):
keyserver ldap.gnupg.test:389:uid=LordPrivySeal,ou=GnuPG Users,dc=gnupg,dc=test:pass:dc=gnupg,dc=test:
Sun, Jan 4
Published to NPM as gpgmejs, which provides disambiguation from gpgme, gpgmepp, gpgmepy, etc.
completed working test and repo:
https://github.com/anthumchris/gpgmejs/
Fri, Jan 2
Thu, Jan 1
Completed working base repository with developer workflows for watching files and rebuilding/retesting:
https://github.com/anthumchris/node-addon
Wed, Dec 31
- --experimental-addon-modules stability for javascript ESM import syntax
Tue, Dec 30
Sun, Dec 28
Tue, Dec 23
Thank you!
Thu, Dec 18
Well, I tested this again. I created a new key and saved a copy. The I updated the expiration date to 2035 and sent the key to the LDAP server. Then I deleted the updated key locally and imported the old copy. Thus I have now:
Wed, Dec 17
The aim of this ticket is to map the message in Kleo for the corresponding gpg case to the "Not found" error in gpgsm and thus show the other message instead.
Tue, Dec 16
In T7774#209645, @ebo wrote:isn't this done?
Thanks, I'll start here and see how it was done with JS for the browser: https://dev.gnupg.org/source/gpgme/browse/master/lang/js/
Mon, Dec 15
Note that we have moved almost all bindings out of gpgme into separate repos. I suggest to develop such bindings externally. And you'll have to find external resources to learn how to create nodejs bindings for gpgme.
Yes, this is obsolete with T7717: Location of qt-application config files. Closing as Wontfix because we use product-specific folders outside of GNUPGHOME.
Sun, Dec 14
Sat, Dec 13
Fri, Dec 12
isn't this done?
Resolved without further testing