[15974] in Kerberos_V5_Development
Re: Dynamic plugin modules and OS packages
daemon@ATHENA.MIT.EDU (Russ Allbery)
Tue Jul 13 16:47:01 2010
From: Russ Allbery <rra@stanford.edu>
To: krbdev@mit.edu
In-Reply-To: <201007132038.o6DKcqBT018604@outgoing.mit.edu> (ghudson@mit.edu's
message of "Tue, 13 Jul 2010 16:38:52 -0400 (EDT)")
Date: Tue, 13 Jul 2010 13:46:55 -0700
Message-ID: <87eif79kjk.fsf@windlord.stanford.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: krbdev-bounces@mit.edu
ghudson@MIT.EDU writes:
> * We add "include" support to the profile library, and the OS adds
> "include /etc/krb5.conf.d/*" to its standard krb5.conf. Each
> plugin package supplies a profile fragment giving the location of
> the dynamic object and an enable/disable boolean (which may
> default to on or off depending on the packaging model and/or the
> plugin).
I prefer this approach. I've been wanting this for a long time for other
reasons.
This enables using the Debian Apache packaging approach for enabling or
disabling plugins, where the plugin configuration files are installed in a
separate location and selectively symlinked into the include directory for
krb5.conf using a tool that adds or removes the symlinks to enable or
disable the plugins.
--
Russ Allbery (rra@stanford.edu) <http://www.eyrie.org/~eagle/>
_______________________________________________
krbdev mailing list krbdev@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev
