-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
On Sun, 6 Aug 2017 11:16:19 +0100, MFPA wrote:
> I tested using text written in Notepad under Windows 10, then
> clearsigned using GnuPG, pasted into Facebook, and hit "post". When
> the post appeared on my timeline, I copied the text back from the post
> and verified the signature without any err
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Saturday 5 August 2017 at 2:56:20 PM, in
, Stefan Claas wrote:-
> Well, to me the formatting then looks a bit ugly. :-)
It does look ugly. But it is a text message, not a presentation.
> But when importing back and verifying it i get:
>
On Sun, 6 Aug 2017 00:29:37 -0500, Werewolf wrote:
> A simpler methode on a linux system
> gpg --clearsign|qrencode -o message.png
> For Decoding message and verifying signature
> zbarimg message.jpg| sed "s/QR-Code:-/-/g"|gpg
>
> or just to verify signature
> zbarimg message.png| sed "s/QR-C
On Fri, Aug 04, 2017 at 02:46:19PM +0200, Stefan Claas wrote:
> So, simply prepare your short GnuPG message and then do a:
>
> $ qrencode -o message.png < message.txt.asc, to obtain a
> .png image, ready to be posted on social media sites.
A simpler methode on a linux system
gpg --clearsign|qren
