Thus said Abilio Marques on Sat, 16 Aug 2014 12:14:09 -0430: > amarques@laptop-01 ~/tmp/resume $ fossil clone > ssh://abiliojr@raspberry1/.fossilrepos/resume.fossil > .resume.fossil > abiliojr@raspberry1's password: > Round-trips: 2 Artifacts sent: 0 received: 0 > Error: not authorized to clone > Round-trips: 2 Artifacts sent: 0 received: 0 > Clone finished with 569 bytes sent, 564 bytes received > server returned an error - clone aborted
Just as a quick follow-up to finish out this thread. Abilio and I diagnosed this off-list and it turns out that this particular fossil had localauth=1 in the config. Having localauth=1 means that all syncs will require Fossil authorization and SSH currently cannot provide Fossil username/password except via REMOTE_USER environment variable (without the password), so he disabled it. One can certainly enable localauth=1 and have remote_user_ok=1 which would then allow the SSH client to authenticate via the REMOTE_USER environment variable, but this would require using SSH keys to force the REMOTE_USER to some value: For example, in ~/.ssh/ authorized_keys: command="env REMOTE_USER=abiliojr bin/fossil http /tmp/resume.fossil" ssh-rsa ... Andy -- TAI64 timestamp: 4000000053f41dfc _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
