From: "Ludovic Courtès" <ludovic.courtes@inria.fr>
To: 43421@debbugs.gnu.org
Subject: bug#43421: Encoding issue in exported archive signatures
Date: Tue, 15 Sep 2020 14:18:17 +0200 [thread overview]
Message-ID: <877dsvi67q.fsf@inria.fr> (raw)
Following the ‘guix authenticate’ in commit
64cf660f872fb7aaf0d2b463e45b4c756297f743¹, I’m observing encoding
issues:
guix archive --export \
/gnu/store/3p5wcw2a0844rbcmlrqfjx8bx7b7gq34-r-rvest-0.3.6-guile-builder
yield an archive with this signature:
--8<---------------cut here---------------start------------->8---
(signature
(data
(flags rfc6979)
(hash sha256 #1DEE0418AF5FD8A05D2142290BA03735176FA27BB68B3A02977C774EA3DBDAEC#)
)
(sig-val
(ecdsa
(r #072B8E5C6B84D4ED469EC2CF63103621602E9AF3902E454CAD49CFA6BDE2FBF0#)
(s "~%*Øw2%YZ»+yvc*¤Ì44C;RM\t3EQIp<ü")
)
)
(public-key
(ecc
(curve Ed25519)
(q #8D156F295D24B0D9A86FA5741A840FF2D24F60F7B6C4134814AD55625971B394#)
)
)
)
--8<---------------cut here---------------end--------------->8---
Notice the ‘s’ field of the signature.
The problem does not occur systematically: it depends on the byte string
(libgcrypt encodes Latin-1ish strings as strings and other strings as
hex sequences.) The problem is similar to <https://issues.guix.gnu.org/17312>.
The interesting bit is that this archive can be correctly ingested by a
new daemon, but it fails signature verification with an older daemon.
Ludo’.
¹ https://issues.guix.gnu.org/43340
next reply other threads:[~2020-09-15 12:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 12:18 Ludovic Courtès [this message]
2020-09-15 15:42 ` bug#43421: Encoding issue in exported archive signatures Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877dsvi67q.fsf@inria.fr \
--to=ludovic.courtes@inria.fr \
--cc=43421@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).