[scponly] scponly svn (subversion) support

[Kaleb Pederson]

I think you are right.  I'm planning on going that way, so if nobody gets 
around to doing it in the next couple of weeks, I might work on it.

I would actually do something slightly different... I would have them issue 
something like the following:

ssh user at host svn update https://myhost/svn/repos/

But, I'm not sure exactly how that will work when the checkouts are in 
numerous locations within their allowed hierarchy?

Perhaps there is an established process?  It's kind of interesting because, at 
least in my case, they can't change directories or use anything but sftp (and 
eventually svn).

--Kaleb

On Thursday 31 March 2005 12:01 pm, Mike Schroll wrote:
> scponly's svn support seems to permit access to svn, but not svnserve,
> which as far as I can tell, is the process used when you access a svn
> repos in the form: svn+ssh://user@host/path/to/repos
>
> debug 9 output:
>
> [70160]: 3 arguments in total.
> [70160]:        arg 0 is scponly
> [70160]:        arg 1 is -c
> [70160]:        arg 2 is svnserve -t
> [70160]: opened log at LOG_AUTHPRIV, opts 0x00000029
> [70160]: retrieved home directory of "/home/lxsvn" for user "lxsvn"
> [70160]: setting uid to 1005
> [70160]: processing request: "svnserve -t"
> [70160]: denied request: svnserve -t [username: lxsvn(1005), IP/port:
> 69.9.186.70 50037 22]
> svn: Connection closed unexpectedly
>
>
> Did subversion change? or am I not using svn correctly?
>
> Thanks
> -Mike Schroll
>
> Applied Networking System Administration Major
> Rochester Institute of Technology
> Rochester, NY
>
> Information Sciences and Technology Major
> Penn State University
> University Park, PA
>
> Czar of Technology
> Internet Marketing Center of Canada, Inc (IMCC.ca)
>
> scponly at LogicX.us
> http://MSchroll.com
>
> _______________________________________________
> scponly mailing list
> scponly at lists.ccs.neu.edu
> https://lists.ccs.neu.edu/bin/listinfo/scponly