From: Andrey Borzenkov <arvidjaar@gmail.com>
To: grub-devel@gnu.org
Subject: Re: DSA GnuPG signatures
Date: Sun, 13 Jan 2013 12:33:30 +0400 [thread overview]
Message-ID: <20130113123330.32f5d374@opensuse.site> (raw)
In-Reply-To: <50F07BFE.4050800@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 879 bytes --]
В Fri, 11 Jan 2013 21:54:22 +0100
Vladimir 'φ-coder/phcoder' Serbinenko <phcoder@gmail.com> пишет:
> Hello, all. I've just committed import of libgcrypt and implementation
> of related code to check signatures. Short usage:
> verify_detached FILE FILE.sig [pubkey.gpg]
Just to be sure. Signature is created using
gpg --detach-sign FILE
correct?
> trust KEY.gpg
> distruct KEYID
distrust?
> check_signatures=[enforce|no]
>
There is no command to list currently trusted keys. Would it be
useful? key_list or "trust --list"?
> grub-mkimage -k KEY gcry_dsa verify [...]
>
> When check_signatures=enforce every time anthing tries to open a file
> its signature (file.sig) is looked for and the open fails if signature
> is absent or invalid.
This means - *any* file, including grub.cfg, themes etc? Or does it
apply to modules only?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2013-01-13 8:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-11 20:54 DSA GnuPG signatures Vladimir 'φ-coder/phcoder' Serbinenko
2013-01-11 22:14 ` Colin Watson
2013-01-11 22:46 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-01-13 8:33 ` Andrey Borzenkov [this message]
2013-01-13 16:47 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-01-31 12:49 ` Andrey Borzenkov
2013-04-03 14:34 ` Vladimir 'φ-coder/phcoder' Serbinenko
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130113123330.32f5d374@opensuse.site \
--to=arvidjaar@gmail.com \
--cc=grub-devel@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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.