Thus said "Andy Bradford" on 29 Jun 2013 18:19:48 -0600: > As can be seen, when my SSH key is used, it will be forced into fossil > http mode, but the client crashes.
I just found the following: http://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg02963.html I don't know what ever became of it---I see no suggestions. I think it would be sufficient for the local fossil client to simply setup the SSH session so that the remote side of the SSH session is just ``fossil http REPOSITORY'' This is similar to how scp works. When you do: scp file remote:/path, the scp client establishes an SSH connection and then runs a remote scp command (in server mode). The scp local command then works in ``client'' mode and talks SCP to the remote scp instance. All of this happens over SSH. For fossil, when the URL is ssh://user@remote//path, it would simply open up a remote ``fossil http /path'' on the remote host and then the local fossil command would switch to ``client'' mode and talk to the SSH connection file descriptors as if it were talking HTTP. As can be seen, the server side is ready and willing: $ ssh amb@localhost GET / HTTP/1.1 Host: localhost HTTP/1.0 302 Moved Temporarily Date: Sun, 30 Jun 2013 00:54:48 GMT Connection: close Location: http://localhost/index X-Frame-Options: SAMEORIGIN Cache-control: no-cache Content-Type: text/html; charset=utf-8 Content-Length: 69 <html> <p>Redirect to Location: http://localhost/index </p> </html> Connection to localhost closed. Perhaps the fossil client wouldn't work using this method, but this is fairly common with most commands that support a remote execution method (one side switches to client, and remote is executed as server and they just talk over the SSH tunnel). Andy -- TAI64 timestamp: 4000000051cf829b _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
