Re: Only two Windows binary distribution support SASL encryption?

2010-11-06 Thread John Alan Belli
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Fri, 5 Nov 2010 16:59:12 -0400, Mark said:
 
 When I have tested the CollabNet binaries in the past they
 supported this fine.  The Cyrus SASL stuff requires registry
 entries to work properly.  If you are trying all of these
 from the same workstation are  you checking those entries?
 
OK. Now that you reminded me, I went and put the registry entry
in. I had forgotten that the client required it since installing
1.5. I had to reinstall Windows on my workstation a while back,
and haven't used the command line client since then.
  
With the registry entry in the proper place, the Win32Svn works
as well. Slik at least doesn't seem to even check for it,
apparently just using the directory the binary is in.
  
Perhaps this should be noted in the Book somewhere, that the
SearchPath entry may need to be on the clients, as well? Also, on
x64 versions of windows, a 32-bit client needs the entry under
 Wow6432Node.
 
 
 JAB
- -- 
John Alan Belli  jabe...@pobox.com   http:// coming soon
(_...@___#PGP DH/DSS Key ID: 0x9F9A5233  RSA Key ID: 0xFD7399CD
U/~   O-   Available by finger and on various keyservers
 
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.12 (MingW32) - WinPT 1.4.2
Charset: UTF-8

iEYEARECAAYFAkzWMUEACgkQ2IsOhZ+aUjOvtQCg+O/G3NniP6uJqk1sakpK6/is
TAoAn25BWG18KKJRvsIeC5fnnVpjQeYz
=bKtD
-END PGP SIGNATURE-


Only two Windows binary distribution support SASL encryption?

2010-11-05 Thread John Alan Belli
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

I have the Win 2003 server set up with SASL and encryption, as
stated earlier this week. 
 
The relevant portion of svnserve.conf:
 [sasl]
use-sasl = true
min-encryption = 128
max-encryption = 256
  
and svn.conf:
pwcheck_method: auxprop
auxprop_plugin: sasldb
mech_list: DIGEST-MD5
sasldb_path: C:\Subversion\conf\sasldb
 
I tried all the Windows binaries on the binaries download page.
Only SlikSVN and WANdisco are able to talk to the repository. All
other fail with svn: Cannot negotiate authentication mechanism
 
 
 JAB
- -- 
John Alan Belli  jabe...@pobox.com   http:// coming soon
(_...@___#PGP DH/DSS Key ID: 0x9F9A5233  RSA Key ID: 0xFD7399CD
U/~   O-   Available by finger and on various keyservers
 
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.12 (MingW32) - WinPT 1.4.2
Charset: UTF-8

iEYEARECAAYFAkzUZ60ACgkQ2IsOhZ+aUjPytgCg23vT0IeZf/faepHaltdP7Uxa
BWEAoJz3/TUyINwgpoLYGLwtkhR1jx28
=xTV3
-END PGP SIGNATURE-


Re: Windows client and SASL

2010-11-03 Thread John Alan Belli
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Tue, 02 Nov 2010 15:31:03 -0400, I said:
 
 TortoiseSVN has no problem operating on this repository, so
 either there's a bug in the binary, or, more likely, I haven't
 configured something in the command-line environment.
 
Nope, there's a problem with the binary. I downloaded the Slik
binary and it works fine. I have also left a message on
alagazam.net to this effect.
 
 
 JAB
- -- 
John Alan Belli  jabe...@pobox.com   http:// coming soon
(_...@___#PGP DH/DSS Key ID: 0x9F9A5233  RSA Key ID: 0xFD7399CD
U/~   O-   Available by finger and on various keyservers
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.12 (MingW32) - WinPT 1.4.2
Charset: UTF-8

iEYEARECAAYFAkzSL/UACgkQ2IsOhZ+aUjNY8gCg9NJ2svx5kE5IROJVOpicQphK
s8YAoLBdhwBgq604CNUBKl3XK/xmyjl5
=MnlA
-END PGP SIGNATURE-