Reverse Engineering

Description

Please describe what are you missing or wanting to be improved
Recently I read a new syntax coloring technique for programing languages. Instead of highlighting grammar, highlight the things you are likely to mistake. So make sure strcpy and strncpy are easily distinguishable by their color. It would be cool to apply this to immediate values in assembly and the ? command

There is rz_cons_html_filter() call in src/core/Cutter.cpp that has output depending on the internal state of the RzCons. It should be substituted with reading the JSON output from rz_core_print_disasm_json() instead.

App Attest allows your app to attach a hardware-backed assertion as a part of the request. Your server can use assertion to verify the request came from your genuine app, on a genuine Apple device.

https://developer.apple.com/videos/play/wwdc2021/10244/

https://developer.apple.com/documentation/devicecheck/assessing_fraud_risk

https://developer.apple.com/documentation/bundleresources/entit

Tl;dr: Use the workaround from https://github.com/pwndbg/pwndbg/pull/322/files only for broken gdb versions

When class/field/member modifier groups are displayed, its a stack of colored shapes.

It would be useful to have on-hover capabilities for these groups to complain the flags enabled in each group.

See AccessFlags for the list of all flags.

It would be u