Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

gnome-keyring-daemon(1) [centos man page]

GNOME-KEYRING-DAEM(1)						   User Commands					     GNOME-KEYRING-DAEM(1)

gnome-keyring-daemon - The gnome-keyring daemon SYNOPSIS
gnome-keyring-daemon [OPTION...] DESCRIPTION
The gnome-keyring-daemon is a service that stores your passwords and secrets. It is normally started automatically when a user logs into a desktop session. The gnome-keyring-daemon implements the DBus Secret Service API, and you can use tools like seahorse or secret-tool to interact with it. The daemon also implements a GnuPG and SSH agent both of which automatically load the user's keys, and prompt for passwords when necessary. The daemon will print out various environment variables which should be set in the user's environment, in order to interact with the daemon. OPTIONS
The various startup arguments below can be used: -c, --components=ssh,secrets,gpg,pkcs11 Ask the daemon to only initialize certain components. Valid components are ssh, gpg, secrets, pkcs11. By default all components are initialized. -C, --control-directory=/path/to/directory Use this directory for creating communication sockets. By default a temporary directory is automatically created. -d, --daemonize Run as a real daemon, disconnected from the terminal. -f, --foreground Run in the foreground, and do not fork or become a daemon. -l, --login This argument tells the daemon it is being run by PAM. It reads all of stdin (including any newlines) as a login password and does not complete actual initialization. The daemon should later be initialized with a gnome-keyring-daemon --start invocation. This option may not be used together with either the --replace or --start arguments. -r, --replace Try to replace a running keyring daemon, and assume its environment avriables. A successful replacement depends on the GNOMKE_KEYRING_CONTROL environment variable being set by an earlier daemon. This option may not be used together with either the --login or --start arguments. -s, --start Connect to an already running daemon and initialize it. This is often used to complete initialization of a daemon that was started by PAM using the --login argument. This option may not be used together with either the --login or --replace arguments. -V, --version Print out the gnome-keyring version and then exit. -h, --help Show help options and exit. BUGS
Please send bug reports to either the distribution bug tracker or the upstream bug tracker at SEE ALSO
secret-tool(1), seahorse(1) Further details available in the gnome-keyring online documentation at and in the secret-service online documentation at gnome-keyring GNOME-KEYRING-DAEM(1)

Check Out this Related Man Page

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

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)
Man Page