No problem.
Would anyone be traumatized if I worked on a patch to ra_svn to allow
user-defined additional command line options to the svn-tunnel-agent as
used in ra_svn_open? I can coax plink/putty to fudge my user name with a
session (which is not the same between the two machines), but openssh in
cygwin requires "-l username" on the command line.
> seanc@dimensionalrift.com writes:
>
>> > seanc@dimensionalrift.com wrote:
>> >
>> >>I would be willing to go with the ra_svn approach but it doesnt seem
>> >>possible to secure it in a meaningful manner for a multi-user
>> >>configuration. Perhaps if svnserve were to run exclusively on
>> 127.0.0.1
>> >>and a proxy program (say, svnproxy) could be executed via rsh or plink
>> >>from my clients I could at least secure it in the same way as CVS.
>> >>
>> >
>> > uh, you can already tunnel ra_svn over ssh, just as one normally does
>> > with CVS. there's no reason to run svnserve in daemon mode if you
>> don't
>> > want to.
>> >
>>
>> This was not obvious at all from the documentation.
>
> Errr...that's my fault.
>
> I accidentally blew away Ben's documentation (and coincidentally,
> that's what I'm working on fixing right now).
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Feb 26 08:41:09 2003