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 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 12:01:57 AM 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

7 sources
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
Some useful links: - https://github.com/radareorg/cutter (GUI for Radare2, free alternative to IDA) - https://github.com/eteran/edb-debugger (debugger, free alternative for OllyDbg) - http://hte.sourceforge.net/ (hex editor, disassembler, free alternative for Hiew) (open a binary, then press F6, select image format to get started, e.g: elf/image or pe/image) - http://ref.x86asm.net/coder64.html List of x86-64 opcodes - https://godbolt.org/ REPL that shows asm for given C/C++ code. - https://www.reddit.com/r/ReverseEngineering/
In Introduction to reverse engineering and assembly

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.