| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |
Cc: debathena@mit.edu Message-Id: <5E3FE8A6-B014-4B80-8406-0A460A453A8E@mit.edu> From: Jonathan Reed <jdreed@MIT.EDU> To: Geoffrey Thomas <geofft@mit.edu> In-Reply-To: <alpine.DEB.2.00.0903080824390.6057@geminorum.mit.edu> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v919.2) Date: Sun, 8 Mar 2009 12:34:48 -0400 On Mar 8, 2009, at 8:32 AM, Geoffrey Thomas wrote: > If you try to use SSH on cluster machines, it's the case for many > users [*] that you get an annoying popup asking you to unlock your > keyring (which was created for some other purpose, probably with an > old Kerberos password, and doesn't include any SSH keys). According > to http://live.gnome.org/GnomeKeyring/Ssh , you can disable the > prompt by setting the gconf key /apps/gnome-keyring/daemon- > components/ssh to false. This may affect people who do want to use > an SSH agent, though. If we can figure out the conditions that cause this behavior, documenting it is also an option. We currently have documentation for "This thing is asking for a password and I don't know what it is" (c.f. Firefox), so that's certainly an option. It sounds like it affects a small portion of users anyway... Although I guess I'm not opposed to defaulting the gconf key to "false" and letting users override it if they want (and documenting how to do that and its implications). -Jon
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |