Re: Only two Windows binary distribution support SASL encryption?
Hi Glad you got it working and thank God it's not my build that has an error. I tried most of this saturday to get SASL to work with it. First using TortoiseSVN as client. But didn't got the configuration right. Maybe you, now you have your configuration experience fresh in mind, could write some clarifications for the SVN-book page http://svnbook.red-bean.com/nightly/en/svn.serverconfig.svnserve.html#svn.serverconfig.svnserve.sasl or just send some description to this list of your setup (with config files, registry dumps etc.) I think that should help many people out there (or is it here? :-) //David On 2010-11-07 05:56, John Alan Belli wrote: -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-
Re: Only two Windows binary distribution support SASL encryption?
-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?
-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: Only two Windows binary distribution support SASL encryption?
That seems like reasonable information to add to the download page. John Alan Belli wrote on Fri, Nov 05, 2010 at 16:23:51 -0400: -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: Only two Windows binary distribution support SASL encryption?
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 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? I know I have Subclipse users that use SASL via installing those binaries. I do not know which options they use. In general, I think it was a mistake that we ever allowed the SASL stuff into our code base. The required dependencies are poorly documented which just makes SVN look bad and it does not accomplish the main goal virtually every user wanted, which was to connect to Active Directory. IMO, Apache server is still the best way to go. -- Thanks Mark Phippard http://markphip.blogspot.com/
