Application example: Shared hosting of a cvs repository. In http://www.cvshome.org/docs/ddSSHGuideCygwin.html, there is a good description, how to tunnel in general, but this requires a shell on the server-side. For security reasons, hosting providers who are willing to run a cvs for you may well not like you having full shell access on a shared server and thus don't like that. I have heard that there are approaches to do without a full shell? Or maybe as an additional question to: http://www.openssh.org/faq.html ?
Created attachment 213 [details] scvs - a perl script Server-side installation steps as per steiner@acm.org: (1) create one (UNIX) login account with zzh as its login shell. (2) install the ssh public-keys for all CVS users of this account in .ssh (or .ssh2, depending on the ssh implementation) (3) in CVSROOT/passwd create aliases for the (CVS) accounts mapped on the UNIX account created in (1). --- second attachment also needed.
Created attachment 214 [details] zzh.c - a minimum server-side shell by symlinking ~/bin/cvs ~/bin/scvs it also works in emacs (PCL-CVS)
Could perhaps also be done with rsync (win BAT file): http://bugzilla.privasphere.com/attachment.cgi?id=3&action=view Hopefully, such documentation will also go into cvshome! (see http://ccvs.cvshome.org/issues/show_bug.cgi?id=93)
i don't think this belongs to openssh perhaps you can send a patch for the faq?
I am fine if you rather put it into http://www.openssh.org/faq.html than http://www.openssh.org/manual.html. i) Should the patch be on plain HTML or do you have some more sophisticated format I have to work on (e.g. xml?) ii) (since you are covering both the openssh and the openbsd site) is there maybe yet a better place on the openbsd website? Eg close to the paper reference by David in http://bugzilla.mozilla.org/show_bug.cgi?id=58251#c9 ?
closing: This documentaion is more closely related to CVS than SSH. It would probably be better documented in a HOWTO on some website (e.g. cvshome.org) than sitting here in our bug tracking system as an open bug.
Change all RESOLVED bug to CLOSED with the exception of the ones fixed post-4.4.