ame user, deleted the signature and encryption entries relating to
those bindings, then restored from the dump file. I don't know what
issues this may introduce but I no longer get the "TOFU db corruption
detected" messages.
- --
Best regards
MFPA <mailto:20
7771 18A3 3DDA 9BA4 8E62 AACB 3243 6300 52D9
Thanks,
:) Neal
On Sat, 05 Aug 2017 16:56:02 +0200,
MFPA wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> gpg: TOFU db corruption detected.
> gpg: (further info: user id '[jpeg image of size 24800]' not on key
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Sunday 6 August 2017 at 1:32:09 AM, in
, Daniel
Villarreal wrote:-
> "... run sqlite3 with vacuum, reindex and analyze
Reindex and analyze shrunk my tofu.db by a further 4 KB but GnuPG
unfortunately still reports the same issue.
- --
Best r
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Saturday 5 August 2017 at 4:30:12 PM, in
, Teemu Likonen wrote:-
> Before the developers give you more educated answers
> I'll point out that
> the tofu database is a regular Sqlite database file.
> So you can do:
> $ sqlite3 ~/.gnupg/tof
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 08/05/17 11:30, Teemu Likonen wrote:
> MFPA [2017-08-05 15:56:02+01] wrote:
>
>> ... "rebuild" the TOFU database to get rid of the corruption?
>
> ... tofu [db] is a regular Sqlite [db] file. So you can do:
>
> $ sqlite3 ~/.gnupg/tofu.db
>
> a
MFPA [2017-08-05 15:56:02+01] wrote:
> How do I "rebuild" the TOFU database to get rid of the corruption?
Before the developers give you more educated answers I'll point out that
the tofu database is a regular Sqlite database file. So you can do:
$ sqlite3 ~/.gnupg/tofu.db
and then execute
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
gpg: TOFU db corruption detected.
gpg: (further info: user id '[jpeg image of size 24800]' not on key
block 'Fingerprint')
I see the above message when encrypting to the key whose fingerprint I
have redacted above. The co
