On Sun, Jul 21, 2013 at 10:09 PM, Andy Bradford < amb-sendok-1377061791.goefgfndahogdhegp...@bradfords.org> wrote:
> Notice that I'm able to access multiple fossil files with my SSH key and > Fossil account. And, I can install as many SSH keys into the ``guest'' > account as I like. > > > > This is a many-to-many with access controlled by scripts/lookup tables > > at the fossilscm account end. > > So, I can do many-to-many now, what's lacking perhaps is lookup tables. > > > Administration consists of: > > > > 1. Adding public key/user name combinations > > 2. Added users to the access lists > > Here is where I'm confused. Does this mean that an SSH key identifies > the user both to Unix and to Fossil? > > As for the access list, I assume you mean a mapping of which fossils a > given SSH key can actually request? > Yes, lookup tables and scripting would be required and that is definitely outside the scope of fossil itself. The ssh key is being used to give access only to the fossil file and yes, the access list would map ssh keys (thus users) to fossils. -- Matt -=- 90% of the nations wealth is held by 2% of the people. Bummer to be in the majority...
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
