-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Ryan Schmidt wrote:
>> When there is no need for the strong encryption SSH provides, why then
>> burden the server with the extra load?
>
> Because, aside from the benefit of ssh encryption, or the drawback of
> extra cpu cycles, depending on how you see it, svn+ssh also provides the
> feature you asked for: authentication via system user accounts.
That's why I used it that way, at least up to now.
Does svnserve just assume the current system user is authenticated when
it is called with the -t option?
>> Since the repository is used only in the intranet (or from outside
>> through VPN), the Apache solution is not really interesting for me.
>
> We use Apache to serve our repository which is only usually accessed
> internally within our company. Why do you think this configuration isn't
> relevant? We find it very handy to be able to set up Apache to
> authenticate to our LDAP server, which is the same LDAP server we use
> within the base OS for user account authentication. And our
> administrators already know how to administer an Apache server. I'm sure
> we also could have used the svn+ssh setup but since we're a web
> development shop the Apache solution was the most natural for us.
Ok, sounds really handy indeed. Nevertheless I have neither an LDAP
server for authentication, nor an Apache server running so far. So for
me, the straight-forward solution is the one with svnserve (resp.
svnserve/SSH).
Best regards,
Florian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFEEJBITSAdWevar50RAjOeAJ94CPA6MugDcH5lFlJxt8Dd7XUsRgCfRPke
XiE+gO/HPbImqpB/fjdR2Bk=
=Pxzc
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Mar 9 21:34:35 2006