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

Re: svn client & smartcard certificates

From: Joe Orton <jorton_at_redhat.com>
Date: Fri, 18 Apr 2008 15:26:29 +0100

On Fri, Apr 18, 2008 at 10:17:48AM -0400, Van Deman, Quint CTR US USJFCOM J7 wrote:
> Joe--
>
> That patch works great for checkouts,

Excellent!

I noticed you had to manually verify the server cert. Are the set of
trusted CA roots from the DoD PKI shipped on the CAC cards? I have
wondered about having neon/SVN automatically trust any certs marked as
trusted on the token.

> but commits give the following: svn:
> 'https://jtsd-svn.att.jfcom.mil/repos/JATTL/testproject' is a URL, but
> URLs cannot be commit targets
...
> [jattl_at_jtsd-svn testproject1]$ svn commit -m "CAC test"
> https://jtsd-svn.att.jfcom.mil/repos/JATTL/testproject testproject1

> svn: 'https://jtsd-svn.att.jfcom.mil/repos/JATTL/testproject' is a URL, but URLs cannot be commit targets

You don't need to specify the URL when committing; the repository
location is stored in the working copy metadata. Just run:

 $ svn commit -m "CAC test"

Regards,

joe

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-04-18 16:27:06 CEST

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

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