Your message dated Mon, 04 Nov 2024 18:29:34 +0000 with message-id <e1t81pw-0033tb...@fasolo.debian.org> and subject line Bug#1080503: Removed package(s) from unstable has caused the Debian Bug report #1027037, regarding backdoor-factory: Backdoor-factory isn't working after python3 transition 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.) -- 1027037: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027037 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: backdoor-factory Version: 3.4.2+dfsg-5 Severity: grave Justification: renders package unusable X-Debbugs-Cc: charlesmel...@outlook.com Dear Maintainers, hi. I was working to get a new debian release of backdoor-factory (bdf) before the freeze and noted while testing it that it doesn't work with python3. I tested the application trying to patch a binary in 4 scenarios: 1. ELF binary - ssh with -fPIE compiler flag set (it shouldn't work as warned in the man page); 2. ELF binary - devtodo without -fPIE flag set (I've built it locally and disabled hardening option in d/rules); 3. PE binary - premake4.exe; 4. PE binary - PSTools from microsoft (the one actually show in the README example). In all test scenarios, bdf showed a message saying the binary wasn't compatible although they were in 3 out of 4 scenarios. Digging a little deeper in the source code, I've found the problem. Even though bdf was patched to build with python3, those changes only fixed syntactic problems (mostly print statements). The actual problem - and source of the bug - is the change on how files are read in python3. In python2, everything read from a file was considered a string. But in python3 it is considered a bitearray if the file was opened as a binary ('rb' option for example). In the source code of bdf, everything is treated as strings (comparisons, assignments, operations, etc), but now everything read from the binary file is a bytearray so the program fails to identify it as a susceptible binary. Even though it would be easy to patch this to make bdf correctly identify the file, every step after that would also need to be fixed (Right now, it basicaly fails to identify the files as susceptible and exits). That would require a major rewrite of the program, together with testing and debugging. Cheers, Charles -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.0.0-5-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---Version: 3.4.2+dfsg-5+rm Dear submitter, as the package backdoor-factory has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1080503 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)
--- End Message ---
