Today
With the next gpg release (2.5.14) the keyboxd has an extended fingerprint table which carries a flags column. A bit in this column can eventually be used to mark subkeys with the "R" key flag and the search funtion can be enhanced to ignore keys with that flag set. This way we can more easily lookup the actual ADSK key (with the "E" key flag) and check whether this subkey has been revoked.
Yesterday
these articles on the graph API might be useful:
This is fixed.
At line 133 shouldn't we have used iobuf_cancel there?
I believe this bug was fixed by T7829. Please confirm with new gpgwin-5.0.0-beta.
Mon, Nov 17
The error dialog now has a button to show the audit log (named Diagnostics).
The error dialog now has a button to show the audit log (named Diagnostics).
works with Gpg4win-5.0.0-beta395, too
as far as i can tell (and remember), I haven't implemented Ingo's suggestions. I'm putting the ticket back in the backlog and on my TODO list
g++-15 `pkg-config --cflags --libs gpgmepp` -o foo -O2 -Wall --std=c++23
@ikloecker says that Kleo already support this feature. (I didn't know that.)
So, compatibility flag to switch on/off the feature would be needed,
or this feature is not needed in GnuPG at all.
Please show the command line of the linker.
The revision was actually applied (rG0947a20c28cf: gpgsm: Fix output of card serial number in colon listing.), but Phabricator doesn't allow me to set it as applied because not all reviewers have approved it.
At line 133 shouldn't we have used iobuf_cancel there? Would it be possible to call finish_temp_output from iobuf_close or iobuf_cancel instead?
Here is my attempt to do that:
Sun, Nov 16
Fix applied. Thanks.
This is not a composite key specific thing despite that this is an extra challenge. The creation date is used to reconstruct a key if the public key has been lost and only the fingerprint is still available. A solution might be to test the all combinations of stored creation dates to match the fingerprint.
Panel Used By
| Dashboard | Prajeen's Dashboard |