HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
radareorg
cutter
HISTORICAL RECORD2017–2020
radareorg / cutter · Not publicly available

cutter

Discover this repository through its Hacker News conversations.

13Distinct people
21Mentions
0Explicit recommenders
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A public description has not been verified.

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year21 dated mentions

Observed mentions: 2017-12-04 13:38:53 UTC to 2020-12-13 07:30:10 UTC.

02462017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 4 mentions; 3 submissions, 1 comments20172018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 7 mentions; 2 submissions, 5 comments20182019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 5 mentions; 2 submissions, 3 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 5 mentions; 1 submissions, 4 comments2020

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC431
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC725
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC523
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC514

What Hacker News says

21 sources
This is a really well-designed page. The website is full of nice-looking graphics, good web design, and convincing demo material. That's interesting for a fork that was announced a couple days ago. A story is missing here, and I think it should be told. Unfortunately, I don't know what it is. However, people don't spontaneously decide to fork a project, and the details here are too vague for a value judgment. Firstly, I'd like to thank the project for doing actual tangible work before announcing a fork. If you are going to fork a project over internal disagreements, you have to understand and appreciate that the world doesn't have time to dig into literally 10,000 different project's internal affairs to try to guess which side of a fight to take; most people would prefer to let the contributors decide who wins by virtue of mindshare, and
Read the rest
then pick the technically better project as a result. Rizin is off to at least some start here, having at least one major feature and some aspirations. Firstly, why did this project start? To get a better idea of what's going on, let's analyze the timeline. The project appears to have kicked off on October 1st, at least symbolically. The first PR seems to be a rename: https://github.com/rizinorg/rizin/pull/2 What are the values of the Rizin org and what do they define as welcoming vs unwelcoming? Since I don't know for sure, I can take a cursory glance at the types of PRs that exist within Rizin so far. - Use Meson for macOS CI #3 -- A CI related change. - Other renames in man and small places #4 -- Looks like more renames. Was pushed manually to master for some reason? Note also that it seems the primary branch has been renamed from 'master' since it was mentioned in this PR. - Use R2PIPE_* -> RZ_PIPE_* env vars #5 -- More radare->rizon renames. ... - Import patches #10 -- First import of Radare2 patches that I have noticed. ... - Add new Projects Implementation #12 -- First major feature I can find. ... - Create CODE_OF_CONDUCT.md #93 -- The project gains a code of conduct. Arguably the first interesting change that demonstrates the values of the project in some form. ... - Change the "anal" abbreviation to "Analysis" in Code #117 -- December 6th. Interestingly, the source branch 'no-more-anal', reads a lot like a joke of a similar fashion to what is apparently unacceptable. This PR is the next change that demonstrates the values of the project. - Add a fortune #118 -- "Rizin is the vegan pineapple pizza of reverse engineering tools." That's funny. I wonder if that's a bit of tongue-in-cheek self-awareness about the optics of forking a project over "ideological" disagreements. ...Ultimately, most of the PRs fall into the category of: - 21 PRs: CI/infrastructure changes. - 18 PRs: importing Radare2 changes. - 9 PRs: renaming Radare2 -> Rizin ...of the 100 or so PRs. A lot of the others are minor changes like documentation updates, but it's hard to enumerate them into groups easily. After surveying the PRs, it is no clearer exactly what motivates the project. Searching through Radare PRs get no closer. Looking for PRs from around the time the project is created, I don't see many points of contention. I see some other discussions about fortunes but really not many. Searching through issues, much doesn't stand out. Fortunes doesn't appear to come up much in issues, with the search returning nothing from this year. --- With that excavation out of the way, I'd like to turn my attention to the claim that Rizin is made up of "core Radare2 developers." This should be relatively easy to confirm. Firstly, we can look at the developers listed in AUTHORS.md: Mentors and co-maintainers -------------------------- Most active in community, setting up CI servers, regression tests, esil, coverity, blog, release notes, .. - xvilka - condret - crowell - jvoisin - maijin Now we can look at the top 5 contributors to Radare2 on Github: - user "radare", apparently goes by the alias pancake, seems to be the primary maintainer. Very active all the way from 2010 to 2019, where things seem to have tapered a bit. 12,040 commits, 1,308,025 ++, 911,136 -- - user "alvarofe", was active during a couple of years, is mentioned specially in the AUTHORS.md file. 852 commits, 52,922 ++, 43,348 -- - user "XVilka", pretty active since around 2013. 834 commits, 92,857 ++, 54,658 -- - user "kazarmy", active since 2017. 779 commits, 24,498 ++, 17,779 -- - user "ret2libc", with a somewhat sporadic looking graph with pretty large activity spikes since 2015 or so. 673 commits, 170,629 ++, 89,518 -- Alright. Now onto the Rizinorg team on GitHub, it is comprised of the following members: - user "ITAYC0HEN," Itay Cohen. - user "kazarmy," Khairul Azhar Kasmiran. - user "ret2libc," Riccardo Schirone. - user "thestr4ng3r," Florian Märkl. - user "wargio," Giovanni. - user "XVilka," Anton Kochkov. Some notes to make: - "radare" aka pancake is not present. Obviously, otherwise it would beg the question why a fork is needed. - "xvilka" is one of the contributors who was specially called out in the README as a core contributor. - All of these developers were contributors to radare2 who contributed more than minor bits. This is a good sign for Rizin, of course. So not every core developer is involved in Rizin, but the Rizin team has plenty of developers who have worked a lot on Radare2. --- The next aspect that's interesting is Cutter moving over. Who works on Cutter? There is no similar AUTHORS.md in Cutter, however it is in the Rizin org now. This is interesting. I think this may have been the last step before launching Rizin. You can see that it appears Cutter was under Radareorg until very recently: https://web.archive.org/web/20201208101941/https://github.co... Further, we can look at the top Github contributors: - user "thestr4ng3r", Florian Märkl. 558 commits, 47,091 ++, 49,926 -- - user "xarkes" - do not appear to be terribly active anymore. 364 commits, 47,370 ++, 55,610 -- - user "ITAYC0HEN," Itay Cohen. 196 commits, 12,434 ++, 5,895 -- - user "karliss," 165 commits, 22,387 ++, 11,620 -- - user "fcasal," 83 commits, 6,327 ++, 823 -- Notably, thestr4ng3r and ITAYC0HEN are also part of the Rizinorg team. karliss is not despite seeming to be a major part of maintaining Cutter up until recently. It looks like Cutter operated the Rizin changes in private for some reason, until relatively recently. You can see evidence of this here: https://github.com/rizinorg/cutter/pull/2496/files which I find interesting. --- All of this leaves me feeling very mixed. I don't feel we really know what the motivations for Rizin are. The above-ground claim is that the reason why Rizin exists is due to an unwelcoming environment. Based on the kerfuffles with fortunes and renaming anal to analysis, I can only suspect that this is due to issues such as offensive language. However, the project was forked on October 1st before I can find much evidence of the fortunes problem, so it must've been brewing already. But what's weirder than that is that the fork was done by "thestr4ng3r," one of the primary developers of Cutter, who, as far as I can tell, does not seem to care that much about political correctness, at least based on the very tiny amount of information I can exact from these public channels, based on discussions that occurred after the fork had already begun: https://github.com/radareorg/radare2/pull/17980 (An aside: I am not attempting to 'shame' anyone, just making observations based on publicly available information. Make your own judgements.) That last part, "After the fork had already begun," is where things get interesting. It is possible that there were disagreements with pancake in private, or other bad conduct that I just happen to be missing, but above all I question the sincerity of the reasoning for this fork. I would like the maintainers to clarify what is going on here. Otherwise, it feels like there is some kind of power struggle going on, and that users are being roped into it without hearing the real reasons why. The stuff involving Cutter is especially interesting due to the fact that upstream Cutter is now based on Rizin, leaving Linux packagers with a fairly complicated conundrum that basically requires value judgements to resolve. --- I can only imagine that somebody is going to be upset by some of what I'm doing here, but please understand that I am simply trying to figure out what is going on. I have a strong feeling that there might be a lot more going on here that will surface later on. As far as attempts to fork a project based on non-technical disagreements, Rizin seems well-positioned, with control over Cutter and some core contributors on board. Let's see what happens next... For now, I am very likely to continue using r2, at least until Linux packagers decide to switch. They might as Cutter's choice is likely going to force the issue. --- Yet another weird sidenote. I think PR #17980 discussion is full of interesting nuance. User "FFY00," Filipe Laíns, created this PR. They appear to have contributed to Radare2 once in the past to add a small feature in 2017 (#9054.) They don't appear to have contributed to Rizin yet. User "FFY00," Filipe Laíns says: > @trufae this is what people are referring to when they criticize radare2. People are not out to get you, and do not hate radare2 just because... They are referring to this kind of behavior, which is harmful to others. This is some solid evidence that there is some kind of reputation and pre-existing conflict regarding pancake's conduct (note that @trufae appears to be another Github account of pancakes?) Continuing, user "FFY00," Filipe Laíns says: > I don't understand how having these stupid sentences show up when you start the program is worth possibly hurting users. This is a particularly strange sentence because they are, as far as I can tell, not shown at startup by default, and haven't been for years. In fact, their own commit description seems to be aware: > Even if they are not active by default, they should have no place here if you are trying to be a welcoming project. I have no idea what to conclude from this. It must just be an accident.
In Rizin – a free and open-source Reverse Engineering framework
They mentioned WinDbg and OllyDbg but both are quirks of the past (except WinDbg usage for kernel debugging), and there's a better tool for this - x32dbg/x64dbg[1]. It's open-source, unlike WinDbg and actively developed, unlike OllyDbg. Moreover, recently we worked a lot on improving Windows support in radare2 [2] and Cutter[3]. Most of our fixes should land in the upcoming 4.5.0[4] release. This summer one of our GSoC students works on improving reversible debugging [5] feature as well. And of course, both integrated with Frida as well - see r2frida plugin[6]. [1] https://x64dbg.com/ [2] https://github.com/radareorg/radare2 [3] https://github.com/radareorg/cutter [4] https://github.com/radareorg/radare2/milestone/51 [5] https://www.radare.org/gsoc/2020/ideas.html#title_10 [6] https://github.com/nowsecure/r2frida
In Using Frida for Windows Reverse Engineering
Working hard on Cutter, an open-source, free and libre Reverse Engineering project. It's cross platform and supports tons of architectures. A debugger was recently introduced, as well as native integration with multiple Decompilers https://cutter.re https://github.com/radareorg/cutter using it recently to reverse engineering some Gameboy ROMs, embedded devices and the usual x86 malware hopefully more people will come to work on this great project :)
In Ask HN: What's your quarantine side project?
I don't get an excitement. There is already IDA Pro and Binary Ninja, developing at a big pace and with actual support. Moreover, there is FOSS radare2[1] and Cutter[2], that also being developed at crazy speed. We have even work in progress decompiler radeco[3][4], though there is still a lot to be done. If people would contribute - there is a lot of time until March (time of GHIDRA release). [1] https://github.com/radare/radare2 [2] https://github.com/radareorg/cutter [3] https://github.com/radareorg/radeco [4] https://github.com/radareorg/radeco-lib
In NSA to Release Their Reverse Engineering Framework GHIDRA to Public at RSA
Sorry for highjacking your thread, but since the subject of reverse engineering is very close, writing it here. Radare2 project is famous to be blind users friendly, but we want the same thing for Cutter also [1]. If you know how to improve radare2 expierence too, don't hesitate to open an issue on our GitHub [2]. [1] https://github.com/radareorg/cutter/issues/889 [2] https://github.com/radare/radare2/issues
In Ask HN: Blind programmers, what can I do to make my code easier for you?
I've been picking up the basics in the past few months - I started out with playing around with some open source tools (radare2/Cutter), and then watching Josh Stroschein's introductory course on PluralSight [1]. The course is more Windows oriented but that's alright for the basics. Then, I asked my friend to make me a really basic CrackMe challenge [2]. Solving this was where most of the real learning took place. The tool I have been learning is Cutter [3], which is the official GUI for radare2. It's a feature-rich and open-source tool that allows you to reverse engineer without the licensing/price restrictions of the more well-known paid/closed-source tools. To help concrete this new knowledge, I'm currently working on a 3-part introduction to reverse engineering with Cutter series, part 1 of which is out so far [4]. Something that I've
Read the rest
found very useful for learning is to analyse your own binary rather than someone else's. Just write basic C++ programs ("What's your name?", calculator, etc - almost as if you're learning programming from scratch again), compile and then reverse engineer them. Having full knowledge of what the binary does and how it works allows you to focus on understanding the technical details (registers, stack, etc) rather than jumping straight in at the deep end with a mystery binary. Once you've got your head around how a basic binary works, the knowledge is very transferable to binaries where you don't have the source code. [1] https://www.pluralsight.com/courses/reverse-engineering-gett... [2] https://github.com/jamieweb/crackme-challenge Looking at source.cpp may reveal the solution, so be careful! Get a trusted friend to audit the code first if you are concerned about its legitimacy. [3] https://github.com/radareorg/cutter [4] https://www.jamieweb.net/blog/radare2-cutter-part-1-key-term...
In Ask HN: What books/tutorials/articles to read to get into reverse engineering?
Some free quality resources, ready to use: - Intel CPU programming guide https://www.intel.com/content/dam/www/public/us/en/documents... - Calling conventions https://en.wikipedia.org/wiki/X86_calling_conventions https://en.wikibooks.org/wiki/X86_Disassembly/Calling_Conven... - Web compiler output viewer https://godbolt.org/ - Operation code (opcode) reference http://ref.x86asm.net/ - Disassembler/debugger https://github.com/eteran/edb-debugger, https://x64dbg.com - Disassembler/Reverse engineering tools http://hte.sourceforge.net/ https://github.com/radareorg/cutter And this: https://github.com/codilime/veles (binary analysis tool)
In X86 assembly doesn’t have to be scary

Showing the 15 most recent of 21 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.