Open Benjamin-Loison opened 5 months ago
My Stack Exchange answer seems simple enough to meet my needs.
Ideally it would be nice that just gpg --sign
and gpg --verify
and it precise whether or not there was a verifiable timestamp in it and how it was verified.
Possibly --sign
or --upgrade
or --verify
with --wait
.
Related to #4 and #5.
That way would transform:
To generate:
echo -n 'To sign' > doc.txt gpg --clearsign doc.txt ots stamp -m 1 -c https://alice.btc.calendar.opentimestamps.org doc.txt.asc doc.txt.asc # cf #5 ots upgrade --wait doc.txt.asc.ots zip signature.zip doc.txt.asc{,.ots} cat signature.zip | base64 | qrencode -l H -o signature.png
To verify:
zbarimg --raw signature.png | base64 -d > signature.zip unzip signature.zip rm signature.zip ots verify doc.txt.asc.ots gpg --verify doc.txt.asc cat doc.txt.asc
to:
To generate:
echo -n 'To sign' > doc.txt
gpg --clearsign doc.txt --ots -m 1 -c https://alice.btc.calendar.opentimestamps.org
qrencode -r doc.txt.asc -l H -o signature.png
To verify:
zbarimg --raw signature.png > doc.txt.asc
gpg --verify doc.txt.asc
cat doc.txt.asc
Related to Benjamin_Loison/gpg/issues/1.
blob/185a5997cf315402747223a1feae18e669ae08f2/ots-git-gpg-wrapper.sh
DuckDuckGo results for
gpg opentimestamps
are not interesting. For this search Google only brings this interesting result and following messages up to this one it seems.