This is the mail archive of the
mailing list for the Cygwin project.
Re: Subversion https access
- From: David Rothenberger <daveroth at acm dot org>
- To: cygwin at cygwin dot com
- Date: Fri, 18 Sep 2009 08:08:14 -0700
- Subject: Re: Subversion https access
- References: <5FA355C2B0004D36BC879A369D21BBC2@phoenix>
- Reply-to: cygwin at cygwin dot com
On 9/18/2009 7:40 AM, Jason Pyeron wrote:
I have two machines on my desk. One performs fine, the other gets SSL errors
while trying to connect.
The files under /cygwin on both machines are the same. Attached are both
cygchecks. DDCRDR003646 is the working machine.
$ svn co https://XXXXXXXXXXXXX/YYYYYYYYYYYYYYYYYY
svn: OPTIONS of 'https://XXXXXXXXXXXXX/YYYYYYYYYYYYYYYYYY': SSL negotiation
failed: SSL error: unknown protocol (https://XXXXXXXXXXXXX)
Any ideas on what should my next debugging step be?
svn is working fine here against Apache2 running SSH. This looks to me
like a problem with the server, not the client. My suggestions for
1. Hit the URL with your web browser and check if it works.
2. Try another, Windows-based client (e.g., TortoiseSVN) to
see if that works.
3. Try switching to serf using this switch to svn:
If those ideas don't help, there are these shots in the dark:
1. Switch your HOME directory to a path without a space.
2. Remove (or move) ~/.subversion
David Rothenberger ---- email@example.com
Those who do not understand Unix are condemned to reinvent it, poorly.
-- Henry Spencer, University of Toronto Unix hack
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple