Package: reaver
Version: 1.6.5-1+b1
Severity: grave
Justification: package unusable
Tags: fixed

Dear Maintainer,

   * What led up to the situation? The package has a segmentation
fault on any command I tried to run, but I've used this package in the
past and it was working and I think some more up-to-date dependency is
causing this.
   * What exactly did you do (or not do) that was effective (or
ineffective)? Executing multiple commands.
   * What was the outcome of this action? Every command executed
returns segmentation fault.
   * What outcome did you expect instead? The correct thing is that
all commands were executed correctly.

I tried compiling a newer version 1.6.6 and it worked fine with no
segmentation fault. Plus several improvements upstream.
Remembering that this packaging is unusable in the face of tests carried out.

Short description of what the segmentation fault is about in your description.
In the context of segmentation fault, segment refers to the program
memory address space. Only the program's memory space is readable. Of
this space, only the stack and part of the data segment are writable.
Other parts of the data segment and text segment are not writable.
The data segment is where global or static variables reside. The text
segment, also called the code segment, is where program instructions
are stored.
Segments have size and permissions, such as write, read, and execute.
Segmentation fault occurs when a program tries to access restricted
memory, such as trying to write to the text segment or read from a
non-existent memory address. The failure is reported by the memory
protection system of the Memory Management Unit or MMU. The MMU is the
hardware responsible for translating the virtual memory address to
physical addresses.
As soon as the MMU notices a memory access violation, it informs the
Kernel of the problem. In the case of Linux, the Kernel sends a signal
to the program, the SEGV. Upon receiving the signal, the program is
usually terminated.

-- System Information:
Debian Release: 12.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-security'), (500,
'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-9-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8),
LANGUAGE=pt_BR:pt:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages reaver depends on:
ii  libc6       2.36-9
ii  libpcap0.8  1.10.3-1

Versions of packages reaver recommends:
ii  pixiewps  1.4.2-5

Versions of packages reaver suggests:
ii  aircrack-ng  1:1.7-5

-- no debconf information

Reply via email to