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

[Andrew J. Korty]

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

Greetings.  I'd like to publish my planner and Wiki pages so I can
point people to what I'm working on.  But being a security dude, I
write some things only my team or my boss are allowed to see.  So I'm
curious if someone has dealt with the problem of granular access
control on planner pages.

One of planner's greatest strengths is the extent to which it
interconnects pieces of information, but that makes it all the more
difficult to limit access to one piece and not another.

So far I've come up with two general approaches to the problem.  One
is to use separate planner directories for public and private
information.  I don't think that will work very well, though, because
my team will need information from both.  They'll have to know where
to look and keep switching between the two.

The other approach is to use a completely separate system for
publishing notes.  For example, I could use Mason (a component
architecture built on mod_perl) and generate a separate content for
each note.  A remember handler could insert notes as separate
components into this system.  Then some Mason code could control
access to each note, and the equivalent of day and project pages would
be built dynamically depending on the credentials of the viewer.

The latter seems like the way to go, but it would be a lot more work.
Also, I would prefer the simplicity of emacs-wiki-publish.  So now I'm
just fishing for ideas.  Is anyone else in a similar situation?

- -- 
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)

iD8DBQFAwgYM8gM8+Mr5peERAuxgAJ0SN+B3b7XUEhO4XL47jucniai7GwCfQ833
RHwOusdtca+016BGd+C/owQ=
=tcNE
-----END PGP SIGNATURE-----