search

ainfosec / FISSURE

The RF and reverse engineering framework for everyone. Follow and ★ to show your support!
https://twitter.com/FissureRF
GNU General Public License v3.0
1.56k stars 85 forks source link

Distinguish between Multiple HackRFs #7

Closed cpoore1 closed 2 years ago

cpoore1 commented 2 years ago

Expected Behavior

Assign the HackRF ID to distinguish between multiple HackRFs. Assign the values using the hardware buttons for the components, pass it to the attacks and other flow graphs, ignore it or use something like hackrf=0 if the ID is not specified.

Current Behavior

No way to distinguish multiple HackRFs other than unplugging or the automatic assignment for one that is not running.

Steps to Reproduce

  1. Click hardware button
  2. Select HackRF
  3. Nothing to choose

Context

Discussed in https://github.com/ainfosec/FISSURE/discussions/6

Originally posted by **joereith** August 19, 2022 * Distinguish between multiple hackrf devices (serial?) I think this would be a nice feature to have seeing as the open source releasing of FISSURE is going to draw a lot of attention. Once people start to use it they will most likely be connecting all sorts of SDR's and giving FISSURE a spin. This will allow the easy visual separation of hackrf's by serial number to be able to assign individually to individual components. Having a list or dropdown box containing each detected hackrf in the GUI will ensure people are selecting the proper hackrf.
cpoore1 commented 2 years ago

I am using the serial number from hackrf_info and dropping the leading zeros. I added functionality to the Probe and Guess buttons. If you click more than once on Guess it will cycle through them. All the flow graphs appear to distinguish by serial number. You may have to reload an attack to get the serial number to update if you just changed it.

One exception is for Inspection flow graphs with GUIs. Those are special because I am unable to change the values of the variables prior to loading it like I do with the flow graphs without GUIs. It's probably the same deal for flow graph attacks with GUIs. That can be a whole new issue I have to work on.