is only the first step - so far no clients support it yet.
vh
Mads Toftum
--
`Darn it, who spiked my coffee with water?!' - lwall
, concise and more of a reference is the way to go, and it makes
life simpler for someone like me who admins apache more than mod_perl.
vh
Mads Toftum
--
`Darn it, who spiked my coffee with water?!' - lwall
as an SSL
proxy module that I've been able to find.
I did make a module like that last year - it is available from
http://www2.toftum.dk/apache/
vh
Mads Toftum
--
`Darn it, who spiked my coffee with water?!' - lwall
it
to allow the weak ciphers, and then limit actual access by using SSLRequire
to allow only = 128 bits encryption.
vh
Mads Toftum
--
`Darn it, who spiked my coffee with water?!' - lwall
accelerator support which might end up giving us some cheaper
hw options in the future.
vh
Mads Toftum
--
`Darn it, who spiked my coffee with water?!' - lwall
Take a look at ftp://ftp.netcetera.dk/pub/apache/mod_proxy_add_forward.c
It could be a way to solve your problem.
vh
Mads Toftum
--
`Darn it, who spiked my coffee with water?!' - lwall
for such a setup - I usually end up with a mix
of proxy and rewrite to get the job done.
Lots of examples are available in http://www.apache.org/docs/misc/rewriteguide.html
vh
Mads Toftum
--
`Darn it, who spiked my coffee with water?!' - lwall
through the firewall is restricted to one
simple rule in the FW machine and that it can be easily protected with
encryption/authentication.
This probably doesn't answer your question ;-) But I hope that at least
the idea is useful.
vh
Mads Toftum, QDPH
specific example isn't a problem - something like
A HREF="http://intranet_host/" would be a problem.
vh
Mads Toftum, QDPH
