Cameradar hacks its way into RTSP videosurveillance cameras
Enhancements:
Bug fixes:
Misc:
In the 3.0.0 version, the API of the cameradar API forces you to:
In the 4.0.0 version, instead, you create a cameradar.Scanner
, pass it the options you want, and then simply call Scan
, Attack
and PrintStreams
on it. It is much more intuitive, clean and simple. The logic of the order in which to attack and many other things were moved from the client side to the API side.
The new interface is cleaner, provides a better picture of what is going on during the attack process and keeps the same attack summary as the previous interface has.
Its debug and verbose mode are significantly more readable than the previous --log
mode.
Thanks to @rikosintie for his issue about digest authentication (#199)
CAMERADAR_CUSTOM_CREDENTIALS
and CAMERADAR_CUSTOM_ROUTES
environment variables were no longer used, in favor of CAMERADAR_CUSTOM-CREDENTIALS
and CAMERADAR_CUSTOM-ROUTES
because of a regression introduced in v3.0.0. (#189)Discover
method5554
) #186nmap
#187This wasn't originally supposed to trigger a major release, but due to the refactors that became obvious once the old implementation of the discovery was improved, I had to make a few breaking changes to the cameradar library.
I don't think any developers use it, so I guess it isn't a big deal, but just in case, I'll bump up the major version.