Hello
> sorry for not responding to your mails, but as i have no access to
> my mail account right now, i have to do this from work.
Nice to hear from you again.
> 1.) mod_php:
> This is what i work on right now, as the PHP Group didn`t do
> so yet.
Sadly they seem to have gone more for IIS support under Windows.
> Status: Not ready yet, but i will try to get it done
> within the next two weeks.
Oooooh, I look forward to it <g>
> 2.) mod_perl:
> Like mod_php, this will be an issue for the next master release.
> To Luke: we`ll have to define some kind of standard config for
> the InstallShield installation, to allow running without doing
> any config.
I'd like to use the new release of perl, and I've soured to ActiveState
recently so I intend to use the basic perl distribution. Because of the
close ties between mod_perl and perl, the two really have to be distributed
together, either as a seperate install package or in with OpenSA (ouch!). I
suspect the former would be more practical.
As for mod_perl config, any preferences people? I quite like my current
set-up of having /perl-bin like /cgi-bin for perl, .phtml files as
HTML::Embperl and the /perl-status directory to report status, but I'm a
neophile who's new to mod_perl.
> Luke, any experiences with OpenSSL, mainly using it with
> scripting languages like perl, php or batch files are
> appreciated, no matter if they succedded or not :-)
As I said, I intend to open my own CA soon based on OpenSA's OpenSSL, and
Perl. It's currently under TinyWeb (it's still good for development as it's
so simple to use), but I'll move it to OpenSA for the Grand Opening.
OpenSSL is infinitely more stable and complete than those old ssleay
binaries I used to use, and I've not found any problems yet (other than some
misleading error messages, but I suspect it's a problem of the OpenSSL
source).
>From a certificate issuer point of view, I'd like to see the ca-fix program.
It already compiles under Windows using the OpenSSL headers, so I hope it
should be easy to do, and it makes up for some shortfalls of OpenSSL. It's
available from www.drh-consultancy.demon.co.uk (?) under 'Certificate
Patcher Program' or something.
If you want my perl scrips drop me a line, but you'll probably do better
until I tidy it up a bit.
Finally, is anyone gullible enough to help me test the certificate issuer?
So far I do it myself under IE5 and NS4.6, but I'd like some feedback. It's
probably better if you _don't_ have a keyring full of keys since it may eat
your keyring for you (but unlikely), and security is currently on the back
burner (although I'll be using https and basic auth mainly)
> To make my point clear: i never wanted any kind of financial
> support. If you have any suggestions on how to handle things
> in a fair way, i`d be glad to hear them.
IMHO keep it all free, but say that any contributions would a) be welcome
and b) bring the matter in question towards the front of your todo list!
Regards,
Luke
