related to
child of
duplicate of
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0008166 | Kali Linux | Kali Package Improvement | public | 2023-01-29 13:05 | 2023-08-25 16:20 |
| Reporter | turbopapero | Assigned To | |||
| Priority | normal | Severity | feature | Reproducibility | always |
| Status | closed | Resolution | open | ||
| Product Version | 2022.4 | ||||
| Summary | 0008166: Decompiler not working in packaged version of Cutter | ||||
| Description | In the Appimage version available on https://cutter.re there are two decompilers working out of the box. Attached, a screenshot of the packaged version (black) and the Appimage version (white), running on the same binary. The packaged version of cutter is currently 2.1.0. | ||||
| Steps To Reproduce | Run cutter on Kali 2022.4 with any binary and go to the decompiler tab. | ||||
 |
I think it's because rz-ghidra (-> https://github.com/rizinorg/rz-ghidra) is not packaged in Kali. (Note that ghidra itself IS available in Kali, just install the package ghidra). If you wish to see rz-ghidra packaged for Kali Linux, here's your starting point https://www.kali.org/docs/tools/submitting-tools/ (don't forget to link to this issue) |
 |
If I got it right from the rizin pages we can't use the code from the Ghidra tool, we need the rz-ghidra plugin to make it work with Cutter. I am asking the developers about the possibility of a deb package here: https://github.com/rizinorg/rz-ghidra/issues/314 I will submit the tool request as you suggested once this is clarified. Thanks |
|
|
Confirmed that the tool is already deb packaged by other distro (e.g. for Parrot OS https://gitlab.com/parrotsec/packages/rizin-ghidra-plugin/-/tree/master/debian) but the rz-ghidra developers do not maintain the deb package. The deb package has to be maintained by the distro owners. I will create the new tool request as soon as possible. |
|
|
Reading your comments and it all looks correct. Generally speaking, distro packages are maintained by distro maintainers, not by upsteam. Of course, It's possible that an upstream developers have two hats, and is at the same time a distro maintainer, and also takes care of packaging their application for a distro. But here it's not the case, so if we want this package in Kali, it has to be setup and maintained by Kali developers. Thanks for submitting the tool request! |
 |
|
|
|
This report has been filed against an old version of Kali. We will be closing this ticket due to inactivity. Please could you see if you are able to replicate this issue with the latest version of Kali Linux (https://www.kali.org/get-kali/)? If you are still facing the same problem, feel free to re-open the ticket. If you choose to do this, could you provide more information to the issue you are facing, and also give information about your setup? |
