https://wiki.archlinux.org/api.php?action=feedcontributions&user=L1mpm4rk&feedformat=atomArchWiki - User contributions [en]2024-03-29T01:19:14ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=GNOME/Keyring&diff=220998GNOME/Keyring2012-09-01T17:13:18Z<p>L1mpm4rk: /* Gnome Keyring and SSH */</p>
<hr />
<div>[[Category:Daemons and system services]]<br />
[[Category:Desktop environments]]<br />
From [https://live.gnome.org/GnomeKeyring/ GnomeKeyring]:<br />
:''GNOME Keyring is a collection of components in GNOME that store secrets, passwords, keys, certificates and make them available to applications.''<br />
<br />
== Manage using GUI ==<br />
pacman -S seahorse<br />
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."<br />
<br />
== Use Without GNOME ==<br />
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:<br />
# Start a D-Bus session<br />
source /etc/X11/xinit/xinitrc.d/30-dbus<br />
# Start GNOME Keyring<br />
eval $(/usr/bin/gnome-keyring-daemon --start --components=gpg,pkcs11,secrets,ssh)<br />
# You probably need to do this too:<br />
export SSH_AUTH_SOCK<br />
export GPG_AGENT_INFO<br />
export GNOME_KEYRING_CONTROL<br />
export GNOME_KEYRING_PID<br />
See {{bug|13986}} for more info.<br />
<br />
On [[Xfce]] you may need to disable {{ic|gpg-agent}}, silently [http://docs.xfce.org/xfce/xfce4-session/advanced loaded at startup] by {{ic|xfce4-session}}, otherwise the above environment variables will be overwritten. Execute the following command, then log out and log in again:<br />
xfconf-query -c xfce4-session -p /startup/ssh-agent/enabled -n -t bool -s false<br />
<br />
== SSH Keys ==<br />
To add your SSH key:<br />
<br />
$ ssh-add ~/.ssh/id_dsa<br />
Enter passphrase for /home/mith/.ssh/id_dsa:<br />
<br />
To list automatically loaded keys:<br />
<br />
$ ssh-add -L<br />
<br />
To disable all keys;<br />
<br />
$ ssh-add -D<br />
<br />
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!<br />
<br />
== Integration with applications ==<br />
<br />
* [[Firefox#GNOME_integration]]<br />
<br />
== Gnome Keyring dialog and SSH ==<br />
<br />
Run in a terminal, the following:<br />
<br />
$ gnome-keyring-daemon -s<br />
<br />
Output will get a few lines, but in reality we are interested, {{ic|SSH_AUTH_SOCK}}, example:<br />
<br />
GNOME_KEYRING_C.................<br />
SSH_AUTH_SOCK=/run/user/1000/keyring-XXXXXX/ssh<br />
GPG_AGENT_INF...................<br />
<br />
Now you should add to your {{ic|~/.bashrc}}, according to the output of the previous command, for example:<br />
<br />
SSH_AUTH_SOCK=`netstat -xl | grep -o '/run/user/1000/keyring-.*/ssh$'`<br />
[ -z "$SSH_AUTH_SOCK" ] || export SSH_AUTH_SOCK<br />
<br />
If you run on your terminal the following:<br />
<br />
$ echo $SSH_AUTH_SOCK<br />
<br />
will return something like the following:<br />
<br />
/run/user/1000/keyring--XXXXXX/ssh<br />
<br />
Now when you connect with ssh, gnome-keyring dialog will launch the "entry of the passphrase"<br />
<br />
== Unlock at Startup ==<br />
GNOME's login manager ({{pkg|gdm}}) will automatically unlock the keyring once you log in; for others it is not so easy.<br />
<br />
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}}.<br />
<br />
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.<br />
<br />
== Useful Tools ==<br />
=== gnome-keyring-query ===<br />
{{AUR|gnome-keyring-query}} from the AUR provides a simple command-line tool for querying passwords from the password store of the GNOME Keyring.</div>L1mpm4rkhttps://wiki.archlinux.org/index.php?title=GNOME/Keyring&diff=220995GNOME/Keyring2012-09-01T17:10:43Z<p>L1mpm4rk: correction title</p>
<hr />
<div>[[Category:Daemons and system services]]<br />
[[Category:Desktop environments]]<br />
From [https://live.gnome.org/GnomeKeyring/ GnomeKeyring]:<br />
:''GNOME Keyring is a collection of components in GNOME that store secrets, passwords, keys, certificates and make them available to applications.''<br />
<br />
== Manage using GUI ==<br />
pacman -S seahorse<br />
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."<br />
<br />
== Use Without GNOME ==<br />
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:<br />
# Start a D-Bus session<br />
source /etc/X11/xinit/xinitrc.d/30-dbus<br />
# Start GNOME Keyring<br />
eval $(/usr/bin/gnome-keyring-daemon --start --components=gpg,pkcs11,secrets,ssh)<br />
# You probably need to do this too:<br />
export SSH_AUTH_SOCK<br />
export GPG_AGENT_INFO<br />
export GNOME_KEYRING_CONTROL<br />
export GNOME_KEYRING_PID<br />
See {{bug|13986}} for more info.<br />
<br />
On [[Xfce]] you may need to disable {{ic|gpg-agent}}, silently [http://docs.xfce.org/xfce/xfce4-session/advanced loaded at startup] by {{ic|xfce4-session}}, otherwise the above environment variables will be overwritten. Execute the following command, then log out and log in again:<br />
xfconf-query -c xfce4-session -p /startup/ssh-agent/enabled -n -t bool -s false<br />
<br />
== SSH Keys ==<br />
To add your SSH key:<br />
<br />
$ ssh-add ~/.ssh/id_dsa<br />
Enter passphrase for /home/mith/.ssh/id_dsa:<br />
<br />
To list automatically loaded keys:<br />
<br />
$ ssh-add -L<br />
<br />
To disable all keys;<br />
<br />
$ ssh-add -D<br />
<br />
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!<br />
<br />
== Integration with applications ==<br />
<br />
* [[Firefox#GNOME_integration]]<br />
<br />
== Gnome Keyring and SSH ==<br />
<br />
Run in a terminal, the following:<br />
<br />
$ gnome-keyring-daemon -s<br />
<br />
Output will get a few lines, but in reality we are interested, {{ic|SSH_AUTH_SOCK}}, example:<br />
<br />
GNOME_KEYRING_C.................<br />
SSH_AUTH_SOCK=/run/user/1000/keyring-XXXXXX/ssh<br />
GPG_AGENT_INF...................<br />
<br />
Now you should add to your {{ic|~/.bashrc}}, according to the output of the previous command, for example:<br />
<br />
SSH_AUTH_SOCK=`netstat -xl | grep -o '/run/user/1000/keyring-.*/ssh$'`<br />
[ -z "$SSH_AUTH_SOCK" ] || export SSH_AUTH_SOCK<br />
<br />
If you run on your terminal the following:<br />
<br />
$ echo $SSH_AUTH_SOCK<br />
<br />
will return something like the following:<br />
<br />
/run/user/1000/keyring--XXXXXX/ssh<br />
<br />
Now when you connect with ssh, gnome-keyring dialog will launch the "entry of the passphrase"<br />
<br />
== Unlock at Startup ==<br />
GNOME's login manager ({{pkg|gdm}}) will automatically unlock the keyring once you log in; for others it is not so easy.<br />
<br />
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}}.<br />
<br />
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.<br />
<br />
== Useful Tools ==<br />
=== gnome-keyring-query ===<br />
{{AUR|gnome-keyring-query}} from the AUR provides a simple command-line tool for querying passwords from the password store of the GNOME Keyring.</div>L1mpm4rkhttps://wiki.archlinux.org/index.php?title=GNOME/Keyring&diff=220991GNOME/Keyring2012-09-01T16:48:42Z<p>L1mpm4rk: /* The gnome-keyring dialog does not appear in some terminals when connecting with SSH */</p>
<hr />
<div>[[Category:Daemons and system services]]<br />
[[Category:Desktop environments]]<br />
From [https://live.gnome.org/GnomeKeyring/ GnomeKeyring]:<br />
:''GNOME Keyring is a collection of components in GNOME that store secrets, passwords, keys, certificates and make them available to applications.''<br />
<br />
== Manage using GUI ==<br />
pacman -S seahorse<br />
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."<br />
<br />
== Use Without GNOME ==<br />
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:<br />
# Start a D-Bus session<br />
source /etc/X11/xinit/xinitrc.d/30-dbus<br />
# Start GNOME Keyring<br />
eval $(/usr/bin/gnome-keyring-daemon --start --components=gpg,pkcs11,secrets,ssh)<br />
# You probably need to do this too:<br />
export SSH_AUTH_SOCK<br />
export GPG_AGENT_INFO<br />
export GNOME_KEYRING_CONTROL<br />
export GNOME_KEYRING_PID<br />
See {{bug|13986}} for more info.<br />
<br />
On [[Xfce]] you may need to disable {{ic|gpg-agent}}, silently [http://docs.xfce.org/xfce/xfce4-session/advanced loaded at startup] by {{ic|xfce4-session}}, otherwise the above environment variables will be overwritten. Execute the following command, then log out and log in again:<br />
xfconf-query -c xfce4-session -p /startup/ssh-agent/enabled -n -t bool -s false<br />
<br />
== SSH Keys ==<br />
To add your SSH key:<br />
<br />
$ ssh-add ~/.ssh/id_dsa<br />
Enter passphrase for /home/mith/.ssh/id_dsa:<br />
<br />
To list automatically loaded keys:<br />
<br />
$ ssh-add -L<br />
<br />
To disable all keys;<br />
<br />
$ ssh-add -D<br />
<br />
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!<br />
<br />
== Integration with applications ==<br />
<br />
* [[Firefox#GNOME_integration]]<br />
<br />
== The gnome-keyring dialog does not appear in some terminals when connecting with SSH ==<br />
Solution:<br />
<br />
Run in a terminal, the following:<br />
<br />
$ gnome-keyring-daemon -s<br />
<br />
Output will get a few lines, but in reality we are interested, {{ic|SSH_AUTH_SOCK}}, example:<br />
<br />
GNOME_KEYRING_C.................<br />
SSH_AUTH_SOCK=/run/user/1000/keyring-XXXXXX/ssh<br />
GPG_AGENT_INF...................<br />
<br />
Now you should add to your {{ic|~/.bashrc}}, according to the output of the previous command, for example:<br />
<br />
SSH_AUTH_SOCK=`netstat -xl | grep -o '/run/user/1000/keyring-.*/ssh$'`<br />
[ -z "$SSH_AUTH_SOCK" ] || export SSH_AUTH_SOCK<br />
<br />
If you run on your terminal the following:<br />
<br />
$ echo $SSH_AUTH_SOCK<br />
<br />
will return something like the following:<br />
<br />
/run/user/1000/keyring--XXXXXX/ssh<br />
<br />
Now when you connect with ssh, gnome-keyring dialog will launch the "entry of the passphrase"<br />
<br />
== Unlock at Startup ==<br />
GNOME's login manager ({{pkg|gdm}}) will automatically unlock the keyring once you log in; for others it is not so easy.<br />
<br />
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}}.<br />
<br />
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.<br />
<br />
== Useful Tools ==<br />
=== gnome-keyring-query ===<br />
{{AUR|gnome-keyring-query}} from the AUR provides a simple command-line tool for querying passwords from the password store of the GNOME Keyring.</div>L1mpm4rkhttps://wiki.archlinux.org/index.php?title=GNOME/Keyring&diff=220990GNOME/Keyring2012-09-01T16:46:47Z<p>L1mpm4rk: /* The gnome-keyring dialog does not appear in some terminals when connecting with SSH */</p>
<hr />
<div>[[Category:Daemons and system services]]<br />
[[Category:Desktop environments]]<br />
From [https://live.gnome.org/GnomeKeyring/ GnomeKeyring]:<br />
:''GNOME Keyring is a collection of components in GNOME that store secrets, passwords, keys, certificates and make them available to applications.''<br />
<br />
== Manage using GUI ==<br />
pacman -S seahorse<br />
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."<br />
<br />
== Use Without GNOME ==<br />
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:<br />
# Start a D-Bus session<br />
source /etc/X11/xinit/xinitrc.d/30-dbus<br />
# Start GNOME Keyring<br />
eval $(/usr/bin/gnome-keyring-daemon --start --components=gpg,pkcs11,secrets,ssh)<br />
# You probably need to do this too:<br />
export SSH_AUTH_SOCK<br />
export GPG_AGENT_INFO<br />
export GNOME_KEYRING_CONTROL<br />
export GNOME_KEYRING_PID<br />
See {{bug|13986}} for more info.<br />
<br />
On [[Xfce]] you may need to disable {{ic|gpg-agent}}, silently [http://docs.xfce.org/xfce/xfce4-session/advanced loaded at startup] by {{ic|xfce4-session}}, otherwise the above environment variables will be overwritten. Execute the following command, then log out and log in again:<br />
xfconf-query -c xfce4-session -p /startup/ssh-agent/enabled -n -t bool -s false<br />
<br />
== SSH Keys ==<br />
To add your SSH key:<br />
<br />
$ ssh-add ~/.ssh/id_dsa<br />
Enter passphrase for /home/mith/.ssh/id_dsa:<br />
<br />
To list automatically loaded keys:<br />
<br />
$ ssh-add -L<br />
<br />
To disable all keys;<br />
<br />
$ ssh-add -D<br />
<br />
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!<br />
<br />
== Integration with applications ==<br />
<br />
* [[Firefox#GNOME_integration]]<br />
<br />
== The gnome-keyring dialog does not appear in some terminals when connecting with SSH ==<br />
Solution:<br />
<br />
Run in a terminal, the following:<br />
<br />
gnome-keyring-daemon -s<br />
<br />
Output will get a few lines, but in reality we are interested, {{ic|SSH_AUTH_SOCK}}, example:<br />
<br />
GNOME_KEYRING_C.................<br />
SSH_AUTH_SOCK=/run/user/1000/keyring-XXXXXX/ssh<br />
GPG_AGENT_INF...................<br />
<br />
Now you should add to your {{ic|~/.bashrc}}, according to the output of the previous command, for example:<br />
<br />
SSH_AUTH_SOCK=`netstat -xl | grep -o '/run/user/1000/keyring-.*/ssh$'`<br />
[ -z "$SSH_AUTH_SOCK" ] || export SSH_AUTH_SOCK<br />
<br />
If you run on your terminal the following:<br />
<br />
echo $SSH_AUTH_SOCK<br />
<br />
will return something like the following:<br />
<br />
/run/user/1000/keyring--XXXXXX/ssh<br />
<br />
Now when you connect with ssh, gnome-keyring dialog will launch the "entry of the passphrase"<br />
<br />
== Unlock at Startup ==<br />
GNOME's login manager ({{pkg|gdm}}) will automatically unlock the keyring once you log in; for others it is not so easy.<br />
<br />
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}}.<br />
<br />
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.<br />
<br />
== Useful Tools ==<br />
=== gnome-keyring-query ===<br />
{{AUR|gnome-keyring-query}} from the AUR provides a simple command-line tool for querying passwords from the password store of the GNOME Keyring.</div>L1mpm4rkhttps://wiki.archlinux.org/index.php?title=GNOME/Keyring&diff=220876GNOME/Keyring2012-09-01T00:22:18Z<p>L1mpm4rk: /* The gnome-keyring dialog does not appear in some terminals when connecting with SSH */</p>
<hr />
<div>[[Category:Daemons and system services]]<br />
[[Category:Desktop environments]]<br />
From [https://live.gnome.org/GnomeKeyring/ GnomeKeyring]:<br />
:''GNOME Keyring is a collection of components in GNOME that store secrets, passwords, keys, certificates and make them available to applications.''<br />
<br />
== Manage using GUI ==<br />
pacman -S seahorse<br />
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."<br />
<br />
== Use Without GNOME ==<br />
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:<br />
# Start a D-Bus session<br />
source /etc/X11/xinit/xinitrc.d/30-dbus<br />
# Start GNOME Keyring<br />
eval $(/usr/bin/gnome-keyring-daemon --start --components=gpg,pkcs11,secrets,ssh)<br />
# You probably need to do this too:<br />
export SSH_AUTH_SOCK<br />
export GPG_AGENT_INFO<br />
export GNOME_KEYRING_CONTROL<br />
export GNOME_KEYRING_PID<br />
See {{bug|13986}} for more info.<br />
<br />
On [[Xfce]] you may need to disable {{ic|gpg-agent}}, silently [http://docs.xfce.org/xfce/xfce4-session/advanced loaded at startup] by {{ic|xfce4-session}}, otherwise the above environment variables will be overwritten. Execute the following command, then log out and log in again:<br />
xfconf-query -c xfce4-session -p /startup/ssh-agent/enabled -n -t bool -s false<br />
<br />
== SSH Keys ==<br />
To add your SSH key:<br />
<br />
$ ssh-add ~/.ssh/id_dsa<br />
Enter passphrase for /home/mith/.ssh/id_dsa:<br />
<br />
To list automatically loaded keys:<br />
<br />
$ ssh-add -L<br />
<br />
To disable all keys;<br />
<br />
$ ssh-add -D<br />
<br />
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!<br />
<br />
== Integration with applications ==<br />
<br />
* [[Firefox#GNOME_integration]]<br />
<br />
== The gnome-keyring dialog does not appear in some terminals when connecting with SSH ==<br />
Solution:<br />
<br />
Run in a terminal, the following:<br />
<br />
gnome-keyring-daemon -s<br />
<br />
Output will get a few lines, but in reality we are interested, {{ic|SSH_AUTH_SOCK}}, example:<br />
<br />
GNOME_KEYRING_C.................<br />
SSH_AUTH_SOCK=/run/user/1000/keyring-XXXXXX/ssh<br />
GPG_AGENT_INF...................<br />
<br />
Now you should add to your {{ic|~/.bashrc}}, according to the output of the previous command, for example:<br />
<br />
SSH_AUTH_SOCK=`netstat -xl | grep -o '/run/user/1000/keyring-.*/ssh$'`<br />
[ -z "$SSH_AUTH_SOCK" ] || export SSH_AUTH_SOCK<br />
<br />
If you run on your terminal the following:<br />
<br />
echo $SSH_AUTH_SOCK<br />
<br />
will return something like the following:<br />
<br />
/home/USER/.cache/keyring-XXXXXX/ssh<br />
<br />
Now when you connect with ssh, gnome-keyring dialog will launch the "entry of the passphrase"<br />
<br />
== Unlock at Startup ==<br />
GNOME's login manager ({{pkg|gdm}}) will automatically unlock the keyring once you log in; for others it is not so easy.<br />
<br />
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}}.<br />
<br />
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.<br />
<br />
== Useful Tools ==<br />
=== gnome-keyring-query ===<br />
{{AUR|gnome-keyring-query}} from the AUR provides a simple command-line tool for querying passwords from the password store of the GNOME Keyring.</div>L1mpm4rkhttps://wiki.archlinux.org/index.php?title=GNOME/Keyring&diff=190535GNOME/Keyring2012-03-20T20:52:09Z<p>L1mpm4rk: /* SSH Keys */</p>
<hr />
<div>{{stub}}<br />
[[Category:Daemons_and_system_services (English)]]<br />
[[Category:Desktop environments (English)]]<br />
<br />
The GNOME Keyring stores passwords in an encrypted file that can be accessed by applications.<br />
<br />
== Manage using GUI ==<br />
pacman -S seahorse<br />
It is possible to leave the gnome keyring password blank. In seahorse, 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."<br />
<br />
== Use Without Gnome ==<br />
It is possible to use GNOME Keyring without the rest of the gnome desktop. This can be accomplished by adding to your .xinitrc:<br />
# Start a dbus-session<br />
source /etc/X11/xinit/xinitrc.d/30-dbus<br />
# Start Gnome-Keyring<br />
/usr/bin/gnome-keyring-daemon --start --components=gpg,pkcs11,secrets,ssh<br />
See [https://bugs.archlinux.org/task/13986 Bug #13986] for more info.<br />
<br />
== SSH Keys ==<br />
To add your SSH key:<br />
<br />
$ ssh-add ~/.ssh/id_dsa<br />
Enter passphrase for /home/mith/.ssh/id_dsa:<br />
<br />
To list automatically loaded keys:<br />
<br />
$ ssh-add -L<br />
<br />
To disable all keys;<br />
<br />
$ ssh-add -D<br />
<br />
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 won't need to enter your passphrase again!<br />
<br />
== The gnome-keyring dialog does not appear in some terminals when connecting with SSH ==<br />
Solution:<br />
<br />
Add the following lines to your {{ic|~/.bashrc}}<br />
<br />
SSH_AUTH_SOCK=`netstat -xl | grep -o '/tmp/keyring-.*/ssh$'`<br />
[ -z "$SSH_AUTH_SOCK" ] || export SSH_AUTH_SOCK<br />
<br />
If you run on your terminal the following:<br />
<br />
echo $SSH_AUTH_SOCK<br />
<br />
will return something like the following:<br />
<br />
/tmp/keyring-ABCDEF/ssh<br />
<br />
Now when you connect with ssh, gnome-keyring dialog will launch the "entry of the passphrase"<br />
<br />
== Unlock at Startup ==<br />
GNOME's login manager (gdm) will automatically unlock the keyring once you login, for others it isn't so easy.<br />
<br />
For SLiM, see [[SLiM#SLiM_and_Gnome_Keyring]]</div>L1mpm4rk