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

Feature Proposal: Alternative Interfaces #92

Open
jtpereyda opened this issue Aug 18, 2015 · 0 comments
Open

Feature Proposal: Alternative Interfaces #92

jtpereyda opened this issue Aug 18, 2015 · 0 comments

Comments

@jtpereyda
Copy link
Contributor

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.

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

No branches or pull requests

1 participant