Support all analysis info required for Diaphora and create a script to extract

[radare]

What is required:

• Name of the function
• Number of nodes & edges of the function
• In and out-degree of the function
• Size in bytes
• Number of assembly instructions
• The mnemonics (not the instruction)
• The names referenced (strings and other constants)
• The function's prototype
• The comment of the function if any
• The pseudo-code (decompiled code) of the function if any
• The assembly dump and the relative virtual address.

• Script easy to use to extract those information

[joxeankoret]

Oh! And some structure or whatever representing the control flow graph of each function.

[radare]

Can you specify the type of each field? array of strings, graph, etc? Except the the decompilation, r2 can provide the all this information. and the decompilation can be extracted by using the retdec plugin or pdc/radeco in the future if needed. Also, mark which of those fields are optional

[radare]

ref https://github.com/joxeankoret/diaphora/blob/master/diaphora.py#L1020

[radare]

Waiting for @joxeankoret to provide an interface class to fill it with r2pipe magic

[jvoisin]

Any updates about this?
Shall we defer it to 1.0, or write the interface ourselves ?

[radare]

I guess we should do everything. But its ok for 1.0

On 08 Oct 2015, at 19:38, jvoisin notifications@github.com wrote:

Any updates about this?
Shall we defer it to 1.0, or write the interface ourselves ?

—
Reply to this email directly or view it on GitHub.

[XVilka]

@sushant94 @oddcoder would be useful also for 'radare2 <-> radeco' interaction.

[radare]

see ?O to get the list of all the instructions.

[radare]

the inout degree is the number of xrefs and the number of refs? I think you can already have all the info you want from current r2. just need to chat a bit with you to confirm that

[joxeankoret]

One of the problems I'm facing: I have no idea how to, simply, get the number of edges in a function. That's it, for a function graph G = (V,E), where V = {A, B, C} and E = {(A,B), (A,C)}, I just want to know that there are 2 edges. What command should I use for that? The help of the appropriate command (I think) afi is none.

[radare]

https://twitter.com/trufae/status/793504061152690178

On 01 Nov 2016, at 16:56, Joxean notifications@github.com wrote:

One of the problems I'm facing: I have no idea how to, simply, get the number of edges in a function. That's it, for a function graph G = (V,E), where V = {A, B, C} and E = {(A,B), (A,C)}, I just want to know that there 2 edges. What command should I use for that? The help of the appropriate command (I think) afi is none.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub #2742 (comment), or mute the thread https://github.com/notifications/unsubscribe-auth/AA3-lgKp1SUT_p5fZNGX0Pv99U1Kb_jiks5q52E9gaJpZM4E_eoC.

[lowlyw]

When you say V and E do you mean for the BBS in a function, or its in and
out connectivity to other functions? afi can give this info

On Nov 1, 2016 10:49 AM, "radare" notifications@github.com wrote:

https://twitter.com/trufae/status/793504061152690178

On 01 Nov 2016, at 16:56, Joxean notifications@github.com wrote:

One of the problems I'm facing: I have no idea how to, simply, get the
number of edges in a function. That's it, for a function graph G = (V,E),
where V = {A, B, C} and E = {(A,B), (A,C)}, I just want to know that there
2 edges. What command should I use for that? The help of the appropriate
command (I think) afi is none.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <
https://github.com/radare/radare2/issues/2742#issuecomment-257605524>, or
mute the thread <https://github.com/notifications/unsubscribe-
auth/AA3-lgKp1SUT_p5fZNGX0Pv99U1Kb_jiks5q52E9gaJpZM4E_eoC>.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#2742 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATaD6K9JUaXh-ccwFf9PwRFP9FtCrbYxks5q53usgaJpZM4E_eoC
.

[joxeankoret]

With V I mean vertex (nodes, basic blocks) and with E I mean Edges (connections between basic blocks). Anyway, that part is already implemented, thanks to @radare.

[Maijin]

All those requirements are fullfilled, what is remaining for this to happen @joxeankoret

[joxeankoret]

GUI support, mainly. Even supposing that I can port the internal export logic, there is no way I can display the results anywhere unless I create myself a new independent GUI.

[radare]

Buy a mac

…

On 12 Mar 2017, at 12:03, Joxean ***@***.***> wrote: GUI support, mainly. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[radare]

No srsly. Cant you just make a command line interface? Visual mode should be enough for most of that or at least a batch mode

…

On 12 Mar 2017, at 12:03, Joxean ***@***.***> wrote: GUI support, mainly. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[joxeankoret]

The Visual mode is cool, but non practical for diffing, I guess. Command line diffing? For example, I had a project where many functions had hundreds and even thousands of basic blocks. How am I supposed to analyse it with a command line version? No, you need a graph view with an overview or something similar.

That said, one Diaphora's side project is to create an independent GUI tool.

[radare]

is you create proper primitives the gui will be a separate part totally independent from the diffing engine and the backend source. so it doesnt matters if its a gui or a cli or a cui. i understand a proper gui is needed for managing this kind of things for big projects, but that’s not a reason for blocking access to this, mainly because you cant test graphical apps.. well you can but its silly and having stuff done without tests is dangerous

…

On 13 Mar 2017, at 17:36, Joxean ***@***.***> wrote: The Visual mode is cool, but non practical for diffing, I guess. Command line diffing? For example, I had a project where many functions had hundreds and even thousands of basic blocks. How am I supposed to analyse it with a command line version? No, you need a graph view with an overview or something similar. That said, one Diaphora's side project is to create an independent GUI tool. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2742 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA3-lmIjw0YpKWLZd84WM0pnQDqhtlb4ks5rlXB-gaJpZM4E_eoC>.

[Maijin]

• 1 for having the info available from CLI so we can test.

[joxeankoret]

Writing an exporter should be rather easy. I will start with this part.

[XVilka]

Can this be closed? Since it's completely done.

[XVilka]

@radare so what do you think? everything on radare2 side is ready/

[radare]

Yes i think we can close this issue and open another one to write the script that exposes all that info instead. Tired of waiting, this stupid python script is taking more than 2 years to be implemented.