Bug#797043: xul-ext-noscript: menu no longer shows script sources after iceweasel 41.0-1

2015-09-28 Thread Christian Kujau
I'm using Iceweasel/release on Debian/Jessie and had the same error after the last Iceweasel upgrade (40.0.3-3 => 41.0-1). In fact, NoScript was reported as "not compatible with v41" in about:addons and I could not even re-enable it after I disabled it temporarily to try to get the menu back ag

Bug#774047: pnp4nagios FTBFS on arm64, outdated config.sub/guess

2015-05-03 Thread Christian Kujau
So, the fix for #774047 is in the repository[0] but wasn't uploaded to the archives? If this happens, can pnp4nagios still become part of Jessie or is this way too late? Thanks, Christian. [0] https://anonscm.debian.org/cgit/pkg-nagios/pkg-pnp4nagios.git/commit/?id=d7b0b893927cc8c0783379003dff

Bug#569658: libapache-mod-security: upgrade to 2.5.12

2010-03-10 Thread Christian Kujau
I've successfully built (and installed, activated) libapache2-mod-security against v2.5.12 and put the results (.diff, .dsc, .changes) on: http://nerdbynature.de/bits/BTS-569658/deb/ The .diff (attached) is basically just libapache2-mod-security_2.5.11-1~bpo50+2.diff.gz from #516540 plus a ch

Bug#457828: on detecting Enye LKM

2008-04-26 Thread Christian Kujau
Hi, while reading #457828 I wanted to find out more about this Enye LKM and stumbled over another method to check for this particular rootkit. How about: http://www.binrev.com/forums/index.php?showtopic=19617&st=0&p=217399&#entry217399 Thanks, Christian. -- BOFH excuse #304: routing problems o

Bug#449200: [Pkg-openssl-devel] Bug#449200: libssl0.9.8: wpa_supplicant segfaults with 0.9.8f-2

2007-11-11 Thread Christian Kujau
I too can confirm that libssl0.9.8_0.9.8g-3_i386.deb fixed the bug. I noticed that I could use libssl0.9.8_0.9.8g-2_i386.deb, but only when I compiled wpa_supplicant with -O0 and opened http://hostap.epitest.fi/bugz/show_bug.cgi?id=245 (which I've closed now with an actual fix in place). Tha

Bug#412572: F1D53D8C4F368D5D removed?

2007-03-24 Thread Christian Kujau
Hi, I stumbled over #412572 while trying to figure out why the F1D53D8C4F368D5D is not available any more: > [EMAIL PROTECTED]:~$ gpg --no-default-keyring --keyring > /usr/share/keyrings/debian-archive-removed-keys.gpg --with-colons > --list-keys| awk '/^pub/{FS=":";print $5}' > Key > F1D53D8C4

Bug#366748: snort-mysql still depends on libmysqlclient12

2006-06-04 Thread Christian Kujau
On Sun, 4 Jun 2006, Javier Fern?ndez-Sanguino Pe?a wrote: It looks like there is no libmysqclient-dev that Snort-mysql could use. It seems reasonable, however, as the different versions probably provide incompatible APIs. Hm, the build-depends of the original snort_2.3.3-6 package say: libmysq

Bug#366748: snort-mysql still depends on libmysqlclient12

2006-05-31 Thread Christian Kujau
Package: snort-mysql Version: 2.3.3-6 Followup-For: Bug #366748 I've noticed the same dependancy and I was happy that it was already "fixed"...almost: $ apt-cache show snort-mysql | egrep '^Version|libmysqlclient' Version: 2.3.3-6 Depends: snort-rules-default (>= 2.3.3-6), debconf (>= 0.2.80) |

Bug#299875: ppp: out-of-memory 30min after "LCP terminated by peer"

2005-03-20 Thread Christian Kujau
Justin Pryzby wrote: > Okay. Do I correctly understand that kernel patch + downgrade solves > your problem? i don't even have to patch the kernel. i tried with 2.6.11-rc5-bk2, same thing. but (only!) downgrading ppp_2.4.2 (current is ppp_2.4.3) did the trick. > And, if you have *just* the kernel

Bug#299875: ppp: out-of-memory 30min after "LCP terminated by peer"

2005-03-20 Thread Christian Kujau
hi again, sorry for the delay, but the "bug" triggers only when the remote peer disconnects me - and it does it only once a day. Marco d'Itri wrote: > reassign 299875 kernel > retitle 299875 CAN-2005-0384: Remote Linux DoS on ppp servers > tag 299875 patch security yes, it really looks like a "p

Bug#299875: ppp: out-of-memory 30min after "LCP terminated by peer"

2005-03-17 Thread Christian Kujau
Justin Pryzby wrote: > I assume that you have seen this: > http://kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.11.4 yes i have*now*. obviously this was a security issue (CAN-2005-0384) and i *guess* that's why the issue was not discussed in public. what pity and what a waste of time in tra