Thanks, that explains it.
And the faketime gpgsm command worked (after installing faketime).
But that's a hack, and users should not have to do this. Especially
since GnuPG 2.1 defauls to keybox and more people recommend it with of
the recent flooding issues.
I opened an issue to track this:
On Wed, 17 Jul 2019 23:41, i...@zeromail.org said:
> But the keybox file didn't get any smaller:
Good catch. In gpg we have not implenteted the compression run:
/* FIXME: Do a compress run if needed and no other
user is currently using the keybox. */
However, in gpgsm this is done
Hi all,
On 18.07.19 12:19, ilf wrote:
> Same on a different box with a different keyring. I trimmed it down from
> ~1250 keys to ~350 keys, but the size of pubring.kbx remains 19M.
>
> Does --delete really mean *delete* with keybox?
>
> ilf:
>> This got my keyring down from 4.600 to 1.000 keys:
Same on a different box with a different keyring. I trimmed it down from
~1250 keys to ~350 keys, but the size of pubring.kbx remains 19M.
Does --delete really mean *delete* with keybox?
ilf:
This got my keyring down from 4.600 to 1.000 keys:
But the keybox file didn't get any smaller:
--
il
Over the years, my keyring grew and got rather big. So I did some
cleaning and deleted some revoked and otherwise useless certificates.
(If you wonder how, see this script - feedback welcome:
https://github.com/ilf/gpg-maintenance/blob/master/gpg-delete-revoked-keys.sh)
This got my keyring do