- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Jan 29 2021
There is a question for me here if we should make the behavior of rKLEOPATRA5639dc833f92 the default.
See also https://gitlab.com/openpgp-wg/webkey-directory/-/issues/3 which is the same issue.
I linked all related tasks for the release of 1.9.1, so that making release notes can be easier and recording information here.
Jan 28 2021
Patch lets it build on xenial for me, thank you.
Patch for this bug is available here, "attachment-0001.bin": https://lists.gnupg.org/pipermail/gcrypt-devel/2021-January/005079.html
I committed the partial result docker container, so I can restart it for investigation. So:
The groups are read from kleopatragroupsrc (located in the default location(s) for configuration files, e.g. next to kleopatrarc). The format is
[Group-<group id>] Name=<group name> Keys=<fingerprint>,<fingerprint>,...
where group id is a unique identifier for the group (can be identical to group name), group name is the (display) name of the group (which should also be unique for practical reasons), fingerprint is the fingerprint of a key in the group. Everything has to be UTF-8-encoded.
The last server of the HKPS pool dropped off for several hours yesterday, during which hkps.pool.sks-keyservers.net could not be resolved.
I tested xenial with gcc-5.3 (xenial distro repo) and gcc-5.4 (xenial-updates distro repo) and libgcrypt 1.9.0 from git repo and from tarball. I did not get any errors.
Jan 27 2021
In the next few days I'll be able to boot into Leopard, Mac OS X 10.5.8, to test this. Right now it seems that I need to fix a few problems with updated software sources…