Bug#824229: Good News

You are lucky,Two Million has just been donated to you, contact: lerynnewest...@outlook.com for more details. University of Northampton: Transforming Lives and Inspiring Change www.northampton.ac.uk This e-mail is private and may be confidential and is for the

Bug#421802: apache2: ssl.conf dropped IE workarounds

Stefan Fritsch wrote: The problem is that the IE workaround needs to be in the ssl virtualhost context (see #289868), but ssl.conf is global server context. Therefore, you have to add the workaround to your ssl virtualhost file. When an example ssl virtualhost is added, the IE workaround

Bug#421802: apache2: ssl.conf dropped IE workarounds

Stefan Fritsch wrote: When an example ssl virtualhost is added, the IE workaround should be included there. That's not been my experience at all. Simply re-instating the section in its location in httpd.conf solved the problems I was experiencing. Yes it does. But it causes a different

Bug#406493: chkrootkit: Same problem here...

Package: chkrootkit Version: 0.47-1.1 Followup-For: Bug #406493 However, applying the following patch seems to have solved the issue: http://stereo.lu/chkrootkit.diff.html -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (700, 'stable') Architecture: i386 (i686)

Bug#421864: chkrootkit: false positive for Enye LKM

Package: chkrootkit Version: 0.47-1.1 Severity: normal The check for the Enye LKM seems pretty bogus as described here: http://guru.multimedia.cx/a-few-days-ago-chkrootkit-told-me-enye-lkm-found/ I had exactly the same experience... Chris -- System Information: Debian Release: 4.0 APT

Bug#421802: apache2: ssl.conf dropped IE workarounds

Package: apache2 Version: 2.2.3-4 Severity: normal For no apparent reason, the following IE support lines were removed from mods-available/ssl.conf in the transition from sarge to etch: SetEnvIf User-Agent .*MSIE.* \ nokeepalive ssl-unclean-shutdown \ downgrade-1.0

Bug#310740: Still experiencing the same problem.

I'm only latest stable debian, did: aptitude install nessusd ...and followed the birdy. As detailed already in this bug report, when I do: nessus-fetch --register ...I get the Unknown error while decoding HTTP response. I'm behind a NAT/DHCP ADSL router, but there's no proxying involved.