[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [PATCH] [gnome-keyring] Miscellaneous improvements

From: John Peacock <john.peacock_at_havurah-software.org>
Date: Tue, 06 May 2008 07:05:22 -0400

Martin Furter wrote:
> When logged in over SSH the popup window will be on the wrong machine maybe
> miles away. It must be possible to disable this feature.

You do know that ssh has this neat feature enabled by the -X option, where all X
windows show up on the local machine not the remote machine, right? ;-)

Or are you saying that the gnome-keyring feature itself needs to be disable-able
because someone might be logging in from a non X workstation that can't handle
the graphical interface that the remote box might otherwise employ. In that
case, +1 from me. There has to be a fallback or workaround if the terminal
capabilities don't support the GUI.

I know the whole idea behind implementing this feature is to provide a higher
security password mechanism by default (like Windoz and OSX already have), but
those are both niche(!) platforms with existing O/S support already provided.
For the dominant platform, this is going to be a *large* change from existing
behavior. ;-)

It also occurred to me now that this feature is going to make the package
maintainers crazy, because now they have to have a svn-with-gnomekeyring and
svn-without-gnomekeyring packages, that will necessarily conflict with each
other. Could this possibly be implemented as a module so that the core only has
the necessary hooks and the plugin has the actual keymanager support? Then it
becomes package/subpackage and it won't require much duplicated effort. Having
this feature be predicated by a compile-time option is a bad design choice,


To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-05-06 13:05:52 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.