How to produce a printable PGP detached signature (eventually in base16)?
up vote
1
down vote
favorite
Given a detached signature mydoc.sig of a document mydoc produced with
gpg --local-user <GPG_RECIPIENT> --detach-sig mydoc
How can I create a printable output of this signature in base16 (as when exporting a private key with paperkey)?
The ASCII armor signature is a convenient output to be printed,
Obviously the following is not working
cat mydoc.sig | paperkey
Unable to find secret key packet
I am looking for a output like the one below:
gpg gpg-agent
asked Apr 20 '17 at 11:16
user123456
1,49521532
add a comment |
up vote
1
down vote
favorite
Given a detached signature mydoc.sig of a document mydoc produced with
gpg --local-user <GPG_RECIPIENT> --detach-sig mydoc
How can I create a printable output of this signature in base16 (as when exporting a private key with paperkey)?
The ASCII armor signature is a convenient output to be printed,
Obviously the following is not working
cat mydoc.sig | paperkey
Unable to find secret key packet
I am looking for a output like the one below:
gpg gpg-agent
asked Apr 20 '17 at 11:16
user123456
1,49521532
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
Given a detached signature mydoc.sig of a document mydoc produced with
gpg --local-user <GPG_RECIPIENT> --detach-sig mydoc
How can I create a printable output of this signature in base16 (as when exporting a private key with paperkey)?
The ASCII armor signature is a convenient output to be printed,
Obviously the following is not working
cat mydoc.sig | paperkey
Unable to find secret key packet
I am looking for a output like the one below:
gpg gpg-agent
asked Apr 20 '17 at 11:16
user123456
1,49521532
Given a detached signature mydoc.sig of a document mydoc produced with
gpg --local-user <GPG_RECIPIENT> --detach-sig mydoc
How can I create a printable output of this signature in base16 (as when exporting a private key with paperkey)?
The ASCII armor signature is a convenient output to be printed,
Obviously the following is not working
cat mydoc.sig | paperkey
Unable to find secret key packet
I am looking for a output like the one below:
gpg gpg-agent
gpg gpg-agent
asked Apr 20 '17 at 11:16
user123456
1,49521532
asked Apr 20 '17 at 11:16
user123456
1,49521532
edited Nov 29 at 16:07
asked Apr 20 '17 at 11:16
user123456
1,49521532
asked Apr 20 '17 at 11:16
user123456
1,49521532
asked Apr 20 '17 at 11:16
user123456
1,49521532
1,49521532
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
2
down vote
accepted
od -t x1 mydoc.sig
produces similar output that should be just as usable.
As you presumably know since you mention it in your question, you can also create an ASCII-armored signature using
gpg --detach-sig -a mydoc
I don’t know whether you’d consider that good enough for printing as-is though. There’s not much point piping that through od, it will include a CRC but it will also be quite a bit longer than the piped binary signature.
answered Apr 20 '17 at 11:19
Stephen Kitt
160k24357432
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
accepted
od -t x1 mydoc.sig
produces similar output that should be just as usable.
As you presumably know since you mention it in your question, you can also create an ASCII-armored signature using
gpg --detach-sig -a mydoc
I don’t know whether you’d consider that good enough for printing as-is though. There’s not much point piping that through od, it will include a CRC but it will also be quite a bit longer than the piped binary signature.
answered Apr 20 '17 at 11:19
Stephen Kitt
160k24357432
add a comment |
up vote
2
down vote
accepted
od -t x1 mydoc.sig
produces similar output that should be just as usable.
As you presumably know since you mention it in your question, you can also create an ASCII-armored signature using
gpg --detach-sig -a mydoc
I don’t know whether you’d consider that good enough for printing as-is though. There’s not much point piping that through od, it will include a CRC but it will also be quite a bit longer than the piped binary signature.
answered Apr 20 '17 at 11:19
Stephen Kitt
160k24357432
add a comment |
up vote
2
down vote
accepted
up vote
2
down vote
accepted
od -t x1 mydoc.sig
produces similar output that should be just as usable.
As you presumably know since you mention it in your question, you can also create an ASCII-armored signature using
gpg --detach-sig -a mydoc
I don’t know whether you’d consider that good enough for printing as-is though. There’s not much point piping that through od, it will include a CRC but it will also be quite a bit longer than the piped binary signature.
answered Apr 20 '17 at 11:19
Stephen Kitt
160k24357432
od -t x1 mydoc.sig
produces similar output that should be just as usable.
As you presumably know since you mention it in your question, you can also create an ASCII-armored signature using
gpg --detach-sig -a mydoc
I don’t know whether you’d consider that good enough for printing as-is though. There’s not much point piping that through od, it will include a CRC but it will also be quite a bit longer than the piped binary signature.
answered Apr 20 '17 at 11:19
Stephen Kitt
160k24357432
edited Apr 20 '17 at 11:42
answered Apr 20 '17 at 11:19
Stephen Kitt
160k24357432
answered Apr 20 '17 at 11:19
Stephen Kitt
160k24357432
answered Apr 20 '17 at 11:19
Stephen Kitt
160k24357432
160k24357432
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f360152%2fhow-to-produce-a-printable-pgp-detached-signature-eventually-in-base16%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
