Move theme selection in the disassembly options menu with font selection

The format option is not implemented yet. I suppose it should set file.type. Does that make sense?

Remove Help->License duplicate with about

No need of special implementation on r2 side you can do r2 http://google.com already

probably a selector in this menu^ by default on "file on disk" and with the following IO which are the one that doesn't require Cutter refactoring:

• http
• ihex
• ipa
• apk

Use oLj

Additionally to the loader menu already done:

Add a menu option to load a PDB after the binary have been loaded

  e io.va = false

followed by:

  pc     C
  pc*    print 'wx' r2 commands
  pch    C half-words (2 byte)
  pcw    C words (4 byte)
  pcd    C dwords (8 byte)
  pca    GAS .byte blob
  pcA    .bytes with instructions in comments
  pcs    string
  pcS    shellscript that reconstructs the bin
  pcj    json
  pcJ    javascript
  pcp    python

 $s # for filesize
 @ 0 # for beginning of size

Into file -> exports -> code then in the save menu just give the user capability to choose formats in a droplist, adding the default extension accordingly.

Example python: filename.py

Is there a way to attach cutter to live processes?

Like Neovim did: https://github.com/neovim/neovim/releases

Somehow they are able to push changes to the only one release instead of creating new ones every commit.

To be able to

• Scroll different parts of same disasm
• To view disasm of another file (may be for diffing mode?)
• Same for hex view
• Or one panel is for disasm and another - for graph
• Or disasm + notes (notepad)

Add ; for shortcut of right click add comment

Appveyor build

Use base64 for comment like CCu base64:AA==

To avoid @ injection

Move theme selection in a droplist and in Disassembly options menu

ping @thestr4ng3r

Obviously one can organize the panels as one wishes, however I believe it would be better to have the functions panel on the left per default.
What do you think?

Idea is to integrate jupyter notebook in two-way interaction with r2 core inside the r2 GUI.
There are widgets support in Jupyter Notebook - see http://jupyter.org/widgets.html

See about low-level widgets interaction here http://ipywidgets.readthedocs.io/en/latest/examples/Widget%20Low%20Level.html

Creating widget on the fly inside the Jupyter Notebook https://blog.dominodatalab.com/interactive-dashboards-in-jupyter/

Angr + IPython https://apps.sandstorm.io/app/cxp85aey2qrdqvxja1zgrs0tyzq7s55qwqdwqgz12k036s3rc1yh

Check the IDA + IPython plugins:

https://github.com/james91b/ida_ipython
https://github.com/eset/ipyida
https://github.com/tmr232/Sark

Use cases

1. Writing text in the markdown format

2. Including images

3. Attaching files (images, pdfs, textfiles)

4. Simple embedded r2pipe command line (ipython + r2pipe.py imported)

5. Some widgets from r2 GUI available embedded in jupyter nodebook - e.g. graph, so you'll be able to run "afg [funcname]" to get the graph of the function, embedded in the notebook - see example of http://nbviewer.jupyter.org/github/james91b/ida_ipython/blob/master/notebook/examples/Sark%20Snapshots.ipynb
   But keep in mind, that this example is poor - because it's just a snapshot. Embedding full-feature graph is nicer.

6. Functions entropy (or similar characteristics) - see http://nbviewer.jupyter.org/github/james91b/ida_ipython/blob/master/notebook/examples/Function%20Entropy.ipynb

7. Machine learning and data analysis:

   • http://www.kdnuggets.com/2016/04/top-10-ipython-nb-tutorials.html
   • https://dev.socrata.com/blog/2016/02/01/pandas-and-jupyter-notebook.html
   • https://blog.treasuredata.com/blog/2015/06/23/data-science-101-interactive-analysis-with-jupyter-pandas-and-treasure-data/

Widgets information

https://github.com/ipython/ipython/wiki/Widgets

Example of the plugin and custom widget for Jupyter - SparkMonitor https://krishnan-r.github.io/sparkmonitor/

Double click in strings, relocs, imports, symbols etc. is broken

• Add space key to switch between graph and disassembly view
• Remove weird behaviours (like switching from disassembly view to graph view when clicking on a function, seeking, etc.)

Adding the first item should help with the second one.

ls.file.zip

The address should say: main (0x00402a2c) instead of just 0x00402a2c

To save the project in a different directory

The dark theme option is still present, but it's not very reliable. It should update every widget and set it's style to the dark one. Also it should change the disassembly colors, etc.

• The arrow buttons are white/black (On the darker background, they look inverted.).
• Most list's selected item/hover colors are explicitly set and don't necessarily match dark themes.
• Disassembly color presets are not perfect yet. Specified in Configuration::loadDefaultTheme() and Configuration::loadDarkTheme()
• The background of the window borders within Cutter is gray/white.
• Tabbed views (e.g. Dashboard | Disassembly | Graph..., or Sections | Comments) are gray/white.
• The dashboard is gray/white.
• The headers of the lists with multiple columns (e.g. the sections window in the bottom left) are gray/white.
• The sections chart has a white background.
• The opcode description is white/black.

