Difference between revisions of "GNOME/Keyring"
m (→Unlock at Startup: one "look" was enoguh) |
|||
(40 intermediate revisions by 22 users not shown) | |||
Line 1: | Line 1: | ||
− | [[Category: | + | [[Category:GNOME]] |
− | [[ | + | From [https://live.gnome.org/GnomeKeyring/ GnomeKeyring]: |
− | {{ | + | :''GNOME Keyring is a collection of components in GNOME that store secrets, passwords, keys, certificates and make them available to applications.'' |
+ | {{Note| 1=Gnome Keyring does not support ECDSA keys. See [https://bugzilla.gnome.org/show_bug.cgi?id=641082 Bug 641082].}} | ||
+ | == Installation == | ||
+ | If you're using GNOME, gnome-keyring got installed automatically as a part of it. If you're using a different setup, install {{Pkg|gnome-keyring}} from the [[official repositories]]. | ||
− | + | == Manage using GUI == | |
+ | # pacman -S seahorse | ||
+ | It is possible to leave the GNOME keyring password blank or change it. In seahorse, in the "View" dropdown, select "By Keyring". On the Passwords tab, right click on "Passwords: login" and pick "Change password." Enter the old password and leave empty the new password. You will be warned about using unencrypted storage; continue by pushing "Use Unsafe Storage." | ||
− | + | == Use Without GNOME == | |
+ | It is possible to use GNOME Keyring without the rest of the GNOME desktop. To do this, add the following to your {{ic|~/.xinitrc}} file: | ||
+ | # Start a D-Bus session | ||
+ | source /etc/X11/xinit/xinitrc.d/30-dbus | ||
+ | # Start GNOME Keyring | ||
+ | eval $(/usr/bin/gnome-keyring-daemon --start --components=gpg,pkcs11,secrets,ssh) | ||
+ | # You probably need to do this too: | ||
+ | export GNOME_KEYRING_CONTROL GNOME_KEYRING_PID GPG_AGENT_INFO SSH_AUTH_SOCK | ||
+ | See {{bug|13986}} for more info. | ||
− | + | If you experience problems retrieving information from the keyring, make sure that the variables "DBUS_SESSION_BUS_ADDRESS" and "DBUS_SESSION_BUS_PID" are exported in the target environment. | |
− | |||
− | |||
− | + | Instructions on how to use GNOME Keyring in Xfce are in the [[Xfce#SSH_Agents|SSH Agents section]] on that page. | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
== SSH Keys == | == SSH Keys == | ||
Line 35: | Line 40: | ||
Now when you connect to a server, the key will be found and a dialog will popup asking you for the passphrase. It has an option to automatically unlock the key when you login. If you check this you will not need to enter your passphrase again! | Now when you connect to a server, the key will be found and a dialog will popup asking you for the passphrase. It has an option to automatically unlock the key when you login. If you check this you will not need to enter your passphrase again! | ||
− | == | + | == Integration with applications == |
− | + | ||
+ | * [[Firefox#GNOME_Keyring_integration]] | ||
+ | |||
+ | == Gnome Keyring dialog and SSH == | ||
+ | |||
+ | Run in a terminal, the following: | ||
− | + | $ gnome-keyring-daemon -s | |
− | SSH_AUTH_SOCK=` | + | Output will get a few lines, but in reality we are interested, {{ic|SSH_AUTH_SOCK}}, example: |
+ | |||
+ | GNOME_KEYRING_C................. | ||
+ | SSH_AUTH_SOCK=/run/user/1000/keyring-XXXXXX/ssh | ||
+ | GPG_AGENT_INF................... | ||
+ | |||
+ | Now you should add to your {{ic|~/.bashrc}}, according to the output of the previous command, for example: | ||
+ | |||
+ | SSH_AUTH_SOCK=`ss -xl | grep -o '/run/user/1000/keyring-.*/ssh$'` | ||
[ -z "$SSH_AUTH_SOCK" ] || export SSH_AUTH_SOCK | [ -z "$SSH_AUTH_SOCK" ] || export SSH_AUTH_SOCK | ||
If you run on your terminal the following: | If you run on your terminal the following: | ||
− | echo $SSH_AUTH_SOCK | + | $ echo $SSH_AUTH_SOCK |
will return something like the following: | will return something like the following: | ||
− | / | + | /run/user/1000/keyring--XXXXXX/ssh |
Now when you connect with ssh, gnome-keyring dialog will launch the "entry of the passphrase" | Now when you connect with ssh, gnome-keyring dialog will launch the "entry of the passphrase" | ||
+ | |||
+ | == Gnome Keyring and Git == | ||
+ | The Gnome keyring is useful in use with Git when you are pushing over https. | ||
+ | First compile the helper | ||
+ | $ cd /usr/share/git/credential/gnome-keyring | ||
+ | # make | ||
+ | Set Git up to use the helper | ||
+ | $ git config --global credential.helper /usr/share/git/credential/gnome-keyring/git-credential-gnome-keyring | ||
+ | Next time you do a git push, you'll be asked to unlock your keyring | ||
== Unlock at Startup == | == Unlock at Startup == | ||
− | GNOME's login manager (gdm) will automatically unlock the keyring once you | + | GNOME's login manager ({{pkg|gdm}}) will automatically unlock the keyring once you log in; for others it is not so easy. |
− | For SLiM, see [[SLiM#SLiM_and_Gnome_Keyring]] | + | For SLiM, see [[SLiM#SLiM_and_Gnome_Keyring]], This method works for KDM as well, but you need to edit {{ic|/etc/pam.d/kde}} instead of {{ic|/etc/pam.d/slim}}. |
If you are using automatic login, then you can disable the keyring manager by setting a blank password on the login keyring. '''Note''': your passwords will be stored unencrypted if you do this. | If you are using automatic login, then you can disable the keyring manager by setting a blank password on the login keyring. '''Note''': your passwords will be stored unencrypted if you do this. | ||
+ | |||
+ | If you use console based login, automatic unlocking of the keyring can be achieved by the following changes in {{ic|/etc/pam.d/login}}: | ||
+ | Add {{ic|auth optional pam_gnome_keyring.so}} at the end of the {{ic|auth}} section and {{ic|session optional pam_gnome_keyring.so auto_start}} at the end of the {{ic|session}} section. The result should look similar to this: | ||
+ | #%PAM-1.0 | ||
+ | |||
+ | auth required pam_securetty.so | ||
+ | auth requisite pam_nologin.so | ||
+ | auth include system-local-login | ||
+ | auth optional pam_gnome_keyring.so | ||
+ | account include system-local-login | ||
+ | session include system-local-login | ||
+ | session optional pam_gnome_keyring.so auto_start | ||
+ | |||
+ | Next, add {{ic|password optional pam_gnome_keyring.so}} to the end of {{ic|/etc/pam.d/passwd}}. The file should look somewhat like this: | ||
+ | #%PAM-1.0 | ||
+ | #password required pam_cracklib.so difok=2 minlen=8 dcredit=2 ocredit=2 retry=3 | ||
+ | #password required pam_unix.so sha512 shadow use_authtok | ||
+ | password required pam_unix.so sha512 shadow nullok | ||
+ | password optional pam_gnome_keyring.so | ||
+ | |||
+ | {{Note|To use automatic unlocking, the same password for the user account and the keyring have to be set.}} | ||
+ | |||
+ | == Useful Tools == | ||
+ | === gnome-keyring-query === | ||
+ | {{AUR|gnome-keyring-query}} from the AUR provides a simple command-line tool for querying passwords from the password store of the GNOME Keyring. |
Revision as of 21:10, 17 September 2013
From GnomeKeyring:
- GNOME Keyring is a collection of components in GNOME that store secrets, passwords, keys, certificates and make them available to applications.
Contents
Installation
If you're using GNOME, gnome-keyring got installed automatically as a part of it. If you're using a different setup, install gnome-keyring from the official repositories.
Manage using GUI
# pacman -S seahorse
It is possible to leave the GNOME keyring password blank or change it. In seahorse, in the "View" dropdown, select "By Keyring". On the Passwords tab, right click on "Passwords: login" and pick "Change password." Enter the old password and leave empty the new password. You will be warned about using unencrypted storage; continue by pushing "Use Unsafe Storage."
Use Without GNOME
It is possible to use GNOME Keyring without the rest of the GNOME desktop. To do this, add the following to your ~/.xinitrc
file:
# Start a D-Bus session source /etc/X11/xinit/xinitrc.d/30-dbus # Start GNOME Keyring eval $(/usr/bin/gnome-keyring-daemon --start --components=gpg,pkcs11,secrets,ssh) # You probably need to do this too: export GNOME_KEYRING_CONTROL GNOME_KEYRING_PID GPG_AGENT_INFO SSH_AUTH_SOCK
See FS#13986 for more info.
If you experience problems retrieving information from the keyring, make sure that the variables "DBUS_SESSION_BUS_ADDRESS" and "DBUS_SESSION_BUS_PID" are exported in the target environment.
Instructions on how to use GNOME Keyring in Xfce are in the SSH Agents section on that page.
SSH Keys
To add your SSH key:
$ ssh-add ~/.ssh/id_dsa Enter passphrase for /home/mith/.ssh/id_dsa:
To list automatically loaded keys:
$ ssh-add -L
To disable all keys;
$ ssh-add -D
Now when you connect to a server, the key will be found and a dialog will popup asking you for the passphrase. It has an option to automatically unlock the key when you login. If you check this you will not need to enter your passphrase again!
Integration with applications
Gnome Keyring dialog and SSH
Run in a terminal, the following:
$ gnome-keyring-daemon -s
Output will get a few lines, but in reality we are interested, SSH_AUTH_SOCK
, example:
GNOME_KEYRING_C................. SSH_AUTH_SOCK=/run/user/1000/keyring-XXXXXX/ssh GPG_AGENT_INF...................
Now you should add to your ~/.bashrc
, according to the output of the previous command, for example:
SSH_AUTH_SOCK=`ss -xl | grep -o '/run/user/1000/keyring-.*/ssh$'` [ -z "$SSH_AUTH_SOCK" ] || export SSH_AUTH_SOCK
If you run on your terminal the following:
$ echo $SSH_AUTH_SOCK
will return something like the following:
/run/user/1000/keyring--XXXXXX/ssh
Now when you connect with ssh, gnome-keyring dialog will launch the "entry of the passphrase"
Gnome Keyring and Git
The Gnome keyring is useful in use with Git when you are pushing over https. First compile the helper
$ cd /usr/share/git/credential/gnome-keyring # make
Set Git up to use the helper
$ git config --global credential.helper /usr/share/git/credential/gnome-keyring/git-credential-gnome-keyring
Next time you do a git push, you'll be asked to unlock your keyring
Unlock at Startup
GNOME's login manager (gdm) will automatically unlock the keyring once you log in; for others it is not so easy.
For SLiM, see SLiM#SLiM_and_Gnome_Keyring, This method works for KDM as well, but you need to edit /etc/pam.d/kde
instead of /etc/pam.d/slim
.
If you are using automatic login, then you can disable the keyring manager by setting a blank password on the login keyring. Note: your passwords will be stored unencrypted if you do this.
If you use console based login, automatic unlocking of the keyring can be achieved by the following changes in /etc/pam.d/login
:
Add auth optional pam_gnome_keyring.so
at the end of the auth
section and session optional pam_gnome_keyring.so auto_start
at the end of the session
section. The result should look similar to this:
#%PAM-1.0 auth required pam_securetty.so auth requisite pam_nologin.so auth include system-local-login auth optional pam_gnome_keyring.so account include system-local-login session include system-local-login session optional pam_gnome_keyring.so auto_start
Next, add password optional pam_gnome_keyring.so
to the end of /etc/pam.d/passwd
. The file should look somewhat like this:
#%PAM-1.0 #password required pam_cracklib.so difok=2 minlen=8 dcredit=2 ocredit=2 retry=3 #password required pam_unix.so sha512 shadow use_authtok password required pam_unix.so sha512 shadow nullok password optional pam_gnome_keyring.so
Useful Tools
gnome-keyring-query
gnome-keyring-queryAUR from the AUR provides a simple command-line tool for querying passwords from the password store of the GNOME Keyring.