Mark Shellenbaum wrote:
Can you give us an example of a 'file' the ssh-agent wishes to open and what the permission are on the file and also what privileges the ssh-agent has, and what the expected results are.
The whole point is that ssh-agent should NEVER be opening any files that the user it runs as owns after its initial startup. It may due to library implementation details need to open world readable system files (such as /etc/default/nss as an implementation detail of parts of the nsswitch).
You need to be very careful about changing the rules for access control, since you may end up breaking POSIX compliance.
basic privileges already has this potential. It is okay here because the application is explicitly requesting this behaviour. An application that only calls POSIX APIs would not be impacted by these new basic privileges (unless it was purposely started from an environment with them removed from the limit set).
-- Darren J Moffat _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
