Improvements and features
- Cameradar can now access cameras with both basic and digest authentication methods
- Previously, only basic auth was supported due to 90% of cameras using it over digest
- A tool to automatically update the route dictionary has been added to the repository
- The Cameradar API is now much simpler to use (#209)
- UX has been improved
- Unit tests are now consistent (#210)
- End to end tests in CI are now more reliable
- Added custom routes
- Added a second camera
- Added two authentication methods in tests
Removed unmaintained documentation
- Contributing guide has been removed. It was very outdated and considering the low amount of contributions at the moment (🙁) I don't think it's worth the maintenance cost
- Documentation of the library in the readme was removed in favor of godoc. AFAIK no one uses cameradar as a library at the moment so I don't think it was necessary for it to be such a focus of the readme file.
Cameradar API
In the 3.0.0 version, the API of the cameradar API forces you to:
- Initialize, manipulate and clean a curl handle
- Call 5 or 6 functions from the library, with 4 to 6 arguments each, to perform a complete scan and attack process
- Print your own summary of the attack
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.
User Experience
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
Thanks to @rikosintie for his issue about digest authentication (#199)