emacs-wiki-discuss
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[emacs-wiki-discuss] Re: planner-authz ideas and questions


From: Andrew J. Korty
Subject: [emacs-wiki-discuss] Re: planner-authz ideas and questions
Date: Sat, 26 Mar 2005 11:07:08 -0500
User-agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21 (darwin)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dryice Liu <address@hidden> writes:

> I'm planning on publishing my planner pages and utilize planner-authz
> to protect my privacy. It's not easy to get started for a Perl and
> Mason newbie like me, but it worth all the trouble. However I'm still
> miss some features and as a planner-authz newbie I would ask first to
> see if this is already available:
>
> A "#authz" directive that opens the project to everyone. I want to
> protect most of my pages so I have `planner-authz-project-default'
> set. And this makes anonymous users (without a user id) can't access
> any page. Is there some thing like a "#authz all" or "#authz nil" that
> opens the page to everyone?

Dryice and I have discussed this off-list.  My current technique (and
Dryice independently came to the same conclusion) is to set what you
want to be your default authorization list in
planner-plan-page-template.  So I have something like

,----
| (setq planner-plan-page-template
|       "#authz ajk boss_of_ajk\n\n* Tasks\n\n\n\n* Notes\n\n\n")
`----

> Access control based on section name. I have some extra sections
> except for tasks, notes, and appt. And I'm missing something like
> (("SectionA" . ("user1" "user2"))
> ("sectionB" . ("user3" "user4"))
> ("sectionC" . all))
> One way to do this is to surround the section with <authz> tag before
> planner-authz do the real work and remove them when the work is done
> :)
>
> I'm using planner-trunk and for some subsections all the content are
> hidden and only the subsection title is left. This is not a big issue,
> though :)

Dryice has sent me some code and ideas on the subject and I will
working on merging them in to my code base.  I'll then submit the
changes to Sacha.

- -- 
Andrew J. Korty, Chief Security Engineer, GCIA, GCFA
Office of the Vice President for Information Technology
Indiana University
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (Darwin)

iD8DBQFCRYis8gM8+Mr5peERAkpZAJ0daWpuaNfmjfV//Uxa9MTFTA3eqACePfDY
JxOyQ/Q0Kle8f41M3V50TiI=
=QEeK
-----END PGP SIGNATURE-----




reply via email to

[Prev in Thread] Current Thread [Next in Thread]