On Mon, Jul 01, 2013 at 12:42:11AM -0600, Andy Bradford wrote: > Thus said Rene on Sun, 30 Jun 2013 16:07:44 +0200: > > > It could be an alternative way. But the urlShell seems to be much > > easier! > > Thanks, I actually looked at urlShell, but it didn't seem right, or was > confusing, or both. >
<snip> > > Now, on to the snag... I can open the cloned repository and commit > changes, but autosync failes due to authorization problems. I'm not > really sure why this doesn't work (the changes I've made are fairly > trivial and I fail to see how they even affect authorization): > > $ f op test.fossil > file > ... > $ f ci -m new > Autosync: ssh://amb@localhost//tmp/test.fossil > ssh -e none -T amb@localhost fossil http /tmp/test.fossil > Round-trips: 1 Artifacts sent: 0 received: 0 > Pull finished with 292 bytes sent, 433 bytes received > New_Version: 7934407cf95c5936eb460a5ce3d166123dbcbdc7 > Autosync: ssh://amb@localhost//tmp/test.fossil > ssh -e none -T amb@localhost fossil http /tmp/test.fossil > Round-trips: 1 Artifacts sent: 2 received: 0 > Error: not authorized to write > Round-trips: 1 Artifacts sent: 2 received: 0 > Sync finished with 633 bytes sent, 465 bytes received > Autosync failed > > > I don't understand why it thinks my user account is not authorized to > write. It has read/write access to the file. Is there something else > that is missing? > > Any pointers? Have you try with server running more recent version ? I remember there was a patch somewhere between version 1.24 and 1.25 that was forcing full right when syncing using ssh://. > > A patch follows with the changes I've made (needs a little clean up in > actually outputting the newly added options in usage statements): > <snip> Nice.. have you send your Contributor aggreement to Mr. Hipp ? http://www.fossil-scm.org/xfer/doc/trunk/www/contribute.wiki I'm very interested to see this kind of security enforcement for the ssh protocol.. With this patch, we can have fossil access via ssh without having full shell access to the server.. Eventually, sync permission could be honor as for http:// since accessing the repo via ssh would not mean anymore to have direct access to the .fossil file. Regards, -- Martin G. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
