mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Serge E. Hallyn" <serue@us.ibm.com>
To: Chris Wright <chrisw@osdl.org>
Cc: Makan Pourzandi <Makan.Pourzandi@ericsson.com>,
	linux-kernel@vger.kernel.org,
	Axelle Apvrille <axelle.apvrille@trusted-logic.fr>,
	serue@us.ibm.com, david.gordon@ericsson.com, gaspoucho@yahoo.com
Subject: Re: [ANNOUNCE] Release Digsig 1.3.1: kernel module for run-time authentication of binaries
Date: Thu, 9 Sep 2004 13:23:01 -0400	[thread overview]
Message-ID: <20040909172301.GA28466@escher.cs.wm.edu> (raw)
In-Reply-To: <20040909092457.L1973@build.pdx.osdl.net>

> >      - support to avoid vulnerability for rewrite of shared
> >      libraries
> 
> Could you elaborate on this one?

When a file is being executed, deny_write_access(file) is called to
prevent writing until execution completes.  Because deny_write_access
is not exported from fs/namei.c, we emulate this behavior for shared
libraries.

> > Future works
> > =============
> > 
> >      - improving the caching and revocation: it is currently tested
> >        and will be sent out soon after stability testing
> 
> Should be helpful enough to cache result until thing's opened for
> writing, or is that what you're doing now?

Exactly.  When the file is opened for writing (which as much as possible
requires the file to not be executed), we uncache the signature
validation.

(The new patch hashes revocations (they were on a linked list), and
steals the seqlock-based structure Rik van Riel had suggested for
the selinux avc cache for use in the signature revocation cache.  There
is no change in functionality, only (hopefully) performance improvements.)

-serge

  reply	other threads:[~2004-09-09 17:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-09 15:55 Makan Pourzandi
2004-09-09 16:24 ` Chris Wright
2004-09-09 17:23   ` Serge E. Hallyn [this message]
2004-09-09 17:42     ` Chris Wright
2004-09-09 18:43       ` Serge E. Hallyn
2004-09-09 17:31   ` Makan Pourzandi
2004-09-09 17:55     ` Chris Wright
2004-09-09 19:05       ` Serge E. Hallyn
2004-09-09 20:40         ` Makan Pourzandi
2004-09-09 21:03           ` Chris Wright
2004-09-09 21:45             ` Serge E. Hallyn
2004-09-10 21:28               ` Chris Wright
2004-09-10 20:53             ` Makan Pourzandi
2004-09-10 21:26               ` Chris Wright

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=20040909172301.GA28466@escher.cs.wm.edu \
    --to=serue@us.ibm.com \
    --cc=Makan.Pourzandi@ericsson.com \
    --cc=axelle.apvrille@trusted-logic.fr \
    --cc=chrisw@osdl.org \
    --cc=david.gordon@ericsson.com \
    --cc=gaspoucho@yahoo.com \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®