On Wed, Jan 03, 2001 at 12:02:15AM -0600, Jeff Sheffield wrote:
> I am ashamed ... I twitled with the shiny bits.
> my $auth_name = "WhatEver";
> $SECRET_KEYS{ $auth_name } = "thisishtesecretkeyforthisserver";
> ### END MY DIRTY HACK
> Note that without MY DIRTY LITTLE HACK it does not set those two
> variables. I am/was pretty sure that this somehow relates to
> "StackedHandlers"
I believe the problem is a known documentation bug with the module. I need
to fix the docs and make a new release (have been meaning to for, oh,
five months now) but I no longer work at the place that originally paid
me to write the module and haven't had a chance so far. I have a few other
patches to integrate too. I believe your specific problem stems
from having the:
PerlModule Apache::AuthCookieDBI
line before the
PerlSetVar WhatEverDBI_SecretKeyFile /www/domain.com/test.key
line in the server config file. Yes, the documentation has it the wrong
way around. The reason is that the server reads this configuration
directive at module load time (i.e. with PerlModule, at server start time
when it's still running as root) so that it can preload the secret keys
from files on disk. You want those files to be root-owned and only
readable by root, which is why it does it at start time. Try putting
all your DBI_SecretKeyFile directives before the PerlModule line and
see if that fixes your problem.
It should give better diagnostics when this problem comes up, I need to
fix that. Right now I don't even have this module running anywhere, but
I will install it again on my home machine at least, for testing.
Hopefully I will have a new release and an announce notice for this out
soon.
--
Jacob Davies
[EMAIL PROTECTED]