When you order the functions by name, it does not order them correctly. Fix that.

After our last thread regarding getting Homebrew in place and resolving the Travis issues with the question of what needs to be done in order to get Travis moving, I meandered over to see what may be going on and found the thread to be gone. After close inspection I discovered that the project had been moved / forked over here. While this seems appropriate, I had hoped that we could get some insight as to why this move was made and some of those threads we were discussing issues on vanished.

• Implement up scrolling
• Fix down scrolling (some artifacts / extra spaces)
  BONUS
• Split readDisasm into pd -50 and pd 50 so it the view does not start at current seek, but a bit before (add some context to current offset)

Loading a PDB replace the current bin by the pdb

Add Right click rename flag used at cursor, same as V -> d -> n.

Will allow renaming of call, jmp, local, var, str etc. renaming

Merge https://github.com/radareorg/cutter && https://github.com/radareorg/cutter_win32 repositories

• Colored assembly (Use Highlighter from disassembly view and make it compliant with x64dbg RichText)
• Remove black dots in front of assembly
• Escape to go back
• Right click context menu
• Double click on function
• Show comments (requires radare2 agj update)

I believe it is useless. If not check what is used from there and maybe use r2 API rather than the web server.

Change immediate base:
| ahi b set base to binary
| ahi d set base to decimal
| ahi h set base to hexadecimal
| ahi o set base to octal
| ahi i set base to IP address
| ahi S set base to syscall
| ahi s set base to string
| aho foo a0,33 replace opcode string

sub rsp, 0x628
>ahi 10
sub rsp, 1576

Some files are lowercase, some are camel case. Be consistent.

The thing is, you might want to use radare2 from the command line for your daily tasks, so you would use master. However you might also want to use cutter sometimes but the version might mismatch from the one which is stable with cutter.

• Install/Copy/Whatever radare2 from cutter submodule in a separate folder (not with default ./sys/install.sh)
• On startup set PATH according to the previous installation

Add name on top of function in graph:

And add the prototype the information available in radare2 (radareorg/radare2#8785):

• Change format words, dwords, qwords, ..(pxh, pxw, pxq) on right click (see px?)
• Scrolling by line
• hex.compact
• hex.comments (pxc command)
• hex.pairs (it's set to false by default in cutter, but we should make it configurable for the user)
• Use same disassembly architecture in parsing panel as the one used by the opened file by default
• Hashes configurable in Hexdump -> information -> bytes info
• Endianess
• Colors hexdump
• Implement write operations (wo?) (see #715)

• Add ability to always align (like now aligned on 0) or never align (stand at current seek)
• Show where current seek it
• show flags (pxa command) (not compatible-yet with hex.compact radareorg/radare2#8957)
• Hexdump is too wide #149
• Place separators between areas to visually split them
• Synchronize selection for hex-data and ASCII areas
• Change number of columns on right click hex.cols
• Add a button to close the side bar of the hexdump (see #636)
• Add "right Click > Select Block" to the Hex Widget (see #761)

Offsets are visibile at first, ihmo we should only see functions names and scroll a bit to the right if you need the offset.

I think it requires a fix of ecj on Windows, at least some investigation and a proper fix.

Here are the one I suggest for the first iteration

| /cj jmp [esp]         search for asm code
| /cj instr1;instr2   search for instruction 'instr1' followed by 'instr2'
| /j foo\x00           search for string 'foo\0' (json output)
| /xj ff0033            search for hex string

A simple windows showing results that can be clickable like the x-ref windows

• Add space bar shortcut to switch between both
• Add a mechanism so that when there's no graph to display it switches to the Disassembly

Monospace is not a valid font for stock Mac.
Use "Andale Mono" for Mac, or Courier or maybe use the ones that were bundled with iaito before.
Or just use QFontDatabase::systemFont(QFontDatabase::FixedFont) if it works

Add asm.describe as a view options

I thought https://github.com/radareorg/cutter/pull/33 was ok but it seems not.
It fails to find make install. CC @SiebelsTim

I think we should destroy the MemoryWidget class and split it into other widgets.
The graph view has already its own Widget, we should do the same for the assembly and hex view.

Add font/font size selector in a menu

It takes a load of space (~80mb) in the release...

Widgets still using QWebEngine:

• Dashboard
• PreviewWidget
• SidebarWidget

• Remove from Travis
• Remove from Appveyor

In my opinion we should refactor the code so that the unique MainWindow instance is accessible everywhere and remove it from Widgets constructors parameters.

xref menu contain the type

axtj sub.write_c42
[{"from":4294982639,"type":"d","opcode":"lea rax, sub.write_c42","fcn_addr":4294982616,"fcn_name":"sub.tputs_bd8"}]

Data, Code etc.