Skip to content

Feature Proposal: Alternative Interfaces #92

@jtpereyda

Description

@jtpereyda

I'm working on a way to switch out alternative interfaces. This would open the door to serial, radio, smoke signals, etc. as fuzzing mediums.

I need to do this for my own tests, but am hoping to share the extensibility changes.

  • The basic plan is to refactor sessions.py such that the Target class contains all of the medium-specific connection code.
  • From there it should be easy to subclass Target as needed for future interfaces.

I think @Fitblip alluded to moving away from pcaps for record-keeping in another issue. This will be a good time to do so -- pcaps may be a lot harder to get for alternative interfaces. For now, I plan to add some kind of logging mechanism to the Target class, such that all sent and received data is recorded. Action plan:

  • Add logging mechanism to Target class
  • Supplement but don't [yet] replace netmon.

Input welcome.

Edit: I actually did this a while ago and then lost my changes, so I know this basically works. I'm looking for input though since it's a significant new feature.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions