I'm looking for the web page / archived email thread / source file / person who could clear this up.
>From what I can piece together the ssh transport, at a minimum, can be used to >substitute a regular sshd setup for a http/https server in the role of a >*transport*. For instance: thomas@netbook:~$ ssh 127.0.0.1 Linux netbook 2.6.32-5-686 #1 SMP Sun May 6 04:01:19 UTC 2012 i686 ... Last login: Sat Oct 6 12:42:43 2012 from localhost thomas@netbook:~$ logout Connection to 127.0.0.1 closed. thomas@netbook:~$ mkdir fossil-test thomas@netbook:~$ cd fossil-test/ thomas@netbook:~/fossil-test$ fossil init test.fossil project-id: 552443d800c3b059410a94af195981035f001bdb server-id: d3116e43357b61e4f51e88b2622087c88416cc74 admin-user: thomas (initial password is "a7ed20") thomas@netbook:~/fossil-test$ fossil clone ssh://thomas@127.0.0.1/home/thomas/fossil-test/test.fossil test-cloned.fossil password for thomas: ssh -e none -T thomas@127.0.0.1 fossil: ssh connection failed: ... thomas@netbook:~/fossil-test$ Is there also a technique to then tell the instance of fossil on the server to use some arbitrary internal fossil user for the connection regardless of passwords? Similar to a "fossil ui" in the sense that "administrative ownership" of the database is ultimately enforced by file permissions / host environment. and yes clearly this would be the same level of security as a single shared user. although that bridge is already crossed by giving access to a shell account with write permission anyway. www.thomasstover.com _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
