[Bug 172] Add multiple AuthorizedKeyFiles options

[bugzilla-daemon at mindrot.org]

http://bugzilla.mindrot.org/show_bug.cgi?id=172





------- Additional Comments From alex.kiernan at thus.net  2002-04-10 05:00 -------
> ------- Additional Comments From mouring at eviladmin.org  2002-04-06 08:08
> -------
> I would perfer not myself.  The reason why we went down to ONE authorization
> 
> file was to simplify management.  Allowing multiple key locations is
> asking for trouble.

If this were the default behaviour, I'd agree. It's not. It can be turned on 
only by deliberate administrator action.

We automatically distribute the /var/db/keys-distributed-by-security-team/%u 
section (and have other evil hacks that allow keys in this location to be 
owned by a special user - those hacks aren't in the patch).

This preserves the principal of least astonishment by seperating out the keys 
that the security team modify (and potentially clobber) from the keys that the 
users expect to have control over.

> How do you handle the case where you have two alike authorization entries
> with 
> conflicting key options (command=,environment=,etc)?  Which one takes 
> priority?  First come first serve?  

There's already that possibility today - you can have multiple keys which can 
match in a single file, the first match is the one that gets used.

> No, you should have one spot only.

Agreed you should have only one by default, but I don't think the flexibility 
loses you anything.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.