Hi,
how did you solve your problem? Could you tell me?
Bhati, Vidushi wrote:
Thanks Toftum :)
--
View this message in context:
http://www.nabble.com/mod-proxy%2C-path-rewrite%2C-and-digest-authentication-tp16098622p17207979.html
Sent from the Apache HTTP Server - Module Writers mailing
I know that the following patch really requires some work to review, but it
is missing only one vote and it would be really worth to be included in 2.2.9:
* mod_proxy: Allow for keepalive backend proxies (PR43238), which also
addresses PR44026 and PR44543. These are pretty much interwrapped
If you are just catching up:
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2008-0166
http://it.slashdot.org/article.pl?sid=08/05/13/1533212
Most of the talk has been about how SSH Servers and Client private keys
are vulnerable.
However, Private x509 Keys generated by a vulnerable machine, and used
I see no issues with making this the default and having a --disable-dtrace.
I can see a reason that someone might wish to turn them off -- thought
that someone isn't me.
+1
--disable-dtrace could be useful in certain scenarios e.g dtrace internal bugs.
IMHO, by default it should be enabled.
