What about setting up a persistent connection using ControlMaster/ControlPath/ControlPersist (man ssh_config) and reusing it for the multiple commands needed?
On Wed, Feb 16, 2011 at 1:08 PM, Richard Hipp <d...@sqlite.org> wrote: > > > On Wed, Feb 16, 2011 at 1:06 PM, Joerg Sonnenberger < > jo...@britannica.bec.de> wrote: > >> On Wed, Feb 16, 2011 at 12:25:11PM -0500, Richard Hipp wrote: >> > If any reader has suggestions on a better way to do SSH access for >> Fossil, >> > please speak up. >> >> The correct way is to use ssh -T and a single instance on the other >> side. This doesn't currently work since the HTTP processing is >> fire-and-exit. A trivial hack would be to use a new ssh session >> for each roundtrip, but that's of course not a long term option. >> > > A new ssh for each roundtrip also means the user has to reenter their > password (if using password authentication) for each roundtrip,. > > >> >> Joerg >> _______________________________________________ >> fossil-users mailing list >> fossil-users@lists.fossil-scm.org >> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users >> > > > > -- > D. Richard Hipp > d...@sqlite.org > > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > > -- Justin Mazzi
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
