Dear List, All of the remote ssh commands that I execute (pull/push/sync/clone) try to run as the user "nobody". This is a big problem, because I need to make sure that other users on my machine cannot login to the web interface, (eg. I want "nobody" and "anonymous" to have no capabilities) and I want to use my named username of "beyert".
After performing the clone over sshfs, which works fine (although sshfs gives database errors for pull/push/sync), I set the remote-url command as follows: ssh://beyert@[my-domain]:[my-port]//the/remote/path/scripts.fossil I have tried every variation of the password notation that I know of, namely: ssh://beyert@[my-domain]:[my-port]//the/remote/path/scripts.fossil ssh://beyert:*@[my-domain]:[my-port]//the/remote/path/scripts.fossil ssh://beyert:[my-password]@[my-domain]:[my-port]//the/remote/path/scripts.fossil With my secure settings for "nobody" with no capabilities, I get the following error: "Error: not authorized to read" I only was able to get the pull/push/sync to work once I gave "nobody" "gio" capabilities, which allowed other users on my machine to see the repository. When I looked at the usage logs, that sync operation was recorded as belonging to user "nobody", whereas all of my other repository commands belong to "beyert". I don't understand why it isn't using the user "beyert", which has "s" capabilities? I also tried setting the environment variable REMOTE_USER to "beyert", which didn't help. On both sides, the command "fossil user default" gives "beyert", and my UNIX user on both machines is "beyert". I'm using FreeBSD 9.0-RELEASE on both machines, with a snapshot from 2012-03-17. Should I use a newer snapshot? Regards, Tim _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
