Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #1147613 > unrolled thread

Bug#1036591: reaver: segmentation fault

Back to article view | Back to linux.debian.bugs.dist

Contents

  Bug#1036591: reaver: segmentation fault Leandro Cunha <leandrocunha016@gmail.com> - 2023-05-23 08:50 +0200
    Bug#1036591: reaver: segmentation fault Andrey Rakhmatullin <wrar@wrar.name> - 2023-05-23 22:40 +0200
    Bug#1036591: reaver: segmentation fault Samuel Henrique <samueloph@debian.org> - 2023-05-24 00:40 +0200
    Bug#1036591: reaver: segmentation fault Andrey Rakhmatullin <wrar@wrar.name> - 2023-05-24 10:10 +0200
    Bug#1036591: reaver: segmentation fault Bartosz Fenski <bartosz@fenski.pl> - 2023-05-28 15:50 +0200

#1147613 — Bug#1036591: reaver: segmentation fault

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

[toc] | [next] | [standalone]

#1147723

On Tue, May 23, 2023 at 04:38:26PM -0300, Leandro Cunha wrote:
> Control: tags +1 fixed
Please don't tag this "fixed".

> However, the package is at risk with an NMU of see link for more information.[1]
> 
> [1] https://wiki.debian.org/PackageSalvaging
Not sure what do you mean and how is that related to this bug, sorry.

[toc] | [prev] | [next] | [standalone]

#1147736

> On Tue, May 23, 2023 at 10:21:35PM +0100, Samuel Henrique wrote:
> > Andrey, Leandro meant to use the "patch" tag instead of "fixed", here's his fix:
> > https://salsa.debian.org/leandrocunha/reaver
> Do you think this change will be approved for bookworm, especially at this
> point in the freeze?

I don't see any other better alternative.
I don't think it's worthy to cherry-pick a single possible fix since
the package might be broken in other ways as well.

The correct action here is to update to 1.6.6, which has been released
years ago and is being shipped by a lot of other distros.

To be clear, I haven't tried to reproduce the issue myself, but it
looks general enough and easy to do so, I'll do it in the next few
days, but wanted to make sure we keep moving on fixing this.

Cheers,

-- 
Samuel Henrique <samueloph>

[toc] | [prev] | [next] | [standalone]

#1147769

On Tue, May 23, 2023 at 08:07:45PM -0300, Leandro Cunha wrote:
> There was a user who reported that the problem also occurs in Debian
> 11 (Bullseye).
> But I can't confirm because I don't use stable.
> Samuel, I know you use testing.
> Andrey Rakhmatullin, do you use stable or do you have machines with stable?
No.
But if you don't have a fix suitable for stable it doesn't matter that
much to confirm the bug there.

[toc] | [prev] | [next] | [standalone]

#1148180

Hey,

I'm fine with NMUing it. Thanks for your effort.

regards
Bartosz Fenski

W dniu 23.05.2023 o 23:21, Samuel Henrique pisze:
> Control: tags -1 patch fixed-upstream
>
> Hello Bartosz,
>
> We are planning to perform an NMU, changing the package's maintership
> to the Security Tools team (while keeping you as an Uploader), fixing
> this RC bug and filling an unblock request so we can ship this package
> for bookworm.
>
> Please let me know if you disagree, we will have to act quickly due to
> the freeze.
>
> Andrey, Leandro meant to use the "patch" tag instead of "fixed", here's his fix:
> https://salsa.debian.org/leandrocunha/reaver
>
> Cheers,
>

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.bugs.dist

csiph-web