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

Client certificates - JavaHL not prompting for file/password?

From: Brian Clarke <brian_p_clarke_at_yahoo.com>
Date: 2005-07-21 17:42:03 CEST

For background, I posted the following to the
Subclipse users list and was redirected here after
discussion - I'd appreciate any help:

From what I gathered on the Subclipse list, it appears
that JavaHL isn't using the prompting mechanisms for
client certificates and passwords when used with

If I add both the ssl-client-cert-file and the
ssl-client-cert-password (plaintext) to the Subversion
'servers' file, both the 'svn' command-line client and
Subclipse succeed in connecting to the repository.
Unfortunately, having the plaintext password on disk
is likely to be unacceptable.

If I leave the ssl-client-cert-password out: a) the
svn command-line client prompts for the password and
then succeeds in connecting to the repository, while
b) Subclipse (Eclipse SVN Repository Perspective->New
Repository Location...) doesn't prompt for a password
and fails.

In addition, if I leave both
ssl-client-cert-{file,password} out of the servers
config, the svn client prompts for both the
certificate filename and the password, and succeeds.
Subclipse doesn't prompt for either, and fails.

Can anyone provide some input to resolve this
situation? Is this a JavaHL issue?

[It'd be fine to configure the client cert file
location and have Subclipse prompt the user for the
password (say once per Eclipse dev "session").]


Start your day with Yahoo! - make it your home page

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jul 21 17:42:58 2005

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.