Hi Arthur, Carlos,
the issue you reportied looks a lot like
https://github.com/the-tcpdump-group/libpcap/issues/333 or
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733747, which was
fixed in libpcap 1.5.3 (uploaded 2014-01-16, in jessie since
2014-01-27).
As I'm unable to reproduce the
Hello all,
just chiming in here ...
On Wed, Feb 12, 2014 at 10:18:32PM +0100, Florian Schlichting wrote:
the issue you reportied looks a lot like
https://github.com/the-tcpdump-group/libpcap/issues/333 or
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733747, which was
fixed in libpcap
Hello all,
just chiming in here ...
On Wed, Feb 12, 2014 at 10:18:32PM +0100, Florian Schlichting wrote:
the issue you reportied looks a lot like
https://github.com/the-tcpdump-group/libpcap/issues/333 or
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733747, which was
fixed in libpcap
Florian Schlichting wrote, on 13/02/14 07:48:
Hi Arthur, Carlos,
the issue you reportied looks a lot like
https://github.com/the-tcpdump-group/libpcap/issues/333 or
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733747, which was
fixed in libpcap 1.5.3 (uploaded 2014-01-16, in jessie since
On 12/02/14 22:58, Arthur Marsh wrote:
Florian Schlichting wrote, on 13/02/14 07:48:
Hi Arthur, Carlos,
the issue you reportied looks a lot like
https://github.com/the-tcpdump-group/libpcap/issues/333 or
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733747, which was
fixed in
severity 731155 grave
thanks
I'm raising the severity level.
The rationale is that this bug not only makes arpwatch unusable, but
also can break the system.
A rogue process eating the 100% of the CPU in an endless loop can cause
the system to seriously overheat or malfunction.
I have deleted
Package: arpwatch
Version: 2.1a15-1.2
Severity: normal
Dear Maintainer,
*** Please consider answering these questions, where appropriate ***
* What led up to the situation?
upgrading libpcap0.8 to 1.5.1-1
* What exactly did you do (or not do) that was effective (or
ineffective)?
7 matches
Mail list logo