Skip to content

Releases: Ullaakut/cameradar

v2.1.0 File input

12 Nov 06:56
a8c1c8c
Compare
Choose a tag to compare

Enhancements

  • Cameradar can now take a file as an input, to make it easier to automatize #169
  • Issuing of RTSP SETUP requests to improve route & credential detection #182
  • Add more default credentials #176
  • Increase test coverage #159

Bugfixes

  • Fix multi address hosts #180
  • Fix nmap not taking multiple hosts in docker #177

v2.0.0: Cameradar is now a golang lib

19 Sep 06:02
Compare
Choose a tag to compare

Cameraccess

  • Cameraccess will serve as both a replacement for the old Cameradar C++ app and an example on how to use the Cameradar library
  • The Cameradar docker image uses Cameraccess as an entrypoint
  • Cameraccess is more performant than the old C++ Cameradar
  • Cameraccess has a better and more user-friendly UX than the old C++ Cameradar
  • The new docker image is somehow exactly two times lighter than the previous one (187MB vs 374MB)

Cameradar golang library

  • The Cameradar golang library provides the necessary tools to quickly build a tiny program to discover and attack RTSP streams, and makes it easy to build on top of it.
  • The code is much cleaner and all legacy code has been removed

v1.1.4 : Latest minor release before 2.0.0

18 Jan 13:09
Compare
Choose a tag to compare

v1.1.4

This version is the latest minor release before the 2.0.0. However, there might be other hotfixes coming after it if there are issues with the current state of Cameradar.

Minor changes :

  • Simplified use of Docker image
  • Renamed MySQL table name to be more explicit
  • Refactoring of the Golang functional tester done
  • The output was made more human readable
  • Added automatic code quality checks for pull requests
  • Added contribution documentation
  • Updated dictionaries to add user suggestions for Chinese cameras
  • Enhanced result.json file's format

Bugfixes :

  • Fixed a bug in the functional testing in which if the result.json file was not formatted correctly, the test failed but was still considered a success.

v1.1.3 : Minor fixes and testing in Travis CI

23 Nov 08:46
Compare
Choose a tag to compare

v1.1.3

Minor changes :

  • Added automatic pushes to DockerHub to the travis integration
  • Made travis configuration file better
  • Changed the package generation scripts to make them report errors
  • Removed old etix_rtsp_server binary from the test folder

Bugfixes :

  • Fixed an issue that made it mandatory to launch tests at least once so that they can work the second time
  • Fixed an issue that made the golang testing tool not compile in the testing script
  • Fixed an issue that made the golang testing tool sometimes ignore some tests
  • The previous known issue has been investigated and we don't know where it came from. However after a night of testing I have been unable to reproduce it, so I will consider it closed

v1.1.2

Minor changes :

  • Added travis integration
  • Added default environment value for Docker deployment
  • Updated docker image description with new easy usage
  • Updated README badges style (replaced flat with square-flat)
  • Build last package can now also generate a debug package if given the Debug command-line argument

Multithreading bugfixes

12 Nov 12:16
Compare
Choose a tag to compare

v1.1.1

Minor changes :

  • Removed unnecessary null pointer checks (thanks to https://github.com/elfring)
  • Updated package description
  • Removed debug message in CMake build
  • Added /ch01.264 to the URL dictionary in the deployment (Comelit default RTSP URL)
  • Updated tests partially (still needs work to make the code cleaner)
    • Variable names are now compliant with Golang best practices
    • JSON variable names are back to normal
    • Functions have been moved in more appropriate source files
    • Structure definitions have been moved in more appropriate source files
    • Source files have been renamed to be more relevant
    • JUnit output now considers each camera as a test case
    • JUnit output now contains errors which makes debugging much easier
  • Added header files where it was forgotten

Bugfixes :

  • Fixed an issue where if you loose your internet connection during thumbnail generation, FFMpeg would get stuck forever and thus Cameradar would never finish
  • Fixed an issue where multithreading could cause crashes
  • Fixed an issue where the routes dictionary was mistaken for the credentials dictionary
  • Fixed issues with the golang testing tool
    • Fixed automated camera generation
    • Fixed docker IP address resolution

Known issues :

  • There is an issue with Camera Emulation Server that makes it impossible for Cameradar to generate thumbnails, which is why right now the verification of the thumbnails presence is commented and it is assumed correct. It is probably an issue with GST-RTSP-Server but requires investigation.

Cameradar UX Update

29 Oct 07:03
Compare
Choose a tag to compare

v1.1.0

Major changes :

  • There are more command line options
    • Port can now be overridden in the command line
    • Subnet can now be overridden in the command line
  • Bruteforce is now multithreaded and will use as many threads as there are discovered cameras
  • Thumbnail generation is now multithreaded and will use as many threads as there are discovered cameras
  • There are now default configuration values in order to make cameradar easier to use

Minor changes :

  • The algorithms take external input into account (so that a 3rd party can change the DB to help Cameradar in real-time) and thus check the persistent data at each iteration
  • The default log level is now DEBUG instead of INFO
  • The bruteforce logs are now INFO instead of DEBUG
  • The thumbnail generation logs are now INFO instead of DEBUG

Bugs fixed

  • Fixed a bug in which the MySQL cache manager would consider a camera with known ids as having a valid path even if it weren't
  • Fixed a bug in which TCP RTSP streams would not generate thumbnails

v1.0.5

  • Fixed error in MySQL Cache Manager in which thumbnail generation on valid streams could not be done
  • Fixed potential crash in the case the machine running cameradar has no memory left to allocate space for the dynamic cache manager

Cameradar Patch Bundle

31 Aug 08:18
Compare
Choose a tag to compare

This patch fixes several problems in the 1.0.0 version

  • v1.0.1 : Updated to 16.04 & removed boost dependency
  • v1.0.2 : Fix issues with MySQL Cache Manager
  • v1.0.3 : Corrected GStreamer check
  • v1.0.4 : Fixed nmap package detection

Cameradar is tested and ready for production

21 Jun 09:02
Compare
Choose a tag to compare

Major changes :

  • Added functional testing

Camera Support Update

27 May 12:41
Compare
Choose a tag to compare

After doing some testing on a weirdly configured camera network in a far away Datacenter, I discovered that some Cameras needed a few tweaks to the Cameradar bruteforcing method in order to be accessed.

Major changes :

  • Cameradar can access Cameras that are configured to always send 400 Bad Requests responses

Minor changes :

  • Changed iterator name from it to stream in dumb cache manager to improve code readability

Bugfixes :

  • Cameradar no longer considers a timing out Camera as an accessible stream

MySQL CM Release

24 May 07:00
Compare
Choose a tag to compare

Version 0.2.0

Major changes :

  • MySQL Cache Manager

Minor changes :

  • Removed legacy code
  • Removed boost dependency
  • Improved debugging logs
  • Updated README

Version 0.2.1

Minor changes :

  • New docker deployment package
  • Updated README