public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Alexander Zangerl <az@bond.edu.au>
Cc: torvalds@osdl.org, akpm@osdl.org, keyrings@linux-nfs.org,
	linux-kernel@vger.kernel.org
Subject: Re: [Keyrings] [PATCH] Keys: Permit key expiry time to be set
Date: Thu, 17 Nov 2005 22:08:06 +0000	[thread overview]
Message-ID: <8585.1132265286@warthog.cambridge.redhat.com> (raw)
In-Reply-To: <25039.1132150357@warthog.cambridge.redhat.com>


I've stuck an updated keyutils tarball and SRPM on:

	http://people.redhat.com/~dhowells/keyutils/keyutils-0.3-2.tar.bz2 
	http://people.redhat.com/~dhowells/keyutils/keyutils-0.3-2.src.rpm

For those who want to play with the new facilities.


Alexander Zangerl: I've incorporated my take on your patch by which
/sbin/request-key can be made to dangle a slave program at the ends of a pair
of pipes to do the work. The callout_info is passed to stdin and the payload
data retrieved via stdout. You configure it by sticking a '|' symbol in front
of the program name in /etc/request-key.conf. Can you test it please. That bit
compiles, but I haven't had time to test it yet, so it may not work.

David

  parent reply	other threads:[~2005-11-17 22:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-16 14:12 [PATCH] Keys: Permit key expiry time to be set David Howells
2005-11-16 14:19 ` [PATCH] Keys: Discard duplicate keys from a keyring on link David Howells
2005-11-16 19:19   ` [PATCH] Keys: Permit running process to instantiate keys David Howells
2005-11-17  2:09 ` [PATCH] Keys: Permit key expiry time to be set Andrew Morton
2005-11-17 22:08 ` David Howells [this message]
2005-11-18 15:53   ` [Keyrings] " David Howells

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=8585.1132265286@warthog.cambridge.redhat.com \
    --to=dhowells@redhat.com \
    --cc=akpm@osdl.org \
    --cc=az@bond.edu.au \
    --cc=keyrings@linux-nfs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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