Nice to see you back! I could suggest people follow our procedures and report them to the ntop / ntop-dev list, vs. maintaining a separate system of 3 year old bug reports.
But, here's some rough thoughts: (1) Anything reported against 2.x and (especially vague ones like #179751) should be closed. Anything to do with seg faults and memory needs to be retested against the 3.1 release. This is esp. true of memory bugs reported against 2.x (we no longer resize hashes, so all of that code has been reworked). I routinely run under valgrind and fix anything I find. (2) Memory problems need to be run under gdb/valgrind so we get accurate reports, not vague ones. Especially informationless ones. So that leaves us with: #249878: ntop: insecure default config, leaks possibly sensitive information Package: ntop; Reported by: Marek Michalkiewicz <[EMAIL PROTECTED]>; 340 days old. Suggestion: Read privacynotice.html page (available through the web interface, About | What is ntop) #250217: ntop: sometimes shows parts of host names Package: ntop; Reported by: Marek Michalkiewicz <[EMAIL PROTECTED]>; 338 days old. Response: There were a lot of fixes in this area in 3.1 and so it needs to be retested first. Make sure you delete the dns cache .db file so as not to perpetuate corrupted data. If this is still a problem, I'd like to see a packet capture and the counts from the info.html page to ascertain whether ntop is getting the bad data from DNS sniffing. #260030: ntop packet dump has bad header Package: ntop; Reported by: "David M. Dowdle" <[EMAIL PROTECTED]>; 280 days old. Response: Known problem - don't know why it's happening - it looks like the packet header is overflowing (negative?) but this needs a patched version of libpcap to debug (the tcpdump message is just a pass through from libpcap, which doesn't identify the cause). #269882: ntop: Can't get web pages (gzflush error -2) Package: ntop; Reported by: Alberto Alonso <[EMAIL PROTECTED]>; Tags: moreinfo, unreproducible; 232 days old. Response: Retest. This happens when memory chains are corrupted - libz is just much more sensitive to it than anyone else. I thought all cases had been fixed in 3.1 - there haven't been any reports of this problem re-occuring. #288006: ntop leaks memory Package: ntop; Reported by: Jerome Warnier <[EMAIL PROTECTED]>; 114 days old. Response: See (2) -----Burton -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ola Lundqvist Sent: Sunday, April 24, 2005 2:30 PM To: [EMAIL PROTECTED] Subject: [Ntop-dev] Debian bugs. Hello I have now got some more free time to spend on Debian packaging and therefore I'm trying to resolve the ones with "normal" severity and not just the important and serious ones. Therefore I'm asking you all for advice on a number of Debian bugs. The list is available on: http://bugs.debian.org/ntop If you could help me to determine if some of them are fixed or how it can be fixed it would be really great. Ignore #238500 and #295846 as they are packaging related. All others are general ntop problems. Thanks in advance, // Ola -- --------------------- Ola Lundqvist --------------------------- / [EMAIL PROTECTED] Annebergsslingan 37 \ | [EMAIL PROTECTED] 654 65 KARLSTAD | | +46 (0)54-10 14 30 +46 (0)70-332 1551 | | http://www.opal.dhs.org UIN/icq: 4912500 | \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / --------------------------------------------------------------- _______________________________________________ Ntop-dev mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop-dev _______________________________________________ Ntop-dev mailing list [email protected] http://listgateway.unipi.it/mailman/listinfo/ntop-dev
