Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Exact file format for Daredevil #11

Open
ChipsSpectre opened this issue Mar 7, 2018 · 1 comment
Open

Exact file format for Daredevil #11

ChipsSpectre opened this issue Mar 7, 2018 · 1 comment
Labels

Comments

@ChipsSpectre
Copy link

Hi Guys,

I want to convert my own memory traces (in a custom format) to the
format that Daredevil supports.

Unfortunately, I could not find the exact specification,
in which order/which attributes are required to run DareDevil.

In Deadpool, a function bin2daredevil() is provided in deadpool_dca.py
that is able to convert TracerGrind or TracerPIN data to the DareDevil
format. (Using this technique, I could reproduce the whitebox samples
of the Deadpool repository).

Is there an exact specification of the DareDevil file format?

Best regards
Chips

@doegox
Copy link
Contributor

doegox commented Mar 8, 2018

Hi @ChipsSpectre

To create a set of traces for Daredevil, you need:

  • one config file that describes how the data is provided, see https://github.com/SideChannelMarvels/Daredevil/blob/master/CONFIG
  • one trace file (see [Traces] in CONFIG) which is just the raw samples without any further formatting than their value (e.g. 32b float, 8b int, etc). transpose=true if you provide each trace one after the other one (which is typically the case).
  • one input or output file (see [Guesses] in CONFIG) which is just each 16b block appended, also transpose=true)

See also https://github.com/SideChannelMarvels/Daredevil/blob/master/trs2daredevil.py

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants