Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Johannes vom Dorp
    @dorpvom
    Hello World
    gitshirokai
    @gitshirokai
    Hola
    Thomas Barabosch
    @tbarabosch
    @gitshirokai Welcome!
    gitshirokai
    @gitshirokai
    do u have a really good documentation ? I would be a master in firmware analysis
    Peter Weidenbach
    @weidenba
    You would like to have a documentation on how to use FACT?
    gitshirokai
    @gitshirokai
    no, a good doc on firmware analysis
    Johannes vom Dorp
    @dorpvom
    actually we don't have or are aware of a firmware analysis book or documentation. There is work on IOT/Hardware Security, but that's more focused on physical analysis/attacks
    If you are interested in howTos you can look into case studies. E.g. here, here or video here
    If you find something interesting, I'd be curious as well
    gitshirokai
    @gitshirokai
    @dorpvom thanks
    Chirag Jariwala
    @CJHackerz
    Hello
    I gotta say the concept behind entire software is intriguing
    I would like to contribute as Python dev, all though I am have never worked on big project but if given correct guidance
    Chirag Jariwala
    @CJHackerz
    I can start implementing any ideas and new features that will be coming my mind in future
    I know the all basics of python and all, also I know how docker works but since the code base is big enough I am already confused from where I can start
    Johannes vom Dorp
    @dorpvom
    Hi, nice to hear that. There's lots of possibilities for working on FACT. I can have a look at our internal issue board to offer suggestions. Otherwise a safe choice for a first project is to build a simple analysis plugin.
    You can use that to look at all the helper functions we have build, e.g. for filesystem interaction, since there is not such a thing as a manual for incorporating the existing work.
    Another useful entry point is looking at the REST API. Not all functionality found via the GUI is implemented there. E.g. there is no endpoint for system workload monitoring and for the statistics
    Implementing some of this requires an idea of how to work with flask but offers valuable insight into the interaction with FACT database interfaces
    Johannes vom Dorp
    @dorpvom
    I'll update regarding open feature requests when I'm next in office
    IoT-junkrat
    @IoT-junkrat
    Hey guys. I want to ask here to see if you have the same behavior, before I open an official issue or debug my FACT instance.
    Problem: When I see a "private key found" tag on the FACT UI for a firmware and curl the API for that UID, I would expect an output in "crypto_material". Unfortunately, I just get an empty summary.
    Is that the case for you as well? The firmware that was initially uploaded is a ZIP file.
    Jörg Stucke
    @jstucke
    Hi, I can confirm this. I will take a look at it.
    Jörg Stucke
    @jstucke
    This seems to be more of a case of missing documentation. It should work if you add a ?summary=true to the end of the url (i.e. curl 'http://localhost:5000/rest/firmware/<UID>?summary=true' -X GET)
    IoT-junkrat
    @IoT-junkrat
    Works like a charm! Thanks for helping @jstucke :)
    stl314159
    @stl314159
    I'm curious what the motivation is for including the file size in the UID? Why SHA256_FILESIZE instead of just SHA256?
    Peter Weidenbach
    @weidenba
    @stl314159 SHA256 should work in 99% of the cases. However, there might occur collisions regarding the estimated number of files in the database. This means, there might be two different files having the same hash value. The filesize should reduce the risk of collisions. By the way, this technique is used by clamav as well.
    stl314159
    @stl314159
    Thanks for the explanation.