Your message dated Mon, 29 May 2023 17:48:55 +0000 with message-id <e1q3gzh-0069kf...@fasolo.debian.org> and subject line Bug#1036591: fixed in reaver 1.6.6-0.1 has caused the Debian Bug report #1036591, regarding reaver: segmentation fault to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1036591: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036591 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---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
--- End Message ---
--- Begin Message ---Source: reaver Source-Version: 1.6.6-0.1 Done: Leandro Cunha <leandrocunha...@gmail.com> We believe that the bug you reported is fixed in the latest version of reaver, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1036...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Leandro Cunha <leandrocunha...@gmail.com> (supplier of updated reaver package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Sat, 27 May 2023 14:24:29 -0300 Source: reaver Architecture: source Version: 1.6.6-0.1 Distribution: unstable Urgency: high Maintainer: Bartosz Fenski <fe...@debian.org> Changed-By: Leandro Cunha <leandrocunha...@gmail.com> Closes: 901595 1036591 Changes: reaver (1.6.6-0.1) unstable; urgency=high . * Non-maintainer upload. * New upstream version. * debian/watch: - Fix watch file is broken and generating errors. (Closes: #901595) - Change version of 3 to 4. * Fix segmentation fault. (Closes: #1036591) Checksums-Sha1: b045c51de7384c4fb4ddabbdc9bad870cdc37869 1736 reaver_1.6.6-0.1.dsc 7e018618bf827b2db274c4b349c3a5ad72ddf4c3 485854 reaver_1.6.6.orig.tar.gz 1420e02d8168640b1592e5b57c6748e37a4f674a 3124 reaver_1.6.6-0.1.debian.tar.xz a67756353005217db1818ec17c03be956736006e 6706 reaver_1.6.6-0.1_amd64.buildinfo Checksums-Sha256: ba3ed6cb26a648465342098c45b8d23900cc1b8bb6151b4779ac1ded43d34b59 1736 reaver_1.6.6-0.1.dsc 73189782b208d12b8dddc4f29d32e1f72b1f3609e573c9ea9510deebec394583 485854 reaver_1.6.6.orig.tar.gz 1d3f9b53507523c51f147452b47f8b5b40a9488001311067a17fd5291cedaaa6 3124 reaver_1.6.6-0.1.debian.tar.xz 35a4ac59627403dee62f940a1109c0ccd8f0cb916ae481f1aaa74f907add7677 6706 reaver_1.6.6-0.1_amd64.buildinfo Files: 28495f9276b755ac64e7e98837e1b023 1736 net optional reaver_1.6.6-0.1.dsc db02764b2397d19d7ff53e4a7c66cd79 485854 net optional reaver_1.6.6.orig.tar.gz 0fae2843a1352bcef37ec36cc798ba90 3124 net optional reaver_1.6.6-0.1.debian.tar.xz d75751d1d71972a7a8d0ab9ce7ab357b 6706 net optional reaver_1.6.6-0.1_amd64.buildinfo -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEBdtqg34QX0sdAsVfu6n6rcz7RwcFAmR04DoACgkQu6n6rcz7 Rwdteg/8Dnj5JwjkotTdjLaEd5BUOfjHcosNE8o8X45Y+N+KsB0sOBnzB4B6EjIJ mNgT/MMzakKZYlE3n0W+oT6ufQalhCOMzIzVtW9CplI3/K5PSBgObyBezDAaDknw ENVmYzYSWEOvDXoWbi0QbeocdFBrwWra3HTy8MGq6OnBbGaWnFcqcSr1kFDG0PRs fEzbXRuIiPgbGYDBS8tpzwwkOsOjj3y2YmyGF0MflR5ZCZ5kb/rpTi34b04kNBo3 BhF+0UjJR1v0qtM0Di8ca4yn08qPdOu6qW+xBoJdZFMlJQBYzccoj9yJmnsVhFIv uAe+Ra8xPAZ/R2EclVRwov3Oc/73IxGjnKQuVAY0a3iQnmOn4LhlVO31oZUmUDj6 Hv5fIyGw8hNsr9sCrSU09aVBtxhUOTc4qMmsmkweviHUfwHMUtq1y/1A/8SgfTt0 1oYVDTAJ3vacTYVhMwsfHPmAteScYsy6I/MEIhegnZuzd99ZVMigRi8W0uhVsgjg 0VjPwU+psP4m0qnID7EoHQciplYgC7YpAnfYNpVrrWnwNviqDeCL3J9vvHtZP2Cd JxEgIb7ZKVJiKgxBzrSp/UwxRfsqZi5g3PtT0A1PQPKe9kl0QXUOucEdZmFJChib G52KM99Coh7u0bupK/61r/xwGdktAQB9E0csLb+opWP1QqERYWU= =Bakc -----END PGP SIGNATURE-----
--- End Message ---
