On Fri, Aug 8, 2014 at 4:40 PM, Jeff Fisher <[email protected]> wrote: > Maybe you could setup 'sudo' to do this? sudo would let the user run > a command as another user, and lets you specify the arguments that can > or cannot be used with the command. It's also easy to write a wrapper > script to do the function you want and give sudo access to this > script.
Thank for your suggestion. Actually, my scripts have to work in 2 platforms AIX et Linux, and those users don't have any special access rights. Truc On Fri, Aug 8, 2014 at 4:40 PM, Jeff Fisher <[email protected]> wrote: > Hello, > > On Thu, Aug 07, 2014 at 12:52:48AM +0200, Sieu Truc wrote: > > I know well your advices , but actually i need to assign 3 users to > > handle the keyring. One like admin , he can modify and add the > > secret key Another like test1 , he cannot add secret key but he can > > add public keys And the third callled test2 , he cannot add any key > > but can use that keyring for do a securisation or desecurisation. > > Maybe you could setup 'sudo' to do this? sudo would let the user run > a command as another user, and lets you specify the arguments that can > or cannot be used with the command. It's also easy to write a wrapper > script to do the function you want and give sudo access to this > script. > > This way, you do not need to change the permissions on any of the > files; they would only be owned by the 'admin' user, and in addition > you can be more specific in specifying what the other users are able > to do. > > Best Regards, > Jeff >
_______________________________________________ Gnupg-users mailing list [email protected] http://lists.gnupg.org/mailman/listinfo/gnupg-users
