Thus said Chad Perrin on Sun, 11 Aug 2013 10:10:40 -0600: > On Sun, Aug 11, 2013 at 03:24:40PM +0200, Rene wrote: > > On 2013-08-11 14:49, Chad Perrin wrote: > > > > > > Err . . . wait. Is it not logging the *user*, or just the IP > > > address? What would it log in place of the actual authenticated > > > Fossil user account that initiated the sync? > > > > The user in the current ssh functionality is not authenticated > > against fossil. > > Ah, okay. I thought you meant the Fossil user account for a moment > there.
What he meant was this..., when you do the following: fossil clone ssh://chad@freebsdhost/fossils/project.fossil project.fossil There is no Fossil authentication that happens in this interaction. It is presumed that because you have SSH access to the file, that you also have Fossil access to the file. So the only entry that will show up in the log for chad is chad. This is fine, and it will probably even work if you want to give out an SSH account for each user that you want to access the fossil as long as the permissions on the fossils are correctly setup for Unix groups. But if you want to have a single SSH account under which to aggregate the fossils, then you won't be able to do it yet, because all access to the fossils would appear to be logged in from the exact same user. All that being said, this is not how you are currently planning on setting up. There, you are simply using SSH as a tunnel/proxy to get you to the Fossil daemon listening on port 8888. Then you do: fossil clone http://chad@localhost:4444/project project.fossil And it will prompt you for Fossil user chad's credentials because it is not using SSH as the transport per se. Hopefully that clarifies. Andy -- TAI64 timestamp: 400000005207fb33 _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
