All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrei Borzenkov <arvidjaar@gmail.com>
To: Jonathan McCune <jonmccune@google.com>
Cc: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: test command and signature checks
Date: Thu, 29 Jan 2015 18:19:48 +0300	[thread overview]
Message-ID: <20150129181948.5add5d29@opensuse.site> (raw)
In-Reply-To: <CADtfRCWC4-mQJPsivzu9r7xbzHkhi_3pVj=7Mc2DaUOk3MU6yw@mail.gmail.com>

В Thu, 29 Jan 2015 06:17:42 -0800
Jonathan McCune <jonmccune@google.com> пишет:

> On Jan 29, 2015 1:19 AM, "Andrei Borzenkov" <arvidjaar@gmail.com> wrote:
> >
> > What sematic of file tests should be? I think they should just test
> > file existence; this already happens for compressed files that checks
> > that on-disk file size, not uncompressed. I think same should apply to
> > signature checks.
> >
> 
> Where the alternative is that an existence check will only succeed if a
> file has a corresponding (and verifiable) .sig?
> 
> I think existence-only is the right semantics because verify_detached can
> be used to achieve the signature-check in a standalone fashion.
> 
> (I.e., the existing behavior of test and verify_detached seems correct to
> me.)
> 

Existing behavior is to simply open file so any filter in effect will
be applied.

> > May be file checks should simply disable all filters unconditionally
> > to become more lightweight.
> >
> > _______________________________________________
> > Grub-devel mailing list
> > Grub-devel@gnu.org
> > https://lists.gnu.org/mailman/listinfo/grub-devel



  reply	other threads:[~2015-01-29 15:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-29  9:19 test command and signature checks Andrei Borzenkov
2015-01-29 14:17 ` Jonathan McCune
2015-01-29 15:19   ` Andrei Borzenkov [this message]
2015-01-29 17:12     ` Jonathan McCune

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=20150129181948.5add5d29@opensuse.site \
    --to=arvidjaar@gmail.com \
    --cc=grub-devel@gnu.org \
    --cc=jonmccune@google.com \
    /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.