Hi Frank, On Tue, Nov 18, 2008 at 09:11:18PM +0100, Frank Hartmann wrote:
Guido Günther <agx@sigxcpu.org> writes:
On Sun, Nov 16, 2008 at 04:47:54PM +0100, Frank Hartmann wrote:
I am a bit confused by the README.debian documentation, so followed the guideline there verbatim and created two files on my system: Documentation updates to README.Debain are always welcome. -- Guido Hi Guido,
as told I am confused. This is maybe not the right starting point. On the other hand it might show the experts what a normal user of the tool is facing. Thanks for the patch!
[..snip..]
+<uid>admin</uid> has by the magic +of his name administration rights and can do certain action which +normal users can't, right? +<uid>test</uid> is a plain user. +<uid>mercury</uid> a shared resource- in our example a conference room +which can be booked by all members of group <uid>users</uid>. + + +The example configuration in /usr/share/doc/calendarserver/examples/sudoers.plist +achieves the following:
Sudoers can act as (impersonate) other principals as I understand things. So your sudo users can manipulate calendars of other users.
+ +It defines a user 'superuser' which is the big brother of 'admin' and +has god like access rights. 'superuser' normally wears a blue suit +with a big red 'S' in front. + +</BIG GAP: NO IDEA, please fill in> The admin user has DAV:all access so is allowed to "write,read,rm everywhere". Is that correct? Cheers, -- Guido