[emacs-wiki-discuss] Re: Access control for published pages

[Andrew J. Korty]

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

Gerd Flaig <address@hidden> writes:

>     1. Change emacs-wiki so it can publish to a list of publishing
>        locations
>
>     2. Add another tag (<private> maybe?) to publishing-markup that
>        omits its content when publishing to a location not marked
>        private

That might work for some.  I want my boss to be able to read certain
entries that other people can't.  But I want him to be able to read
the public pages, too, and I'd prefer not to make him visit more than
one site to do so.

Here's what I have so far.  Any page can contain a #authz tag followed
by a list of users that can view the page.  That page is wrapped in
some Masonry that hides the content from anyone except those users.
If that page's tasks or notes are found on any other page, they're
wrapped on that page, too.  There's also an <authz> tag for
restricting arbitrary content.  I'll post my code as soon as I get it
working. :-)

Someone mentioned that Mason is overkill, and I tend to agree.  We
only need the logic portion (not the caching, test environment, etc.),
so server-side includes or the Template Toolkit might work instead.
I'd like to make it work without anything external, but I haven't
figured out how to do so while fulfilling all my requirements.

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

iD8DBQFAykeM8gM8+Mr5peERAheRAJ4h7CaelD51zpJ1cv+D1ZSE3YsCpQCg0M8L
hfEIHfwh1jwJY7ZlfBp9Ot8=
=V+F9
-----END PGP SIGNATURE-----