> It seems then that an installation of Eclipse is by default
> storing individual users information centrally. Where there
> is only a single individual using an installation then no
> problem. However, if Eclipse is installed so that many users
> of a machine share an installation there could in principle
> be problems.
This could be solved (in the future versions of JavaSVN) by including system
user name as part of the key used to cache credentials. Better option is to
start Eclipse with parameter that will point to the keyring file in the
user's home directory not to the central location (which is default).
> Mark pointed me at that location and I found it. It seems to
> be a binary file so I guess there is a tool for managing the
> file somewhere?
Use google :) At least I'm not aware of such tool, but writing a plugin for
managing keyring information is not a complex task, so may be someone
already developed such a plugin.
> I assume IBM or someone has tested using X to run several
> instances of Eclipse on the same machine and so have sorted
> out all the deadlock / livelock issues of using a central
> repository such as the keyring?
Never tried this :) I think it should work as there are no problems with
running two instances of Eclipse with different workspaces (and same
configuration are at ECLIPSE_HOME/configuration, BTW this location also
could be customized with command line Eclipse options).
Alexander Kitaev,
TMate Software,
http://tmate.org/
http://jetbrains.com/tmate/
> -----Original Message-----
> From: Russel Winder [mailto:russel@russel.org.uk]
> Sent: Friday, October 28, 2005 10:05
> To: users@subclipse.tigris.org
> Subject: RE: SSH passphrase
>
> Alex,
>
> On Thu, 2005-10-27 at 22:35 +0200, Alexander Kitaev wrote:
> > Hello Russel,
>
> > To unstore saved credentials you only may delete keyring file. This
> > will also remove all other information saved in the keyring
> file. As
> > far as I know, CVS plugin also uses to store credentials.
>
> OK so deleting the file is the only way but I have to be
> aware of knock-on consequences. Knowledge is power :-)
>
> It seems then that an installation of Eclipse is by default
> storing individual users information centrally. Where there
> is only a single individual using an installation then no
> problem. However, if Eclipse is installed so that many users
> of a machine share an installation there could in principle
> be problems.
>
> Certainly there is "plug-in pollution" (not necessarily bad
> but...) -- because the plug-ins are stored centrally if a
> person updates or installs a new plug-in then everyone gets
> the plug-in and this can (in
> principle) cause problems.
>
> > > 2. Where is the passphrase kept? It used to be in
> > > ~/.subversion/auth/svn.ssh but isn't any longer -- I just need to
> > > check security issues.
> > This location is no longer used when JavaSVN is used within
> Eclipse (e.g.
> > with Subclipse).
> > Default location for keyring file is
> > ECLIPSE_HOME/configuration/org.eclipse.core.runtime/.keyring
>
> Mark pointed me at that location and I found it. It seems to
> be a binary file so I guess there is a tool for managing the
> file somewhere?
>
> > Eclipse supports command line options that allows to
> specify different
> > location for keyring file as well as password to encrypt
> keyring file with.
> > You may find this options and some other information on
> keyring file
> > in built-in Eclipse help.
>
> Mark put me on to those but it was already too late!
>
> I assume IBM or someone has tested using X to run several
> instances of Eclipse on the same machine and so have sorted
> out all the deadlock / livelock issues of using a central
> repository such as the keyring?
>
> --
> Russel.
> ====================================================
> Dr Russel Winder +44 20 7585 2200
> 41 Buckmaster Road +44 7770 465 077
> London SW11 1EN, UK russel@russel.org.uk
>
Received on Sat Oct 29 03:26:33 2005