Re: Subclipse 0.9.33 Released

On Tue, 2005-09-13 at 13:50 -0400, Roberto C. Sanchez wrote:

> ~/.subversion/auth/svn.ssh, causing later attempts without me directly
> entering the passphrase appear to succeed. In fact, it had been using

Case solved.

I had done a grep -r for username and passphrase strings on all the
Eclipse related stores (and found a ~/.eclipse directory that needed
deleting as well). What I had failed to do was recheck ~/.subversion
(which I generally delete from time to time). Lo and behold:

512 elon:~/.subversion/auth
|> tree
.
|-- svn.simple
|-- svn.ssh
| |-- 322e0839a7eec89f6cfbde926de9e045
| `-- 798bbf8d4a3c08d2ea65f0f6141699b3
|-- svn.ssl.server
`-- svn.username

one of these is 3 months old the other 3 days, both contain username and
passphrase data in plain text and they contain the location of the key
file.

So clearly these files must be being consulted for the passphrase. So
why aren't they consulted for the key file? Clearly they used to be but
now they are not. Presumably this ~/.subversion directory is managed by
Subclipse not by Subversion.

I also assume that if I delete them then I will have to give all
parameters to the eclipse command which is sort of OK for me but, as
Roberto said earlier, on a multi-use machine histories then contain the
plain passphrase so it is much better for Subclipse to enter into a
dialogue to get username and passphrase.

I also think that these files should not be created or if they must the
passphrase needs encoding and it would be good if the files got deleted
at the end of the session to which they relate.

Phew. Glad I understand that one. Sorry I led people up the garden
path

-- 
Russel.
====================================================
Dr Russel Winder                +44 20 7585 2200
41 Buckmaster Road              +44 7770 465 077
London SW11 1EN, UK             russel@russel.org.uk