unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Nikita Karetnikov <nikita@karetnikov.org>
Cc: guix-devel@gnu.org
Subject: Re: ‘guix authenticate’: Throw to key `gcry-error' with args `(536871113)'.
Date: Tue, 11 Feb 2014 23:26:21 +0100	[thread overview]
Message-ID: <878uth4776.fsf@gnu.org> (raw)
In-Reply-To: <87r479720q.fsf@karetnikov.org> (Nikita Karetnikov's message of "Wed, 12 Feb 2014 01:49:57 +0400")

Nikita Karetnikov <nikita@karetnikov.org> skribis:

> The keypair was created this way:
>
> $ openssl genrsa -out ./cache-key.sec 2048
> $ openssl rsa -in ./cache-key.sec -pubout > ./cache-key.pub
>
> All the tests pass.  What’s wrong?
>
> $ guix authenticate rsautl -sign -inkey cache-key.sec -in 3r2n9zm3kxb28klpzgarjxj8x3y3y6wf.narinfo.hash

[...]

> In guix/scripts/authenticate.scm:
>   60: 1 [guix-authenticate "rsautl" "-sign" ...]
> In ice-9/boot-9.scm:
>  793: 0 [call-with-input-file "cache-key.sec" ...]
>
> ice-9/boot-9.scm:793:17: In procedure call-with-input-file:
> ice-9/boot-9.scm:793:17: Throw to key `gcry-error' with args `(536871113)'.

‘guix authenticate’ expects cache-key.sec to be a key in “canonical
sexp” format, like in tests/signing-key.sec.  That’s why it barfs here.

IOW, the idea is that it’s a drop-in replacement for ‘openssl’ in terms
of command-line handling, but what happens behind is very different (see
<https://lists.nongnu.org/archive/html/guix-devel/2013-12/msg00135.html>
and related messages.)

(The command-line compatibility requirement stems from the fact that for
now I want to avoid Guix-specific modifications to the daemon.)

HTH,
Ludo’.

      reply	other threads:[~2014-02-11 22:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-11 21:49 ‘guix authenticate’: Throw to key `gcry-error' with args `(536871113)' Nikita Karetnikov
2014-02-11 22:26 ` Ludovic Courtès [this message]

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=878uth4776.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=nikita@karetnikov.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).