public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Steve French <smfrench@austin.rr.com>
To: linux-kernel@vger.kernel.org
Subject: keyring API, pam and user space
Date: Tue, 15 Feb 2005 12:33:48 -0600	[thread overview]
Message-ID: <4212408C.3070804@austin.rr.com> (raw)

As I was trying to decipher the kernel keyring API this morning, I 
noticed the gnome-keyring/gnom-keyring manager which I thought might 
have already implemented a pam module to store logon info 
(userid/password at a minimum) in the kernel keyring (could avoid the 
need for prompting for the users password in the mount utility - and 
could better impement "multiuser mounts" across the network ie if I can 
get at the password and username in kernel for a particular uid I could 
automatically setup and usie the correct authenticated session for each 
uid on the client without user intervention if the client is configured 
for that).  We do have a quick and dirty pam module for storing the 
passwords via the kernel keyring API but it is a little ugly since we 
could not find a good header with the syscalls etc. already defined.

Unfortunately in grepping through the current gnome-keyring and 
gnome-keyring-manager code from ftp://ftp.gnome.org/pub/GNOME/sources I 
don't see any calls to the kernel API in the gnome keyring code so I 
doubt that the gnome keyring would be any help.  Has there been any work 
to integrate user space tools (pam helper, keyring GUI and libs) with 
the relatively new kernel keyring code?

                 reply	other threads:[~2005-02-15 18:33 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4212408C.3070804@austin.rr.com \
    --to=smfrench@austin.rr.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