"Alexander Kitaev" <firstname.lastname@example.org> wrote on 09/14/2005 09:25:31 AM:
> > JavaSVN should not cache information in that location unless
> > you check the Save Password checkbox on a prompt. In your
> > case, passing it on the command line should not cache it
> > elsewhere. If it does, you should report it to JavaSVN.
> That is not the case for private key with the current version of
> JavaSVN(+Subclipse) key path and passphrase, once defined in the system
> property or [tunnels] section of config file will be cached, and there
> prompt currently that may let user not to cache this information.
Given that the info you are putting in the cache is only used by JavaSVN,
why not use the encryption tools in Java to encrypt the information in the
cache, like Subversion does with WinCrypt?
Also, you mentioned that Subclipse encrypts its cached info stored in
Eclipse. To my knowledge that is not true. It might be obfuscated by
Eclipse but I do not believe we are explicitly adding our own encryption.
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
Received on Thu Sep 15 01:21:54 2005