libgnome-keyring(3) [opensolaris man page]

libgnome-keyring(3)						C Library Functions					       libgnome-keyring(3)

NAME

       libgnome-keyring - gnome keyring library.

DESCRIPTION

       GNOME Keyring is a system to store passwords and other sensitive data in a standardized way across all GNOME applications.

       A  keyring  stores  a collection of encrypted passwords and encrypted information about those passwords. A user can have multiple keyrings,
       each for a different use, but there is a default one, called 'login'. There is also a special 'session' keyring which is not stored on disk
       and goes away when you log out.

       When a user logs into GNOME, the keyrings are locked and a master keyring password has to be provided in order to unlock each of them.

       GNOME  Keyring  includes  an  SSH  agent which integrates with the gnome-keyring and user login for its passwords. It can also use the main
       X.509 private key store.

       GNOME Keyring will set the SSH_AUTH_SOCK environment variable when it starts up.

       The id_rsa and id_dsa files in ~/.ssh are automatically usable through the SSH agent without first 'loading' them. Other X.509 private keys
       marked with the 'ssh-authentication' purpose are also usable.

       Additional SSH keys can be manually loaded and managed via the ssh-add command.

       If  you	use another SSH agent(such as the ssh-agent included with OpenSSH), you may want to disable the SSH agent in GNOME Keyring to pre-
       vent ssh from using it instead of your prefered SSH agent. You can set /apps/gnome-keyring/daemon-components/ssh gconf key to  false.  This
       prevents the SSH component of gnome-keyring from starting up when the user logs in.

ATTRIBUTES

       See attributes(5) for descriptions of the following attributes:

       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE	     |	    ATTRIBUTE VALUE	   |
       +-----------------------------+-----------------------------+
       |Availability		     |SUNWgnome-libs		   |
       +-----------------------------+-----------------------------+
       |Interface stability	     |Volatile			   |
       +-----------------------------+-----------------------------+

SEE ALSO

       gnome-keyring-daemon(1), attributes(5), gnome-interfaces(5)

       http://library.gnome.org/devel/gnome-keyring/stable/

NOTES

       Written by Jeff Cai, Sun Microsystems Inc., 2008.

SunOS 5.11							    31 Jul 2008 					       libgnome-keyring(3)

Check Out this Related Man Page

USER-KEYRING(7) 					     Linux Programmer's Manual						   USER-KEYRING(7)

NAME

       user-keyring - per-user keyring

DESCRIPTION

       The  user  keyring  is  a keyring used to anchor keys on behalf of a user.  Each UID the kernel deals with has its own user keyring that is
       shared by all processes with that UID.  The user keyring has a name (description) of the form _uid.<UID> where <UID> is the user ID of  the
       corresponding user.

       The  user  keyring  is associated with the record that the kernel maintains for the UID.  It comes into existence upon the first attempt to
       access either the user keyring, the user-session-keyring(7), or the session-keyring(7).	The keyring remains pinned in existence so long as
       there  are  processes  running  with that real UID or files opened by those processes remain open.  (The keyring can also be pinned indefi-
       nitely by linking it into another keyring.)

       Typically, the user keyring is created by pam_keyinit(8) when a user logs in.

       The user keyring is not searched by default by request_key(2).  When pam_keyinit(8) creates a session keyring, it adds to it a link to  the
       user keyring so that the user keyring will be searched when the session keyring is.

       A  special  serial  number  value,  KEY_SPEC_USER_KEYRING,  is  defined that can be used in lieu of the actual serial number of the calling
       process's user keyring.

       From the keyctl(1) utility, '@u' can be used instead of a numeric key ID in much the same way.

       User keyrings are independent of clone(2), fork(2), vfork(2), execve(2), and _exit(2) excepting that the keyring is destroyed when the  UID
       record is destroyed when the last process pinning it exits.

       If  it  is  necessary  for  a  key associated with a user to exist beyond the UID record being garbage collected--for example, for use by a
       cron(8) script--then the persistent-keyring(7) should be used instead.

       If a user keyring does not exist when it is accessed, it will be created.

SEE ALSO

       keyctl(1), keyctl(3), keyrings(7), persistent-keyring(7), process-keyring(7), session-keyring(7), thread-keyring(7),
       user-session-keyring(7), pam_keyinit(8)

Linux								    2017-03-13							   USER-KEYRING(7)

Linux and UNIX Man Pages

libgnome-keyring(3) [opensolaris man page]

Check Out this Related Man Page