On Mon, Aug 5, 2013 at 7:11 PM, Matt Welland <[email protected]> wrote:
> Unfortunately even though I'm very interested I haven't had time to look > closely at this new ssh approach. Is the following use case possible to > implemen with your code? I ask because I hear some emphasis on the > many-to-one mapping and I'm interested in one-to-one mapping. > > Each person given access registers their public key (maybe an > administrator checks them in to an admin fossil similar to how gitolite > works) . Users do not have a fossil password (but they are registered with > the fossil). This might use or be similar to the CGI REMOTE_USER variable > workings. > > Once I have my ssh key entered I should be able to do all operations > (clone, sync, commit etc.) without entering my password but the remote > fossil knows who I am. > > That's the way it used to work. I think Andy's changes "fix" it so that it doesn't work that way any more. I'm disappointed too, and would like to find a solution that works both ways. -- D. Richard Hipp [email protected]
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
