Skip to content

Smart route discovery #414

Description

@Ullaakut

Description

Currently we naively always try every single route/cred combination, which is slow and could be made smarter.

If we can discover which vendor the camera was made by (see #413), then we could also have per-vendor profiles with routes and credentials for these cameras specifically. We would then try those dictionaries if the vendor is discovered, and run attacks the current way if not.

Additional Info

One tricky thing will be to think of how this will interact with the custom dictionary feature. Maybe instead of taking dictionaries in their current format, we could make a breaking change where all we would use is profiles instead, and the current dictionaries would become an all profile or something like this.

Not sure if making this a breaking change would actually cause trouble for users who rely on Cameradar in automation or scripts. If this is your case, please give me info in this ticket, would love to know more about how you use Cameradar and how we can make the transition as seamless as possible.

Code of Conduct

  • I agree to follow this project's Code of Conduct

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementEnhancement of existing features.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions