Cameradar hacks its way into RTSP videosurveillance cameras

Overview

Cameradar

Coverage Status

An RTSP stream access tool that comes with its library

Cameradar allows you to

  • Detect open RTSP hosts on any accessible target host
  • Detect which device model is streaming
  • Launch automated dictionary attacks to get their stream route (e.g.: /live.sdp)
  • Launch automated dictionary attacks to get the username and password of the cameras
  • Retrieve a complete and user-friendly report of the results

Table of content

Docker Image for Cameradar

Install docker on your machine, and run the following command:

docker run -t ullaakut/cameradar -t <target> <other command-line options>

See command-line options.

e.g.: docker run -t ullaakut/cameradar -t 192.168.100.0/24 will scan the ports 554, 5554 and 8554 of hosts on the 192.168.100.0/24 subnetwork and attack the discovered RTSP streams and will output debug logs.

  • YOUR_TARGET can be a subnet (e.g.: 172.16.100.0/24), an IP (e.g.: 172.16.100.10), or a range of IPs (e.g.: 172.16.100.10-20).
  • If you want to get the precise results of the nmap scan in the form of an XML file, you can add -v /your/path:/tmp/cameradar_scan.xml to the docker run command, before ullaakut/cameradar.
  • If you use the -r and -c options to specify your custom dictionaries, make sure to also use a volume to add them to the docker container. Example: docker run -t -v /path/to/dictionaries/:/tmp/ ullaakut/cameradar -r /tmp/myroutes -c /tmp/mycredentials.json -t mytarget

Installing the binary on your machine

Only use this solution if for some reason using docker is not an option for you or if you want to locally build Cameradar on your machine.

Dependencies

Steps to install

  1. go get github.com/Ullaakut/cameradar
  2. cd $GOPATH/src/github.com/Ullaakut/cameradar
  3. cd cmd/cameradar
  4. go install

The cameradar binary is now in your $GOPATH/bin ready to be used. See command line options here.

Configuration

The RTSP port used for most cameras is 554, so you should probably specify 554 as one of the ports you scan. Not specifying any ports to the cameradar application will scan the 554, 5554 and 8554 ports.

docker run -t --net=host ullaakut/cameradar -p "18554,19000-19010" -t localhost will scan the ports 18554, and the range of ports between 19000 and 19010 on localhost.

You can use your own files for the credentials and routes dictionaries used to attack the cameras, but the Cameradar repository already gives you a good base that works with most cameras, in the /dictionaries folder.

docker run -t -v /my/folder/with/dictionaries:/tmp/dictionaries \
           ullaakut/cameradar \
           -r "/tmp/dictionaries/my_routes" \
           -c "/tmp/dictionaries/my_credentials.json" \
           -t 172.19.124.0/24

This will put the contents of your folder containing dictionaries in the docker image and will use it for the dictionary attack instead of the default dictionaries provided in the cameradar repo.

Check camera access

If you have VLC Media Player, you should be able to use the GUI or the command-line to connect to the RTSP stream using this format: rtsp://username:[email protected]:port/route

Command-line options

  • "-t, --targets": Set target. Required. Target can be a file (see instructions on how to format the file), an IP, an IP range, a subnetwork, or a combination of those. Example: --targets="192.168.1.72,192.168.1.74"
  • "-p, --ports": (Default: 554,5554,8554) Set custom ports.
  • "-s, --scan-speed": (Default: 4) Set custom nmap discovery presets to improve speed or accuracy. It's recommended to lower it if you are attempting to scan an unstable and slow network, or to increase it if on a very performant and reliable network. You might also want to keep it low to keep your discovery stealthy. See this for more info on the nmap timing templates.
  • "-I, --attack-interval": (Default: 0ms) Set custom interval after which an attack attempt without an answer should give up. It's recommended to increase it when attempting to scan unstable and slow networks or to decrease it on fast and reliable networks.
  • "-T, --timeout": (Default: 2000ms) Set custom timeout value after which an attack attempt without an answer should give up. It's recommended to increase it when attempting to scan unstable and slow networks or to decrease it on fast and reliable networks.
  • "-r, --custom-routes": (Default: <CAMERADAR_GOPATH>/dictionaries/routes) Set custom dictionary path for routes
  • "-c, --custom-credentials": (Default: <CAMERADAR_GOPATH>/dictionaries/credentials.json) Set custom dictionary path for credentials
  • "-o, --nmap-output": (Default: /tmp/cameradar_scan.xml) Set custom nmap output path
  • "-d, --debug": Enable debug logs
  • "-v, --verbose": Enable verbose curl logs (not recommended for most use)
  • "-h": Display the usage information

Format input file

The file can contain IPs, hostnames, IP ranges and subnetwork, separated by newlines. Example:

0.0.0.0
localhost
192.17.0.0/16
192.168.1.140-255
192.168.2-3.0-255

Environment Variables

CAMERADAR_TARGET

This variable is mandatory and specifies the target that cameradar should scan and attempt to access RTSP streams on.

Examples:

  • 172.16.100.0/24
  • 192.168.1.1
  • localhost
  • 192.168.1.140-255
  • 192.168.2-3.0-255

CAMERADAR_PORTS

This variable is optional and allows you to specify the ports on which to run the scans.

Default value: 554,5554,8554

It is recommended not to change these except if you are certain that cameras have been configured to stream RTSP over a different port. 99.9% of cameras are streaming on these ports.

CAMERADAR_NMAP_OUTPUT_FILE

This variable is optional and allows you to specify on which file nmap will write its output.

Default value: /tmp/cameradar_scan.xml

This can be useful only if you want to read the files yourself, if you don't want it to write in your /tmp folder, or if you want to use only the RunNmap function in cameradar, and do its parsing manually.

CAMERADAR_CUSTOM_ROUTES, CAMERADAR_CUSTOM_CREDENTIALS

These variables are optional, allowing to replace the default dictionaries with custom ones, for the dictionary attack.

Default values: <CAMERADAR_GOPATH>/dictionaries/routes and <CAMERADAR_GOPATH>/dictionaries/credentials.json

CAMERADAR_SCAN_SPEED

This optional variable allows you to set custom nmap discovery presets to improve speed or accuracy. It's recommended to lower it if you are attempting to scan an unstable and slow network, or to increase it if on a fast and reliable network. See this for more info on the nmap timing templates.

Default value: 4

CAMERADAR_ATTACK_INTERVAL

This optional variable allows you to set custom interval to wait between each attack in order to stay stealthy. It's recommended to increase it when attempting to scan a network that might be protected against bruteforce attacks. By default, there is no interval, in order to make attacks as fast as possible

Default value: 0ms

CAMERADAR_TIMEOUT

This optional variable allows you to set custom timeout value after which an attack attempt without an answer should give up. It's recommended to increase it when attempting to scan unstable and slow networks or to decrease it on fast and reliable networks.

Default value: 2000ms

CAMERADAR_LOGGING

This optional variable allows you to enable a more verbose output to have more information about what is going on.

It will output nmap results, cURL requests, etc.

Default: false

Contribution

Build

Docker build

To build the docker image, simply run docker build -t . cameradar in the root of the project.

Your image will be called cameradar and NOT ullaakut/cameradar.

Go build

  1. go get github.com/Ullaakut/cameradar
  2. cd $GOPATH/src/github.com/Ullaakut/cameradar
  3. cd cmd/cameradar
  4. go install

The cameradar binary is now in $GOPATH/bin/cameradar.

Frequently Asked Questions

Cameradar does not detect any camera!

That means that either your cameras are not streaming in RTSP or that they are not on the target you are scanning. In most cases, CCTV cameras will be on a private subnetwork, isolated from the internet. Use the -t option to specify your target. If you are sure you did everything right but it still does not work, please open an issue with details on the device you are trying to access 🙏

Cameradar detects my cameras, but does not manage to access them at all!

Maybe your cameras have been configured, and the credentials / URL have been changed. Cameradar only guesses using default constructor values if a custom dictionary is not provided. You can use your own dictionaries in which you just have to add your credentials and RTSP routes. To do that, see how the configuration works. Also, maybe your camera's credentials are not yet known, in which case if you find them it would be very nice to add them to the Cameradar dictionaries to help other people in the future.

What happened to the C++ version?

You can still find it under the 1.1.4 tag on this repo, however it was slower and less stable than the current version written in Golang. It is not recommended using it.

How to use the Cameradar library for my own project?

See the example in /cmd/cameradar. You just need to run go get github.com/Ullaakut/cameradar and to use the cameradar package in your code. You can find the documentation on godoc.

I want to scan my own localhost for some reason, and it does not work! What's going on?

Use the --net=host flag when launching the cameradar image, or use the binary by running go run cameradar/cameradar.go or installing it.

I don't see a colored output:(

You forgot the -t flag before ullaakut/cameradar in your command-line. This tells docker to allocate a pseudo-tty for cameradar, which makes it able to use colors.

I don't have a camera, but I'd like to try Cameradar!

Simply run docker run -p 8554:8554 -e RTSP_USERNAME=admin -e RTSP_PASSWORD=12345 -e RTSP_PORT=8554 ullaakut/rtspatt and then run cameradar, and it should guess that the username is admin and that the password is 12345. You can try this with any default constructor credentials (they can be found here).

What authentication types does Cameradar support?

Cameradar supports both basic and digest authentication.

Examples

Running cameradar on your own machine to scan for default ports

docker run --net=host -t ullaakut/cameradar -t localhost

Running cameradar with an input file, logs enabled on port 8554

docker run -v /tmp:/tmp --net=host -t ullaakut/cameradar -t /tmp/test.txt -p 8554

Running cameradar on a subnetwork with custom dictionaries, on ports 554, 5554 and 8554

docker run -v /tmp:/tmp --net=host -t ullaakut/cameradar -t 192.168.0.0/24 --custom-credentials="/tmp/dictionaries/credentials.json" --custom-routes="/tmp/dictionaries/routes" -p 554,5554,8554

License

Copyright 2019 Ullaakut

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Issues
  • Can't access camera with custom route

    Can't access camera with custom route

    Issue from @johny77g ( https://github.com/EtixLabs/cameradar/commit/cad7d24ccf068d7d45dcf9db746140ec716ee219#commitcomment-25169225 )

    Hi, I exposed my camera for a simple test with very simple setup username: admin, password: admin. Updated credentials.json and routes as below. With option -l the generated connections were following:

    DESCRIBE rtsp://:@x.x.x.x:x/tcp/av0_0 RTSP/1.0 (no usr and no login)
    DESCRIBE rtsp://:@x.x.x.x:x/udp/av0_0 RTSP/1.0 (no usr and no login)
    DESCRIBE rtsp://admin:[email protected]:/ RTSP/1.0 (no command from routes)
    

    BUT the right configuration was never generated. (I mean with: admin, admin, tcp/av0_0) Is it something wrong with my trial or some issue with attack.go file?

    ----------credentials.json----------------
    {
    "usernames": [
    "admin"
    ],
    
    "passwords" : [
    "admin"
    ]
    }
    --------------routes--------------------
    tcp/av0_0
    udp/av0_0
    
    bug 
    opened by Ullaakut 20
  • The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm/v7)

    The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm/v7)

    First, make sure that none of the open and closed issues is about the same issue as you are describing, and make sure to check the frequently asked questions in the README file. Then, replace the parts of this template that are between with the data relative to your issue.

    If you're reporting a bug, use the template below. Otherwise, delete this template and write your issue normally.

    Context

    Please select one:

    • [x] I use the docker image ullaakut/cameradar
    • [ ] I use my own build of the docker image
    • [ ] I use the pre-compiled binary
    • [ ] I use my own build of the binary
    • [ ] None of the above / I don't know

    Please select one:

    • [ ] I use a specific version:
    • [x] I use the latest commit of the master branch
    • [ ] I use the latest commit of the develop branch
    • [ ] I use a forked version of the repository:
    • [ ] I use a specific commit:

    Environment

    My operating system:

    • [ ] Windows
    • [ ] OSX
    • [x] Linux
    • [ ] Other

    OS version: Raspbian OS architecture: arm

    Issue

    I am trying to run this on a Raspberry Pi, but when I execute the command docker run --net=host -t ullaakut/cameradar -t localhost I get this error:

    WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm/v7) and no specific platform was requested
    standard_init_linux.go:219: exec user process caused: exec format error
    
    

    What was expected

    Image should run

    What happened

    Error

    Logs

    If your issue is with Cameradar's binary or docker image, please run it with -v to print verbose logs, and paste them here:

    WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm/v7) and no specific platform was requested
    standard_init_linux.go:219: exec user process caused: exec format error
    
    bug binary 
    opened by Heisenberg2980 20
  • Digest authentication no longer works

    Digest authentication no longer works

    Context

    Both binary and docker releases

    Any commit since digest authentication was added

    Environment

    Any OS

    Issue

    Making any requests with digest authentication causes the following issue:

    *   Trying 127.0.0.1:8554...
    * TCP_NODELAY set
    * Connected to 127.0.0.1 (127.0.0.1) port 8554 (#0)
    * Server auth using Digest with user 'ubnt'
    > DESCRIBE rtsp://ubnt:[email protected]:8554/live.sdp RTSP/1.0
    CSeq: 1
    Accept: application/sdp
    
    < RTSP/1.0 401 Unauthorized
    < CSeq: 1
    < WWW-Authenticate: Digest realm="GStreamer RTSP Server", nonce="3034e78651e4e61e"
    < Server: GStreamer RTSP server
    < Date: Sun, 12 Jan 2020 09:36:53 GMT
    <
    * Connection #0 to host 127.0.0.1 left intact
    * Issue another request to this URL: 'rtsp://ubnt:[email protected]:8554/live.sdp'
    * Protocol "rtsp" not supported or disabled in libcurl
    * Closing connection -1
    

    * Protocol "rtsp" not supported or disabled in libcurl

    While when using basic authentication or no authentication, streams are accessed without any issue, and this log never appears.

    bug 
    opened by vincyrei 18
  • Attack requests dropped

    Attack requests dropped

    When performing the attack (on my own network I get errors for the following Attacking routes of # streams...ok

    Perform failed: curl: RTSP CSeq mismatch or invalid CSeq Perform failed: curl: Failure from receiving data from the peer Attempting to detect authentication of # of streams...ok Perform failed: curl: Failure from receiving data from the peer Attacking credentials of # streams ...ok Perform failed: curl: RTSP CSeq mismatch or invalid CSeq Perform failed: curl: Failure from receiving data from the peer Validating that streams are accessible...ok Perform failed: curl: Failure from receiving data from the peer

    My question is are these normal error messages or did I mess up the installation?

    question 
    opened by dominionman12 18
  • Cameradar is not giving result properly

    Cameradar is not giving result properly

    Im using Cameradar from past 6 months it working fine but now i thing its having some issues with it. Im testing with RTSP IP having open port and also having default credentials which are present in dictionary Folder but it shows "Unable to attack empty list of targets " and when i open my rtsp link with default credentials in VLC it's working. so, i think there have some problem Cameradar. Please help me out. cam1

    Please select one:

    • [* ] I use the docker image ullaakut/cameradar **
    • [ ] I use my own build of the docker image
    • [ ] I use the pre-compiled binary
    • [ ] I use my own build of the binary
    • [ ] None of the above / I don't know

    Environment

    My operating system:

    • [ ] Windows
    • [ ] OSX
    • [* ] Linux
    • [ ] Other

    OS version: <ubuntu 16.04 > OS architecture: <64 bit>

    bug waiting for feedback 
    opened by Huan2gao 17
  • Timeouts during attack on IP Webcam android phone app

    Timeouts during attack on IP Webcam android phone app

    hi i have setup my android phone as my camera using the app called "IP Webcam", just to make sure that the camera is running i did a nmap scan to make sure the port is open as well like below:

    PORT STATE SERVICE 5554/tcp open sgi-esphttp MAC Address: 4C:77:41:43:A6:CD (Lenovo)

    than i ran the command:

    sudo docker run -t ullaakut/cameradar -t 192.168.1.0/24 -l and also this sudo docker run --net=host -t ullaakut/cameradar -t 0.0.0.0

    both commands outputs the same: ✖ No streams were found. Please make sure that your target is on an accessible network.

    my android phone is on the same network, i can access the camera through the browser, but cameradar cannot seem to find it.

    any suggestions?

    question waiting for feedback 
    opened by jepunband 16
  • Add feature to parse IP target list from text file

    Add feature to parse IP target list from text file

    Is It possible to create a TXT file with multiple Ip's and execute a massive scan? Thz

    help wanted optional good first issue feature blocked 
    opened by joaoantonio87 16
  • CURL Timeout Error - Debian Stretch (9.3) (aarch64) (Android chrooted env)

    CURL Timeout Error - Debian Stretch (9.3) (aarch64) (Android chrooted env)

    Hello

    First of all, I wanted to thank you for working on and maintaining such an interesting project. Looking forward to further releases and updates :).

    To keep it short. I recently stumbled upon cameradar while trying to build the perfect IoT pentesting environment on Android. Unfortunately however, I've faced some problems while trying to run it on my current environment. Here's my current scenario:

    After setting up a chrooted Debian environment on Android (8.0 Oreo) and setting up golang and the necessary compilation build tools, the compiled binary somehow gets confused when invoking libcurl functions. Here's precisely what happens while trying to run cameradar on the above mentioned environment

    https://drive.google.com/file/d/1fywQheMe10RJ0dkmQ_89Klbpr2BBbut0/view?usp=drivesdk

    (You'll have to excuse me but I didn't manage to find an easier way of sharing a screenshot )

    Basically, curl tries to connect to (rtsp://%user:%password:%macaddr/%route)

    I already tried debugging the binary through strace thinking that it was invoking curl through execv but to no avail.

    I still didn't manage to find out where the error culprit stands (libcurl invoked with erroneus parameters or simply libcurl failure)

    Hopefully you'll manage to find some time and look into it.

    Thanks in advance :)

    -D4N

    bug library 
    opened by D-4-N 16
  • Implement digest authentication

    Implement digest authentication

    First, make sure that none of the open and closed issues is about the same issue as you are describing, and make sure to check the frequently asked questions in the README file. Then, replace the parts of this template that are between with the data relative to your issue.

    If you're reporting a bug, use the template below. Otherwise, delete this template and write your issue normally.

    Context

    Please select one:

    • [x] I use the docker image ullaakut/cameradar
    • [ ] I use my own build of the docker image
    • [ ] I use the pre-compiled binary
    • [ ] I use my own build of the binary
    • [ ] None of the above / I don't know

    Please select one:

    • [ ] I use a specific version:
    • [x] I use the latest commit of the master branch
    • [ ] I use the latest commit of the develop branch
    • [ ] I use a forked version of the repository:
    • [ ] I use a specific commit:

    Environment

    My operating system:

    • [ ] Windows
    • [ ] OSX
    • [x] Linux
    • [ ] Other

    OS version: Ubuntu 18.04 OS architecture: 64bit Intel

    Issue

    401 Unauthorized from the camera

    What was expected?

    Successful connection

    What happened?

    Hello, I love this project! I am trying to figure out why it isn't working against an Aiphone camera. Below are the logs. The camera is at default with user/pass of aiphone/aiphone.

    I read the FAQ and a previous issue titled "can't detect camera feed". Both were very useful but I still can't figure out what I am doing wrong. Can you give me some tips to help troubleshoot? Thanks!

    If I copy this line from the logs and put it in vlc I get the stream: rtsp://aiphone:[email protected]:554/udp/unicast/aiphone_H264

    Here is the command I used to run Docker. docker run -t -v /home/mhubbard/Dropbox/03_Tools:/tmp/dictionaries ullaakut/cameradar -r "/tmp/dictionaries/rtsp.txt" -c "/tmp/dictionaries/my_credentials.json" -t 192.168.1.12 -l

    Here are the files in /home/mhubbard/Dropbox/03_Tools

    rtsp.txt

    udp/unicast/aiphone_H264
    

    my_credentials.json

    {
      "usernames": [
        "",
        "aiphone",
        "admin"
      ],
      "passwords" : [
        "",
        "aiphone",
        "V3ct0r88"
      ]
    }
    

    Logs

    If your issue is with Cameradar's binary or docker image, please run it with -l to print logs, and paste them here:

    ->docker run -t -v /home/mhubbard/Dropbox/03_Tools:/tmp/dictionaries ullaakut/cameradar -r "/tmp/dictionaries/rtsp.txt" -c "/tmp/dictionaries/my_credentials.json"  -t 192.168.1.12 -l
    * Expire in 0 ms for 6 (transfer 0xd90300)
    * Expire in 2000 ms for 8 (transfer 0xd90300)
    *   Trying 192.168.1.12...
    * TCP_NODELAY set
    * Expire in 200 ms for 4 (transfer 0xd90300)
    * Connected to 192.168.1.12 (192.168.1.12) port 554 (#0)
    > DESCRIBE rtsp://:@192.168.1.12:554/udp/unicast/aiphone_H264 RTSP/1.0
    CSeq: 1
    Accept: application/sdp
    
    < RTSP/1.0 401 Unauthorized
    < Server: Linux/2.6.32.17-davinci1 Ze-PRO
    < CSeq: 1
    < WWW-Authenticate: Digest realm="Secret", nonce="ODQ4MDguNDk3Mzk6NzQ3NTQ0OTk5"
    < 
    * Connection #0 to host 192.168.1.12 left intact
    * Expire in 0 ms for 6 (transfer 0xd9d060)
    * Expire in 2000 ms for 8 (transfer 0xd9d060)
    *   Trying 192.168.1.12...
    * TCP_NODELAY set
    * Expire in 200 ms for 4 (transfer 0xd9d060)
    * Connected to 192.168.1.12 (192.168.1.12) port 554 (#0)
    > DESCRIBE rtsp://:@192.168.1.12:554/udp/unicast/aiphone_H264 RTSP/1.0
    CSeq: 1
    Accept: application/sdp
    
    < RTSP/1.0 401 Unauthorized
    < Server: Linux/2.6.32.17-davinci1 Ze-PRO
    < CSeq: 1
    < WWW-Authenticate: Digest realm="Secret", nonce="ODQ4MDguNTExMjg6MTk5OTQ0OTk="
    < 
    * Connection #0 to host 192.168.1.12 left intact
    * Expire in 0 ms for 6 (transfer 0xda9bc0)
    * Expire in 2000 ms for 8 (transfer 0xda9bc0)
    *   Trying 192.168.1.12...
    * TCP_NODELAY set
    * Expire in 200 ms for 4 (transfer 0xda9bc0)
    * Connected to 192.168.1.12 (192.168.1.12) port 554 (#0)
    * Server auth using Basic with user ''
    > DESCRIBE rtsp://:[email protected]:554/udp/unicast/aiphone_H264 RTSP/1.0
    CSeq: 1
    Accept: application/sdp
    Authorization: Basic OmFpcGhvbmU=
    
    < RTSP/1.0 401 Unauthorized
    < Server: Linux/2.6.32.17-davinci1 Ze-PRO
    < CSeq: 1
    < WWW-Authenticate: Digest realm="Secret", nonce="ODQ4MDguNTE3NDg6MTI3NTc3ODU0Mw=="
    < 
    * Connection #0 to host 192.168.1.12 left intact
    * Expire in 0 ms for 6 (transfer 0xdb6760)
    * Expire in 2000 ms for 8 (transfer 0xdb6760)
    *   Trying 192.168.1.12...
    * TCP_NODELAY set
    * Expire in 200 ms for 4 (transfer 0xdb6760)
    * Connected to 192.168.1.12 (192.168.1.12) port 554 (#0)
    * Server auth using Basic with user ''
    > DESCRIBE rtsp://:[email protected]:554/udp/unicast/aiphone_H264 RTSP/1.0
    CSeq: 1
    Accept: application/sdp
    Authorization: Basic OlYzY3Qwcjg4
    
    < RTSP/1.0 401 Unauthorized
    < Server: Linux/2.6.32.17-davinci1 Ze-PRO
    < CSeq: 1
    < WWW-Authenticate: Digest realm="Secret", nonce="ODQ4MDguNTI0NDI6MTUyMDY5MDU1OA=="
    < 
    * Connection #0 to host 192.168.1.12 left intact
    * Expire in 0 ms for 6 (transfer 0xdc3300)
    * Expire in 2000 ms for 8 (transfer 0xdc3300)
    *   Trying 192.168.1.12...
    * TCP_NODELAY set
    * Expire in 200 ms for 4 (transfer 0xdc3300)
    * Connected to 192.168.1.12 (192.168.1.12) port 554 (#0)
    * Server auth using Basic with user 'aiphone'
    > DESCRIBE rtsp://aiphone:@192.168.1.12:554/udp/unicast/aiphone_H264 RTSP/1.0
    CSeq: 1
    Accept: application/sdp
    Authorization: Basic YWlwaG9uZTo=
    
    < RTSP/1.0 401 Unauthorized
    < Server: Linux/2.6.32.17-davinci1 Ze-PRO
    < CSeq: 1
    < WWW-Authenticate: Digest realm="Secret", nonce="ODQ4MDguNTMwNDg6MTkyMTI5MTY="
    < 
    * Connection #0 to host 192.168.1.12 left intact
    * Expire in 0 ms for 6 (transfer 0xdcfea0)
    * Expire in 2000 ms for 8 (transfer 0xdcfea0)
    *   Trying 192.168.1.12...
    * TCP_NODELAY set
    * Expire in 200 ms for 4 (transfer 0xdcfea0)
    * Connected to 192.168.1.12 (192.168.1.12) port 554 (#0)
    * Server auth using Basic with user 'aiphone'
    > DESCRIBE rtsp://aiphone:[email protected]:554/udp/unicast/aiphone_H264 RTSP/1.0
    CSeq: 1
    Accept: application/sdp
    Authorization: Basic YWlwaG9uZTphaXBob25l
    
    < RTSP/1.0 401 Unauthorized
    < Server: Linux/2.6.32.17-davinci1 Ze-PRO
    < CSeq: 1
    < WWW-Authenticate: Digest realm="Secret", nonce="ODQ4MDguNTM2Mzk6NTQ1OTExMzQz"
    < 
    * Connection #0 to host 192.168.1.12 left intact
    * Expire in 0 ms for 6 (transfer 0xddca80)
    * Expire in 2000 ms for 8 (transfer 0xddca80)
    *   Trying 192.168.1.12...
    * TCP_NODELAY set
    * Expire in 200 ms for 4 (transfer 0xddca80)
    * Connected to 192.168.1.12 (192.168.1.12) port 554 (#0)
    * Server auth using Basic with user 'aiphone'
    > DESCRIBE rtsp://aiphone:[email protected]:554/udp/unicast/aiphone_H264 RTSP/1.0
    CSeq: 1
    Accept: application/sdp
    Authorization: Basic YWlwaG9uZTpWM2N0MHI4OA==
    
    < RTSP/1.0 401 Unauthorized
    < Server: Linux/2.6.32.17-davinci1 Ze-PRO
    < CSeq: 1
    < WWW-Authenticate: Digest realm="Secret", nonce="ODQ4MDguNTQzNTE6MTY1ODg2MDUwOQ=="
    < 
    * Connection #0 to host 192.168.1.12 left intact
    * Expire in 0 ms for 6 (transfer 0xde9660)
    * Expire in 2000 ms for 8 (transfer 0xde9660)
    *   Trying 192.168.1.12...
    * TCP_NODELAY set
    * Expire in 200 ms for 4 (transfer 0xde9660)
    * Connected to 192.168.1.12 (192.168.1.12) port 554 (#0)
    * Server auth using Basic with user 'admin'
    > DESCRIBE rtsp://admin:@192.168.1.12:554/udp/unicast/aiphone_H264 RTSP/1.0
    CSeq: 1
    Accept: application/sdp
    Authorization: Basic YWRtaW46
    
    < RTSP/1.0 401 Unauthorized
    < Server: Linux/2.6.32.17-davinci1 Ze-PRO
    < CSeq: 1
    < WWW-Authenticate: Digest realm="Secret", nonce="ODQ4MDguNTQ5NTU6MTk3MjEyMzA1Ng=="
    < 
    * Connection #0 to host 192.168.1.12 left intact
    * Expire in 0 ms for 6 (transfer 0xdf6200)
    * Expire in 2000 ms for 8 (transfer 0xdf6200)
    *   Trying 192.168.1.12...
    * TCP_NODELAY set
    * Expire in 200 ms for 4 (transfer 0xdf6200)
    * Connected to 192.168.1.12 (192.168.1.12) port 554 (#0)
    * Server auth using Basic with user 'admin'
    > DESCRIBE rtsp://admin:[email protected]:554/udp/unicast/aiphone_H264 RTSP/1.0
    CSeq: 1
    Accept: application/sdp
    Authorization: Basic YWRtaW46YWlwaG9uZQ==
    
    < RTSP/1.0 401 Unauthorized
    < Server: Linux/2.6.32.17-davinci1 Ze-PRO
    < CSeq: 1
    < WWW-Authenticate: Digest realm="Secret", nonce="ODQ4MDguNTU1MzU6MTc4NDM2MDIyNg=="
    < 
    * Connection #0 to host 192.168.1.12 left intact
    * Expire in 0 ms for 6 (transfer 0xe02de0)
    * Expire in 2000 ms for 8 (transfer 0xe02de0)
    *   Trying 192.168.1.12...
    * TCP_NODELAY set
    * Expire in 200 ms for 4 (transfer 0xe02de0)
    * Connected to 192.168.1.12 (192.168.1.12) port 554 (#0)
    * Server auth using Basic with user 'admin'
    > DESCRIBE rtsp://admin:[email protected]:554/udp/unicast/aiphone_H264 RTSP/1.0
    CSeq: 1
    Accept: application/sdp
    Authorization: Basic YWRtaW46VjNjdDByODg=
    
    < RTSP/1.0 401 Unauthorized
    < Server: Linux/2.6.32.17-davinci1 Ze-PRO
    < CSeq: 1
    < WWW-Authenticate: Digest realm="Secret", nonce="ODQ4MDguNTYwODk6MzI4MDMxMDQ1"
    < 
    * Connection #0 to host 192.168.1.12 left intact
    * Expire in 0 ms for 6 (transfer 0xe0f9c0)
    * Expire in 2000 ms for 8 (transfer 0xe0f9c0)
    *   Trying 192.168.1.12...
    * TCP_NODELAY set
    * Expire in 200 ms for 4 (transfer 0xe0f9c0)
    * Connected to 192.168.1.12 (192.168.1.12) port 554 (#0)
    > DESCRIBE rtsp://:@192.168.1.12:554/udp/unicast/aiphone_H264 RTSP/1.0
    CSeq: 1
    Accept: application/sdp
    
    < RTSP/1.0 401 Unauthorized
    < Server: Linux/2.6.32.17-davinci1 Ze-PRO
    < CSeq: 1
    < WWW-Authenticate: Digest realm="Secret", nonce="ODQ4MDguNTY4NjY6MTc2NDgyNDU2OQ=="
    < 
    * Connection #0 to host 192.168.1.12 left intact
    * Expire in 0 ms for 6 (transfer 0xd8a920)
    * Expire in 2000 ms for 8 (transfer 0xd8a920)
    *   Trying 192.168.1.12...
    * TCP_NODELAY set
    * Expire in 200 ms for 4 (transfer 0xd8a920)
    * Connected to 192.168.1.12 (192.168.1.12) port 554 (#0)
    > SETUP rtsp://:@192.168.1.12:554/udp/unicast/aiphone_H264 RTSP/1.0
    CSeq: 1
    Transport: RTP/AVP;unicast;client_port=33332-33333
    
    < RTSP/1.0 401 Unauthorized
    < Server: Linux/2.6.32.17-davinci1 Ze-PRO
    < CSeq: 1
    < WWW-Authenticate: Digest realm="Secret", nonce="ODQ4MDguNTc0NjE6MTA1MDcxOTk0Nw=="
    < 
    * Connection #0 to host 192.168.1.12 left intact
    ✖	Admin panel URL:	http://192.168.1.12/ You can use this URL to try attacking the camera's admin panel instead.
    	Device model:		
    
    	Available:		✖
    	IP address:		192.168.1.12
    	RTSP port:		554
    	Username:		not found
    	Password:		not found
    	RTSP route:		/udp/unicast/aiphone_H264
    
    
    ✖ Streams were found but none were accessed. They are most likely configured with secure credentials and routes. You can try adding entries to the dictionary or generating your own in order to attempt a bruteforce attack on the cameras.
    
    
    binary library feature 
    opened by rikosintie 14
  • Improve route and credential detection by issuing RTSP SETUP Request

    Improve route and credential detection by issuing RTSP SETUP Request

    Hey @Ullaakut :)

    So I was testing some cameras around my neighbourhood and noticed something weird. Cameradar bases it's results on the response it gets from a RTSP DESCRIBE request and so far so good, it works and everything. The problem IMO Is that cameradar never checks to make sure the stream is actually available. This time I'm proposing a detection mechanism enhancement by issuing a second RTSP SETUP request and, thus validating that the credentials and route are actually accessible. Consider the following scenario

    cameradar -t xxx.xxx.xxx.xxx -T 5000 -l Output

    [email protected]:~# cameradar -t 192.168.100.64 -T 5000 -l
    command: nmap -T4 -A -p 554,8554 -oX /tmp/cameradar_scan.xml 192.168.100.6
    4
    
    Starting Nmap 7.40 ( https://nmap.org ) at 2018-07-06 08:30 CEST
    Nmap scan report for 192.168.100.64
    Host is up (0.014s latency).
    PORT     STATE  SERVICE  VERSION
    554/tcp  open   rtsp
    | fingerprint-strings:
    |   FourOhFourRequest:
    |     RTSP/1.0 505 RTSP Version Not Supported
    |     Server: ALi feng/2.1.0_rc1
    |     Date: Week 4, 1 Mon0 0070 22:12:16 GMT
    |   GetRequest:
    |     RTSP/1.0 505 RTSP Version Not Supported
    |     Server: ALi feng/2.1.0_rc1
    |     Date: Week 4, 1 Mon0 0070 22:12:01 GMT
    |   HTTPOptions:
    |     RTSP/1.0 505 RTSP Version Not Supported
    |     Server: ALi feng/2.1.0_rc1
    |     Date: Week 4, 1 Mon0 0070 22:12:11 GMT
    |   RTSPRequest:
    |     RTSP/1.0 400 Bad Request
    |     Server: ALi feng/2.1.0_rc1
    |     Date: Week 4, 1 Mon0 0070 22:12:06 GMT
    |   SIPOptions:
    |     RTSP/1.0 505 RTSP Version Not Supported
    |     Server: ALi feng/2.1.0_rc1
    |_    Date: Week 4, 1 Mon0 0070 22:12:21 GMT
    |_rtsp-methods: OPTIONS,DESCRIBE,SETUP,PLAY,PAUSE,TEARDOWN
    8554/tcp closed rtsp-alt
    1 service unrecognized despite returning data. If you know the service/ver
    sion, please submit the following fingerprint at https://nmap.org/cgi-bin/
    submit.cgi?new-service :
    SF-Port554-TCP:V=7.40%I=7%D=7/6%Time=5B3F0C99%P=aarch64-unknown-linux-gnu%
    SF:r(GetRequest,6F,"RTSP/1\.0\x20505\x20RTSP\x20Version\x20Not\x20Supporte
    SF:d\r\nServer:\x20ALi\x20feng/2\.1\.0_rc1\r\nDate:\x20Week\x204,\x201\x20
    SF:Mon0\x200070\x2022:12:01\x20GMT\r\n\r\n")%r(RTSPRequest,60,"RTSP/1\.0\x
    SF:20400\x20Bad\x20Request\r\nServer:\x20ALi\x20feng/2\.1\.0_rc1\r\nDate:\
    SF:x20Week\x204,\x201\x20Mon0\x200070\x2022:12:06\x20GMT\r\n\r\n")%r(HTTPO
    SF:ptions,6F,"RTSP/1\.0\x20505\x20RTSP\x20Version\x20Not\x20Supported\r\nS
    SF:erver:\x20ALi\x20feng/2\.1\.0_rc1\r\nDate:\x20Week\x204,\x201\x20Mon0\x
    SF:200070\x2022:12:11\x20GMT\r\n\r\n")%r(FourOhFourRequest,6F,"RTSP/1\.0\x
    SF:20505\x20RTSP\x20Version\x20Not\x20Supported\r\nServer:\x20ALi\x20feng/
    SF:2\.1\.0_rc1\r\nDate:\x20Week\x204,\x201\x20Mon0\x200070\x2022:12:16\x20
    SF:GMT\r\n\r\n")%r(SIPOptions,6F,"RTSP/1\.0\x20505\x20RTSP\x20Version\x20N
    SF:ot\x20Supported\r\nServer:\x20ALi\x20feng/2\.1\.0_rc1\r\nDate:\x20Week\
    SF:x204,\x201\x20Mon0\x200070\x2022:12:21\x20GMT\r\n\r\n");
    MAC Address: 50:00:07:00:32:84 (Unknown)
    No exact OS matches for host (If you know what OS is running on it, see ht
    tps://nmap.org/submit/ ).
    TCP/IP fingerprint:
    OS:SCAN(V=7.40%E=4%D=7/6%OT=554%CT=8554%CU=33778%PV=Y%DS=1%DC=D%G=Y%M=5000
    0
    OS:7%TM=5B3F0CBE%P=aarch64-unknown-linux-gnu)SEQ(SP=27%GCD=1%ISR=5F%TI=I%C
    I
    OS:=I%TS=U)SEQ(SP=1C%GCD=1%ISR=5F%TI=I%CI=I%II=RI%SS=S%TS=U)SEQ(SP=0%GCD=1
    7
    OS:F%ISR=5F%TI=I%TS=U)OPS(O1=M5B4NW4NNS%O2=M5B4NW4NNS%O3=M5B4NW4NNS%O4=M5B
    4
    OS:NW4NNS%O5=M5B4NW4NNS%O6=M5B4NW4NNS)WIN(W1=FFF%W2=FFF%W3=FFF%W4=FFF%W5=F
    F
    OS:F%W6=FFFF)ECN(R=Y%DF=N%T=FF%W=FFF%O=M5B4NW4NNS%CC=N%Q=)T1(R=Y%DF=N%T=FF
    %
    OS:S=O%A=S+%F=AS%RD=0%Q=)T2(R=N)T3(R=Y%DF=N%T=FF%W=FFF%S=O%A=S+%F=AS%O=M5B
    4
    OS:NW4NNS%RD=0%Q=)T4(R=Y%DF=N%T=FF%W=FFF%S=A%A=S%F=AR%O=%RD=0%Q=)T5(R=Y%DF
    =
    OS:N%T=FF%W=FFF%S=A%A=S+%F=AR%O=%RD=0%Q=)T6(R=Y%DF=N%T=FF%W=FFF%S=A%A=S%F=
    A
    OS:R%O=%RD=0%Q=)T7(R=Y%DF=N%T=FF%W=FFF%S=A%A=S+%F=AR%O=%RD=0%Q=)U1(R=Y%DF=
    N
    OS:%T=FF%IPL=38%UN=0%RIPL=G%RID=G%RIPCK=G%RUCK=G%RUD=G)IE(R=Y%DFI=S%T=FF%C
    D
    OS:=S)
    
    Network Distance: 1 hop
    
    TRACEROUTE
    HOP RTT      ADDRESS
    1   13.58 ms 192.168.100.64
    
    OS and Service detection performed. Please report any incorrect results at
     https://nmap.org/submit/ .
    Nmap done: 1 IP address (1 host up) scanned in 52.88 seconds
    *   Trying 192.168.100.64...
    * TCP_NODELAY set
    * Connected to 192.168.100.64 (192.168.100.64) port 554 (#0)
    > DESCRIBE rtsp://:@192.168.100.64:554/ RTSP/1.0
    CSeq: 1
    Accept: application/sdp
    
    < RTSP/1.0 400 Bad Request
    < CSeq: 1
    < Server: ALi feng/2.1.0_rc1
    < Date: Week 4, 1 Mon0 0070 22:12:43 GMT
    <
    * Curl_http_done: called premature == 0
    * Connection #0 to host 192.168.100.64 left intact
    *   Trying 192.168.100.64...
    * TCP_NODELAY set
    * Connected to 192.168.100.64 (192.168.100.64) port 554 (#0)
    > DESCRIBE rtsp://:@192.168.100.64:554/1.AMP RTSP/1.0
    CSeq: 1
    Accept: application/sdp
    
    < RTSP/1.0 200 OK
    < CSeq: 1
    < Server: ALi feng/2.1.0_rc1
    < Content-Type: application/sdp
    < Content-Base: rtsp://:@192.168.100.64:554/1.AMP/
    < Date: Week 4, 1 Mon0 0070 22:12:43 GMT
    < Content-Length: 226
    <
    v=0
    o=- 2209068544 2209068544 IN IP4
    s=RTSP Session
    i=1.AMP
    c=IN IP4 0.0.0.0
    t=0 0
    a=type:broadcast
    a=tool:ALi feng 2.1.0_rc1 Streaming Server
    a=control:*
    a=range:npt=0-
    m=video 0 RTP/AVP 33
    a=control:TrackID=0
    
    * Curl_http_done: called premature == 0
    * Connection #0 to host 192.168.100.64 left intact
    *   Trying 192.168.100.64...
    * TCP_NODELAY set
    * Connected to 192.168.100.64 (192.168.100.64) port 554 (#0)
    > DESCRIBE rtsp://:@192.168.100.64:554/1.AMP RTSP/1.0
    CSeq: 1
    Accept: application/sdp
    
    < RTSP/1.0 200 OK
    < CSeq: 1
    < Server: ALi feng/2.1.0_rc1
    < Content-Type: application/sdp
    < Content-Base: rtsp://:@192.168.100.64:554/1.AMP/
    < Date: Week 4, 1 Mon0 0070 22:12:43 GMT
    < Content-Length: 226
    <
    v=0
    o=- 2209068544 2209068544 IN IP4
    s=RTSP Session
    i=1.AMP
    c=IN IP4 0.0.0.0
    t=0 0
    a=type:broadcast
    a=tool:ALi feng 2.1.0_rc1 Streaming Server
    a=control:*
    a=range:npt=0-
    m=video 0 RTP/AVP 33
    a=control:TrackID=0
    
    * Curl_http_done: called premature == 0
    * Connection #0 to host 192.168.100.64 left intact
    ▶       Device RTSP URL:        rtsp://:@192.168.100.64:554/1.AMP
            Device model:
    
            IP address:             192.168.100.64
            RTSP port:              554
            Username:
            Password:
            RTSP route:             /1.AMP
    
    
    [email protected]:~#
    

    Here cameradar correctly outputs that a stream has been found and it's accessible due to the 200 response. However when you try to connect to the stream, this happens

    testRTSPClient rtsp://:@xxx.xxx.xxx.xxx:ppp/streamexample

    [email protected]:~# testRTSPClient rtsp://:@192.168.100.64:554/1.AMP
    Opening connection to 192.168.100.64, port 554...
    ...remote connection opened
    Sending request: DESCRIBE rtsp://:@192.168.100.64:554/1.AMP RTSP/1.0
    CSeq: 2
    User-Agent: testRTSPClient (LIVE555 Streaming Media v2016.11.28)
    Accept: application/sdp
    
    
    Received 424 new bytes of response data.
    Received a complete DESCRIBE response:
    RTSP/1.0 200 OK
    CSeq: 2
    Server: ALi feng/2.1.0_rc1
    Content-Type: application/sdp
    Content-Base: rtsp://:@192.168.100.64:554/1.AMP/
    Date: Week 4, 1 Mon0 0070 22:30:07 GMT
    Content-Length: 226
    
    v=0
    o=- 2209069568 2209069568 IN IP4
    s=RTSP Session
    i=1.AMP
    c=IN IP4 0.0.0.0
    t=0 0
    a=type:broadcast
    a=tool:ALi feng 2.1.0_rc1 Streaming Server
    a=control:*
    a=range:npt=0-
    m=video 0 RTP/AVP 33
    a=control:TrackID=0
    
    
    [URL:"rtsp://:@192.168.100.64:554/1.AMP/"]: Got a SDP description:
    v=0
    o=- 2209069568 2209069568 IN IP4
    s=RTSP Session
    i=1.AMP
    c=IN IP4 0.0.0.0
    t=0 0
    a=type:broadcast
    a=tool:ALi feng 2.1.0_rc1 Streaming Server
    a=control:*
    a=range:npt=0-
    m=video 0 RTP/AVP 33
    a=control:TrackID=0
    
    
    [URL:"rtsp://:@192.168.100.64:554/1.AMP/"]: Initiated the "video/MP2T" sub
    session (client ports 33332-33333)
    Sending request: SETUP rtsp://:@192.168.100.64:554/1.AMP/TrackID=0 RTSP/1.
    0
    CSeq: 3
    User-Agent: testRTSPClient (LIVE555 Streaming Media v2016.11.28)
    Transport: RTP/AVP;unicast;client_port=33332-33333
    
    
    Received 113 new bytes of response data.
    Received a complete SETUP response:
    RTSP/1.0 503 Service Unavailable
    CSeq: 3
    Server: ALi feng/2.1.0_rc1
    Date: Week 4, 1 Mon0 0070 22:30:07 GMT
    
    
    [URL:"rtsp://:@192.168.100.64:554/1.AMP/"]: Failed to set up the "video/MP
    2T" subsession: 503 Service Unavailable
    [URL:"rtsp://:@192.168.100.64:554/1.AMP/"]: Failed to start playing sessio
    n: No RTSP session is currently in progress
    
    [URL:"rtsp://:@192.168.100.64:554/1.AMP/"]: Closing the stream.
    [email protected]:~#
    

    Here you can see that after issuing a DESCRIBE request, testRTSPClient issues a second SETUP request and fails due to the 503 Service Unavailable response.

    I think it would be awesome if cameradar automated such process, without having the user actually debug what's going on using third party tools.

    Anyway this was just an enhancement idea I had. Hopefully you'll consider implementing such functionality in the near future.

    All the best

    -D4N

    library feature 
    opened by D-4-N 11
  • Error while scanning network: Call to pcap_open_live() failed three times

    Error while scanning network: Call to pcap_open_live() failed three times

    I'm starting to explore this package with the following tutorial:

    docker run --net=host -t ullaakut/cameradar:armv7 -t localhost
    

    . and i get the error below, please help me know what i need to do.

    Context

    Please select one:

    • [x] I use the docker image ullaakut/cameradar:armv7
    • [ ] I use my own build of the docker image
    • [ ] I use the pre-compiled binary
    • [ ] I use my own build of the binary
    • [ ] None of the above / I don't know

    Please select one:

    • [x] I use a specific version: armv7
    • [ ] I use the latest commit of the master branch
    • [ ] I use the latest commit of the develop branch
    • [ ] I use a forked version of the repository:
    • [ ] I use a specific commit:

    Environment

    My operating system:

    • [ ] Windows
    • [x] OSX
    • [ ] Linux
    • [ ] Other

    OS version: 12.0 OS architecture: M1

    Issue

    What was expected

    What happened

    Logs

    If your issue is with Cameradar's binary or docker image, please run it with -v to print verbose logs, and paste them here:

    ✖ error while scanning network: Call to pcap_open_live() failed three times. There are several possible reasons for this, depending on your operating system:
    LINUX: If you are getting Socket type not supported, try modprobe af_packet or recompile your kernel with PACKET enabled.
     *BSD:  If you are getting device not configured, you need to recompile your kernel with Berkeley Packet Filter support.  If you are getting No such file or directory, try creating the device (eg cd /dev; MAKEDEV <device>; or use mknod).
    *WINDOWS:  Nmap only supports ethernet interfaces on Windows for most operations because Microsoft disabled raw sockets as of Windows XP SP2.  Depending on the reason for this error, it is possible that the --unprivileged command-line argument will help.
    SOLARIS:  If you are trying to scan localhost or the address of an interface and are getting '/dev/lo0: No such file or directory' or 'lo0: No DLPI device found', complain to Sun.  I don't think Solaris can support advanced localhost scans.  You can probably use "-Pn -sT localhost"
    
    possible bug 
    opened by lamhieu-vk 1
  • [Nmap Warning] Failed to resolve [Nmap Warning] WARNING: No targets were specified, so 0 hosts scanned.">
  • Add GOPROXY in Dockerfile

    Add GOPROXY in Dockerfile

    It is recommended to add the following code in the Dockerfile:

    ENV GOPROXY=https://goproxy.io,direct

    At line 16.

    opened by Droid-MAX 4
  • Update install instructions

    Update install instructions

    Goal of this PR

    Fixes #290

    How to test it

    Run those steps on your machine to verify that it works as expected.

    ⚠️ libcurl is required.

    TODO

    • [ ] Update default dictionary path
    bug no merge 
    opened by Ullaakut 0
  • Error while compiling aarch64

    Error while compiling aarch64

    Arch: aarch64 All pkgs installed and configured Trying to compile by instuctions

    $> go get github.com/Ullaakut/cameradar
    go: downloading github.com/pkg/errors v0.8.0
    github.com/Ullaakut/cameradar
    ../go/pkg/mod/github.com/!ullaakut/[email protected]+incompatible/discover.go:36:15: assignment mismatch: 2 variables but scanner.Run returns 3 values
    
    bug help wanted 
    opened by zalexdev 7
  • mount custom files on docker

    mount custom files on docker

    I can't mount my custom ip range file on docker, how can I do?

    question 
    opened by supremepot 9
  • How to install & Run this in Nethunter in Android

    How to install & Run this in Nethunter in Android

    I wanna try this on Nethunter please reply any one how to do...I research on internet my level best...but not get one video or a understand tutorial...A help will b appreciated...Thanks in advance...One more thing I get 554 port open on that video stream device using zanti(app)...my question is how to use this script on that ip and how to watch(excute)liveIMG_20210605_235720.jpg I got this..so what to do next

    question 
    opened by sallushaik786 2
  • URL not detected when using custom credentials.json and route file

    URL not detected when using custom credentials.json and route file

    First, make sure that none of the open and closed issues is about the same issue as you are describing, and make sure to check the frequently asked questions in the README file. Then, replace the parts of this template that are between with the data relative to your issue.

    If you're reporting a bug, use the template below. Otherwise, delete this template and write your issue normally.

    Context

    Please select one:

    • [ ] I use the docker image ullaakut/cameradar
    • [ ] I use my own build of the docker image
    • [O] I use the pre-compiled binary
    • [ ] I use my own build of the binary
    • [ ] None of the above / I don't know

    Please select one:

    • [ ] I use a specific version:
    • [O] I use the latest commit of the master branch
    • [ ] I use the latest commit of the develop branch
    • [ ] I use a forked version of the repository:
    • [ ] I use a specific commit:

    Environment

    My operating system:

    • [ ] Windows
    • [ ] OSX
    • [O] Linux
    • [ ] Other

    OS version: Ubuntu-20.04 in wsl2 OS architecture:

    Issue

    I used the command below to test. The rtsp URL that should appear is rtsp://192.168.0.59:554/stream_ch00_0. I entered path and account information in the routes file and credentials.json file specified in the command line, but only ip is searched. May I know why?

    Logs

    If your issue is with Cameradar's binary or docker image, please run it with -v to print verbose logs, and paste them here:

    ''' [email protected]:~/go/bin$ ./cameradar -t 192.168.0.0/24 -v -c "../src/github.com/Ullaakut/cameradar/dictionaries/credentials.json" -r ../src/github.com/Ullaakut/cameradar/dictionaries/routes Loading credentials...ok Loading routes...ok Scanning the network...ok Attacking routes of 1 streams...* Trying 192.168.0.59:554...

    TCP_NODELAY set Connected to 192.168.0.59 (192.168.0.59) port 554 (#0) DESCRIBE rtsp://:@192.168.0.59:554//0x8b6c42 RTSP/1.0 CSeq: 1 Accept: application/sdp

    < RTSP/1.0 401 Unauthorized < CSeq: 1 < Server: EFM/(ipTIME) < WWW-Authenticate: Digest realm="iptimeRtspServer", nonce="3b27a446bfa49b0c48c3edb83139543d", stale="FALSE" < Date: Tue, Mar 23 2021 17:49:39 GMT <

    Connection #0 to host 192.168.0.59 left intact ok Attempting to detect authentication methods of 1 streams...* Trying 192.168.0.59:554... TCP_NODELAY set Connected to 192.168.0.59 (192.168.0.59) port 554 (#0) DESCRIBE rtsp://192.168.0.59:554// RTSP/1.0 CSeq: 1 Accept: application/sdp

    < RTSP/1.0 401 Unauthorized < CSeq: 1 < Server: EFM/(ipTIME) < WWW-Authenticate: Digest realm="iptimeRtspServer", nonce="3b27a446bfa49b0c48c3edb83139543d", stale="FALSE" < Date: Tue, Mar 23 2021 17:49:39 GMT <

    Connection #0 to host 192.168.0.59 left intact ok Attacking credentials of 1 streams...* Trying 192.168.0.59:554... TCP_NODELAY set Connected to 192.168.0.59 (192.168.0.59) port 554 (#0) Server auth using Digest with user '' DESCRIBE rtsp://:@192.168.0.59:554// RTSP/1.0 CSeq: 1 Accept: application/sdp

    < RTSP/1.0 401 Unauthorized < CSeq: 1 < Server: EFM/(ipTIME) < WWW-Authenticate: Digest realm="iptimeRtspServer", nonce="3b27a446bfa49b0c48c3edb83139543d", stale="FALSE" < Date: Tue, Mar 23 2021 17:49:39 GMT <

    Connection #0 to host 192.168.0.59 left intact Issue another request to this URL: 'rtsp://192.168.0.59:554//' Protocol "rtsp" not supported or disabled in libcurl Closing connection -1 Trying 192.168.0.59:554... TCP_NODELAY set Connected to 192.168.0.59 (192.168.0.59) port 554 (#0) Server auth using Digest with user '' DESCRIBE rtsp://:[email protected]:554// RTSP/1.0 CSeq: 1 Accept: application/sdp

    < RTSP/1.0 401 Unauthorized < CSeq: 1 < Server: EFM/(ipTIME) < WWW-Authenticate: Digest realm="iptimeRtspServer", nonce="3b27a446bfa49b0c48c3edb83139543d", stale="FALSE" < Date: Tue, Mar 23 2021 17:49:39 GMT <

    Connection #0 to host 192.168.0.59 left intact Issue another request to this URL: 'rtsp://:[email protected]:554//' Protocol "rtsp" not supported or disabled in libcurl Closing connection -1 Trying 192.168.0.59:554... TCP_NODELAY set Connected to 192.168.0.59 (192.168.0.59) port 554 (#0) Server auth using Digest with user '' DESCRIBE rtsp://:[email protected]:554// RTSP/1.0 CSeq: 1 Accept: application/sdp

    < RTSP/1.0 401 Unauthorized < CSeq: 1 < Server: EFM/(ipTIME) < WWW-Authenticate: Digest realm="iptimeRtspServer", nonce="3b27a446bfa49b0c48c3edb83139543d", stale="FALSE" < Date: Tue, Mar 23 2021 17:49:39 GMT <

    Connection #0 to host 192.168.0.59 left intact Issue another request to this URL: 'rtsp://:[email protected]:554//' Protocol "rtsp" not supported or disabled in libcurl Closing connection -1 Trying 192.168.0.59:554... TCP_NODELAY set Connected to 192.168.0.59 (192.168.0.59) port 554 (#0) Server auth using Digest with user '' DESCRIBE rtsp://:[email protected]:554// RTSP/1.0 CSeq: 1 Accept: application/sdp

    < RTSP/1.0 401 Unauthorized < CSeq: 1 < Server: EFM/(ipTIME) < WWW-Authenticate: Digest realm="iptimeRtspServer", nonce="3b27a446bfa49b0c48c3edb83139543d", stale="FALSE" < Date: Tue, Mar 23 2021 17:49:39 GMT <

    Connection #0 to host 192.168.0.59 left intact Issue another request to this URL: 'rtsp://:[email protected]:554//' Protocol "rtsp" not supported or disabled in libcurl Closing connection -1 Trying 192.168.0.59:554... TCP_NODELAY set Connected to 192.168.0.59 (192.168.0.59) port 554 (#0) Server auth using Digest with user '' DESCRIBE rtsp://:[email protected]:554// RTSP/1.0 CSeq: 1 Accept: application/sdp

    < RTSP/1.0 401 Unauthorized < CSeq: 1 < Server: EFM/(ipTIME) < WWW-Authenticate: Digest realm="iptimeRtspServer", nonce="3b27a446bfa49b0c48c3edb83139543d", stale="FALSE" < Date: Tue, Mar 23 2021 17:49:39 GMT <

    Connection #0 to host 192.168.0.59 left intact Issue another request to this URL: 'rtsp://:[email protected]:554//' Protocol "rtsp" not supported or disabled in libcurl Closing connection -1 Trying 192.168.0.59:554... TCP_NODELAY set Connected to 192.168.0.59 (192.168.0.59) port 554 (#0) Server auth using Digest with user '' DESCRIBE rtsp://:[email protected]:554// RTSP/1.0 CSeq: 1 Accept: application/sdp

    < RTSP/1.0 401 Unauthorized < CSeq: 1 < Server: EFM/(ipTIME) < WWW-Authenticate: Digest realm="iptimeRtspServer", nonce="3b27a446bfa49b0c48c3edb83139543d", stale="FALSE" < Date: Tue, Mar 23 2021 17:49:39 GMT <

    Connection #0 to host 192.168.0.59 left intact Issue another request to this URL: 'rtsp://:[email protected]:554//' Protocol "rtsp" not supported or disabled in libcurl Closing connection -1 Trying 192.168.0.59:554... TCP_NODELAY set Connected to 192.168.0.59 (192.168.0.59) port 554 (#0) Server auth using Digest with user '' DESCRIBE rtsp://:[email protected]:554// RTSP/1.0 CSeq: 1 Accept: application/sdp

    < RTSP/1.0 401 Unauthorized < CSeq: 1 < Server: EFM/(ipTIME) < WWW-Authenticate: Digest realm="iptimeRtspServer", nonce="3b27a446bfa49b0c48c3edb83139543d", stale="FALSE" < Date: Tue, Mar 23 2021 17:49:39 GMT <

    Connection #0 to host 192.168.0.59 left intact Issue another request to this URL: 'rtsp://:[email protected]:554//' Protocol "rtsp" not supported or disabled in libcurl Closing connection -1 Trying 192.168.0.59:554... TCP_NODELAY set Connected to 192.168.0.59 (192.168.0.59) port 554 (#0) Server auth using Digest with user '' DESCRIBE rtsp://:[email protected]:554// RTSP/1.0 CSeq: 1 Accept: application/sdp

    < RTSP/1.0 401 Unauthorized < CSeq: 1 < Server: EFM/(ipTIME) < WWW-Authenticate: Digest realm="iptimeRtspServer", nonce="3b27a446bfa49b0c48c3edb83139543d", stale="FALSE" < Date: Tue, Mar 23 2021 17:49:39 GMT <

    Connection #0 to host 192.168.0.59 left intact Issue another request to this URL: 'rtsp://:[email protected]:554//' Protocol "rtsp" not supported or disabled in libcurl Closing connection -1 Trying 192.168.0.59:554... TCP_NODELAY set Connected to 192.168.0.59 (192.168.0.59) port 554 (#0) Server auth using Digest with user '' DESCRIBE rtsp://:[email protected]:554// RTSP/1.0 CSeq: 1 Accept: application/sdp

    < RTSP/1.0 401 Unauthorized < CSeq: 1 < Server: EFM/(ipTIME) < WWW-Authenticate: Digest realm="iptimeRtspServer", nonce="3b27a446bfa49b0c48c3edb83139543d", stale="FALSE" < Date: Tue, Mar 23 2021 17:49:39 GMT <

    Connection #0 to host 192.168.0.59 left intact Issue another request to this URL: 'rtsp://:[email protected]:554//' Protocol "rtsp" not supported or disabled in libcurl Closing connection -1 Trying 192.168.0.59:554... TCP_NODELAY set Connected to 192.168.0.59 (192.168.0.59) port 554 (#0) Server auth using Digest with user '' DESCRIBE rtsp://:[email protected]:554// RTSP/1.0 CSeq: 1 Accept: application/sdp

    < RTSP/1.0 401 Unauthorized < CSeq: 1 < Server: EFM/(ipTIME) < WWW-Authenticate: Digest realm="iptimeRtspServer", nonce="3b27a446bfa49b0c48c3edb83139543d", stale="FALSE" < Date: Tue, Mar 23 2021 17:49:39 GMT <

    Connection #0 to host 192.168.0.59 left intact Issue another request to this URL: 'rtsp://:[email protected]:554//' Protocol "rtsp" not supported or disabled in libcurl Closing connection -1 Trying 192.168.0.59:554... TCP_NODELAY set Connected to 192.168.0.59 (192.168.0.59) port 554 (#0) Server auth using Digest with user '' DESCRIBE rtsp://:[email protected]:554// RTSP/1.0 CSeq: 1 Accept: application/sdp

    < RTSP/1.0 401 Unauthorized < CSeq: 1 < Server: EFM/(ipTIME) < WWW-Authenticate: Digest realm="iptimeRtspServer", nonce="3b27a446bfa49b0c48c3edb83139543d", stale="FALSE" < Date: Tue, Mar 23 2021 17:49:39 GMT <

    Connection #0 to host 192.168.0.59 left intact Issue another request to this URL: 'rtsp://:[email protected]:554//' Protocol "rtsp" not supported or disabled in libcurl Closing connection -1 Trying 192.168.0.59:554... TCP_NODELAY set Connected to 192.168.0.59 (192.168.0.59) port 554 (#0) Server auth using Digest with user '' DESCRIBE rtsp://:[email protected]:554// RTSP/1.0 CSeq: 1 Accept: application/sdp

    < RTSP/1.0 401 Unauthorized < CSeq: 1 < Server: EFM/(ipTIME) < WWW-Authenticate: Digest realm="iptimeRtspServer", nonce="3b27a446bfa49b0c48c3edb83139543d", stale="FALSE" < Date: Tue, Mar 23 2021 17:49:39 GMT <

    Connection #0 to host 192.168.0.59 left intact Issue another request to this URL: 'rtsp://:[email protected]:554//' Protocol "rtsp" not supported or disabled in libcurl Closing connection -1 Trying 192.168.0.59:554... TCP_NODELAY set Connected to 192.168.0.59 (192.168.0.59) port 554 (#0) Server auth using Digest with user '' DESCRIBE rtsp://:[email protected]:554// RTSP/1.0 CSeq: 1 Accept: application/sdp

    < RTSP/1.0 401 Unauthorized < CSeq: 1 < Server: EFM/(ipTIME) < WWW-Authenticate: Digest realm="iptimeRtspServer", nonce="3b27a446bfa49b0c48c3edb83139543d", stale="FALSE" < Date: Tue, Mar 23 2021 17:49:39 GMT <

    Connection #0 to host 192.168.0.59 left intact Issue another request to this URL: 'rtsp://:[email protected]:554//' Protocol "rtsp" not supported or disabled in libcurl Closing connection -1 Trying 192.168.0.59:554... TCP_NODELAY set Connected to 192.168.0.59 (192.168.0.59) port 554 (#0) Server auth using Digest with user '' DESCRIBE rtsp://:[email protected]:554// RTSP/1.0 CSeq: 1 Accept: application/sdp

    < RTSP/1.0 401 Unauthorized < CSeq: 1 < Server: EFM/(ipTIME) < WWW-Authenticate: Digest realm="iptimeRtspServer", nonce="3b27a446bfa49b0c48c3edb83139543d", stale="FALSE" < Date: Tue, Mar 23 2021 17:49:39 GMT <

    Connection #0 to host 192.168.0.59 left intact Issue another request to this URL: 'rtsp://:[email protected]:554//' Protocol "rtsp" not supported or disabled in libcurl Closing connection -1 Trying 192.168.0.59:554... TCP_NODELAY set Connected to 192.168.0.59 (192.168.0.59) port 554 (#0) Server auth using Digest with user '' DESCRIBE rtsp://:[email protected]:554// RTSP/1.0 CSeq: 1 Accept: application/sdp

    < RTSP/1.0 401 Unauthorized < CSeq: 1 < Server: EFM/(ipTIME) < WWW-Authenticate: Digest realm="iptimeRtspServer", nonce="3b27a446bfa49b0c48c3edb83139543d", stale="FALSE" < Date: Tue, Mar 23 2021 17:49:39 GMT <

    Connection #0 to host 192.168.0.59 left intact Issue another request to this URL: 'rtsp://:[email protected]:554//' Protocol "rtsp" not supported or disabled in libcurl Closing connection -1 Trying 192.168.0.59:554... TCP_NODELAY set Connected to 192.168.0.59 (192.168.0.59) port 554 (#0) Server auth using Digest with user '' DESCRIBE rtsp://:[email protected]:554// RTSP/1.0 CSeq: 1 Accept: application/sdp

    < RTSP/1.0 401 Unauthorized < CSeq: 1 < Server: EFM/(ipTIME) < WWW-Authenticate: Digest realm="iptimeRtspServer", nonce="3b27a446bfa49b0c48c3edb83139543d", stale="FALSE" < Date: Tue, Mar 23 2021 17:49:39 GMT <

    Connection #0 to host 192.168.0.59 left intact Issue another request to this URL: 'rtsp://:[email protected]:554//' Protocol "rtsp" not supported or disabled in libcurl Closing connection -1 Trying 192.168.0.59:554... TCP_NODELAY set Connected to 192.168.0.59 (192.168.0.59) port 554 (#0) Server auth using Digest with user '' DESCRIBE rtsp://:[email protected]:554// RTSP/1.0 CSeq: 1 Accept: application/sdp

    < RTSP/1.0 401 Unauthorized < CSeq: 1 < Server: EFM/(ipTIME) < WWW-Authenticate: Digest realm="iptimeRtspServer", nonce="3b27a446bfa49b0c48c3edb83139543d", stale="FALSE" < Date: Tue, Mar 23 2021 17:49:39 GMT <

    Connection #0 to host 192.168.0.59 left intact Issue another request to this URL: 'rtsp://:[email protected]:554//' Protocol "rtsp" not supported or disabled in libcurl Closing connection -1 Trying 192.168.0.59:554... TCP_NODELAY set Connected to 192.168.0.59 (192.168.0.59) port 554 (#0) Server auth using Digest with user '' DESCRIBE rtsp://:[email protected]:554// RTSP/1.0 CSeq: 1 Accept: application/sdp

    < RTSP/1.0 401 Unauthorized < CSeq: 1 < Server: EFM/(ipTIME) < WWW-Authenticate: Digest realm="iptimeRtspServer", nonce="3b27a446bfa49b0c48c3edb83139543d", stale="FALSE" < Date: Tue, Mar 23 2021 17:49:39 GMT <

    Connection #0 to host 192.168.0.59 left intact Issue another request to this URL: 'rtsp://:[email protected]:554//' Protocol "rtsp" not supported or disabled in libcurl Closing connection -1 Trying 192.168.0.59:554... TCP_NODELAY set Connected to 192.168.0.59 (192.168.0.59) port 554 (#0) Server auth using Digest with user '' DESCRIBE rtsp://:[email protected]:554// RTSP/1.0 CSeq: 1 Accept: application/sdp

    < RTSP/1.0 401 Unauthorized < CSeq: 1 < Server: EFM/(ipTIME) < WWW-Authenticate: Digest realm="iptimeRtspServer", nonce="3b27a446bfa49b0c48c3edb83139543d", stale="FALSE" < Date: Tue, Mar 23 2021 17:49:39 GMT <

    Connection #0 to host 192.168.0.59 left intact Issue another request to this URL: 'rtsp://:[email protected]:554//' Protocol "rtsp" not supported or disabled in libcurl Closing connection -1 Trying 192.168.0.59:554... TCP_NODELAY set Connected to 192.168.0.59 (192.168.0.59) port 554 (#0) Server auth using Digest with user '' DESCRIBE rtsp://:[email protected]:554// RTSP/1.0 CSeq: 1 Accept: application/sdp

    < RTSP/1.0 401 Unauthorized < CSeq: 1 < Server: EFM/(ipTIME) < WWW-Authenticate: Digest realm="iptimeRtspServer", nonce="3b27a446bfa49b0c48c3edb83139543d", stale="FALSE" < Date: Tue, Mar 23 2021 17:49:39 GMT <

    Connection #0 to host 192.168.0.59 left intact Issue another request to this URL: 'rtsp://:[email protected]:554//' Protocol "rtsp" not supported or disabled in libcurl Closing connection -1 Trying 192.168.0.59:554... TCP_NODELAY set Connected to 192.168.0.59 (192.168.0.59) port 554 (#0) Server auth using Digest with user '' DESCRIBE rtsp://:[email protected]:554// RTSP/1.0 CSeq: 1 Accept: application/sdp

    < RTSP/1.0 401 Unauthorized < CSeq: 1 < Server: EFM/(ipTIME) < WWW-Authenticate: Digest realm="iptimeRtspServer", nonce="3b27a446bfa49b0c48c3edb83139543d", stale="FALSE" < Date: Tue, Mar 23 2021 17:49:44 GMT <

    Connection #0 to host 192.168.0.59 left intact Issue another request to this URL: 'rtsp://Administrator:[email protected]:554//' Protocol "rtsp" not supported or disabled in libcurl Closing connection -1 Trying 192.168.0.59:554... TCP_NODELAY set Connected to 192.168.0.59 (192.168.0.59) port 554 (#0) Server auth using Digest with user 'Administrator' DESCRIBE rtsp://Administrator:[email protected]:554// RTSP/1.0 CSeq: 1 Accept: application/sdp

    < RTSP/1.0 401 Unauthorized < CSeq: 1 < Server: EFM/(ipTIME) < WWW-Authenticate: Digest realm="iptimeRtspServer", nonce="3b27a446bfa49b0c48c3edb83139543d", stale="FALSE" < Date: Tue, Mar 23 2021 17:49:44 GMT <

    Connection #0 to host 192.168.0.59 left intact Issue another request to this URL: 'rtsp://Administrator:[email protected]:554//' Protocol "rtsp" not supported or disabled in libcurl Closing connection -1 Trying 192.168.0.59:554... TCP_NODELAY set Connected to 192.168.0.59 (192.168.0.59) port 554 (#0) Server auth using Digest with user 'Administrator' DESCRIBE rtsp://Administrator:[email protected]:554// RTSP/1.0 CSeq: 1 Accept: application/sdp

    < RTSP/1.0 401 Unauthorized < CSeq: 1 < Server: EFM/(ipTIME) < WWW-Authenticate: Digest realm="iptimeRtspServer", nonce="3b27a446bfa49b0c48c3edb83139543d", stale="FALSE" < Date: Tue, Mar 23 2021 17:49:44 GMT <

    Connection #0 to host 192.168.0.59 left intact Issue another request to this URL: 'rtsp://Administrator:[email protected]:554//' Protocol "rtsp" not supported or disabled in libcurl Closing connection -1 Trying 192.168.0.59:554... TCP_NODELAY set Connected to 192.168.0.59 (192.168.0.59) port 554 (#0) Server auth using Digest with user 'Administrator' DESCRIBE rtsp://Administrator:[email protected]:554// RTSP/1.0 CSeq: 1 Accept: application/sdp

    < RTSP/1.0 401 Unauthorized < CSeq: 1 < Server: EFM/(ipTIME) < WWW-Authenticate: Digest realm="iptimeRtspServer", nonce="3b27a446bfa49b0c48c3edb83139543d", stale="FALSE" < Date: Tue, Mar 23 2021 17:49:44 GMT <

    Connection #0 to host 192.168.0.59 left intact

    Issue another request to this URL: 'rtsp://Administrator:[email protected]:554//'

    Protocol "rtsp" not supported or disabled in libcurl

    Closing connection -1

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0 ok

    Perform failed for "rtsp://:@192.168.0.59:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://qtumai:@192.168.0.59:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://qtumai:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://qtumai:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://qtumai:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://qtumai:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://qtumai:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://qtumai:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://qtumai:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://qtumai:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://qtumai:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://qtumai:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://qtumai:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://qtumai:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://qtumai:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://qtumai:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://qtumai:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://qtumai:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://qtumai:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://qtumai:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://qtumai:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://qtumai:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://qtumai:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://qtumai:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://qtumai:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://qtumai:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://qtumai:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://qtumai:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://qtumai:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://qtumai:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://qtumai:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://qtumai:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://qtumai:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://qtumai:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://qtumai:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://qtumai:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://qtumai:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://qtumai:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://qtumai:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://qtumai:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://666666:@192.168.0.59:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://666666:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://666666:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://666666:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://666666:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://666666:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://666666:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://666666:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://666666:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://666666:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://666666:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://666666:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://666666:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://666666:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://666666:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://666666:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://666666:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://666666:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://666666:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://666666:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://666666:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://666666:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://666666:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://666666:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://666666:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://666666:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://666666:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://666666:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://666666:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://666666:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://666666:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://666666:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://666666:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://666666:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://666666:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://666666:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://666666:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://666666:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://666666:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://888888:@192.168.0.59:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://888888:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://888888:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://888888:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://888888:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://888888:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://888888:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://888888:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://888888:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://888888:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://888888:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://888888:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://888888:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://888888:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://888888:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://888888:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://888888:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://888888:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://888888:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://888888:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://888888:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://888888:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://888888:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://888888:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://888888:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://888888:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://888888:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://888888:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://888888:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://888888:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://888888:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://888888:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://888888:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://888888:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://888888:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://888888:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://888888:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://888888:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://888888:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://Admin:@192.168.0.59:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://Admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://Admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://Admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://Admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://Admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://Admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://Admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://Admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://Admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://Admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://Admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://Admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://Admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://Admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://Admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://Admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://Admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://Admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://Admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://Admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://Admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://Admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://Admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://Admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://Admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://Admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://Admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://Admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://Admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://Admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://Admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://Admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://Admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://Admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://Admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://Admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://Admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://Admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin:@192.168.0.59:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin1:@192.168.0.59:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin1:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin1:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin1:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin1:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin1:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin1:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin1:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin1:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin1:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin1:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin1:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin1:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin1:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin1:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin1:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin1:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin1:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin1:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin1:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin1:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin1:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin1:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin1:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin1:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin1:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin1:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin1:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin1:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin1:[email protected]0.59:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin1:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin1:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin1:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin1:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin1:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin1:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin1:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin1:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://admin1:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://administrator:@192.168.0.59:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://administrator:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://administrator:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://administrator:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://administrator:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://administrator:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://administrator:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://administrator:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://administrator:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://administrator:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://administrator:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://administrator:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://administrator:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://administrator:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://administrator:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://administrator:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://administrator:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://administrator:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://administrator:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://administrator:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://administrator:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://administrator:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://administrator:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://administrator:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://administrator:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://administrator:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://administrator:[email protected]0.59:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://administrator:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://administrator:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://administrator:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://administrator:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://administrator:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://administrator:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://administrator:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://administrator:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://administrator:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://administrator:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://administrator:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://administrator:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://Administrator:@192.168.0.59:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://Administrator:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://Administrator:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://Administrator:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://Administrator:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://Administrator:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://Administrator:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://Administrator:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://Administrator:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://Administrator:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://Administrator:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://Administrator:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://Administrator:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://Administrator:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://Administrator:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://Administrator:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://Administrator:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://Administrator:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://Administrator:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://Administrator:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://Administrator:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://Administrator:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://Administrator:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://Administrator:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://Administrator:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://Administrator:[email protected]:554//" (auth 2): curl: Unsupported protocol Perform failed for "rtsp://Administrator:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://Administrator:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://Administrator:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://Administrator:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://Administrator:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://Administrator:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://Administrator:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://Administrator:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://Administrator:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://Administrator:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://Administrator:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://Administrator:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://Administrator:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://aiphone:@192.168.0.59:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://aiphone:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://aiphone:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://aiphone:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://aiphone:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://aiphone:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://aiphone:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://aiphone:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://aiphone:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://aiphone:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://aiphone:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://aiphone:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://aiphone:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://aiphone:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://aiphone:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://aiphone:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://aiphone:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://aiphone:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://aiphone:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://aiphone:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://aiphone:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://aiphone:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://aiphone:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://aiphone:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://aiphone:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://aiphone:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://aiphone:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://aiphone:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://aiphone:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://aiphone:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://aiphone:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://aiphone:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://aiphone:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://aiphone:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://aiphone:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://aiphone:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://aiphone:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://aiphone:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://aiphone:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://Dinion:@192.168.0.59:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://Dinion:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://Dinion:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://Dinion:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://Dinion:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://Dinion:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://Dinion:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://Dinion:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://Dinion:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://Dinion:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://Dinion:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://Dinion:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://Dinion:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://Dinion:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://Dinion:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://Dinion:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://Dinion:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://Dinion:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://Dinion:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://Dinion:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://Dinion:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://Dinion:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://Dinion:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://Dinion:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://Dinion:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://Dinion:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://Dinion:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://Dinion:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://Dinion:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://Dinion:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://Dinion:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://Dinion:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://Dinion:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://Dinion:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://Dinion:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://Dinion:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://Dinion:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://Dinion:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://Dinion:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://root:@192.168.0.59:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://root:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://root:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://root:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://root:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://root:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://root:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://root:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://root:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://root:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://root:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://root:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://root:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://root:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://root:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://root:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://root:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://root:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://root:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://root:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://root:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://root:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://root:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://root:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://root:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://root:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://root:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://root:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://root:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://root:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://root:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://root:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://root:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://root:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://root:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://root:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://root:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://root:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://root:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://service:@192.168.0.59:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://service:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://service:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://service:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://service:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://service:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://service:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://service:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://service:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://service:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://service:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://service:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://service:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://service:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://service:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://service:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://service:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://service:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://service:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://service:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://service:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://service:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://service:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://service:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://service:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://service:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://service:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://service:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://service:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://service:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://service:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://service:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://service:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://service:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://service:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://service:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://service:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://service:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://service:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://supervisor:@192.168.0.59:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://supervisor:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://supervisor:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://supervisor:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://supervisor:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://supervisor:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://supervisor:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://supervisor:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://supervisor:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://supervisor:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://supervisor:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://supervisor:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://supervisor:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://supervisor:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://supervisor:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://supervisor:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://supervisor:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://supervisor:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://supervisor:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://supervisor:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://supervisor:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://supervisor:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://supervisor:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://supervisor:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://supervisor:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://supervisor:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://supervisor:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://supervisor:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://supervisor:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://supervisor:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://supervisor:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://supervisor:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://supervisor:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://supervisor:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://supervisor:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://supervisor:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://supervisor:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://supervisor:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://supervisor:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://ubnt:@192.168.0.59:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://ubnt:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://ubnt:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://ubnt:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://ubnt:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://ubnt:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://ubnt:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://ubnt:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://ubnt:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://ubnt:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://ubnt:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://ubnt:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://ubnt:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://ubnt:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://ubnt:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://ubnt:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://ubnt:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://ubnt:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://ubnt:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://ubnt:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://ubnt:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://ubnt:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://ubnt:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://ubnt:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://ubnt:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://ubnt:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://ubnt:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://ubnt:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://ubnt:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://ubnt:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://ubnt:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://ubnt:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://ubnt:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://ubnt:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://ubnt:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://ubnt:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://ubnt:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://ubnt:[email protected]:554//" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://ubnt:[email protected]:554//" (auth 2): curl: Couldn't connect to server Validating that streams are accessible...* Closing connection 0 ok Perform failed for "rtsp://:@192.168.0.59:554//" (auth 2): curl: Couldn't connect to server Second round of attacks...* Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0

    Closing connection 0 ok

    Perform failed for "rtsp://:@192.168.0.59:554//0x8b6c42" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554//live/ch01_0" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/0/1:1/main" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/0/usrnm:pwd/main" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/0/video1" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/1" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/1.AMP" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/1/h264major" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/1/stream1" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/11" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/12" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/125" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/1080p" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/1440p" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/480p" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/4K" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/666" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/720p" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/AVStream1_1" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/CAM_ID.password.mp2" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/CH001.sdp" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/GetData.cgi" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/HD" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/HighResolutionVideo" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/LowResolutionVideo" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/MediaInput/h264" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/MediaInput/mpeg4" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/ONVIF/MediaInput" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/ONVIF/MediaInput?profile=4_def_profile6" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/StdCh1" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/Streaming/Channels/1" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/Streaming/Unicast/channels/101" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/StreamingSetting?version=1.0&action=getRTSPStream&ChannelID=1&ChannelName=Channel1" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/VideoInput/1/h264/1" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/VideoInput/1/mpeg4/1" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/access_code" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/access_name_for_stream_1_to_5" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/api/mjpegvideo.cgi" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/av0_0" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/av2" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/avc" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/avn=2" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/axis-media/media.amp" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/axis-media/media.amp?camera=1" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/axis-media/media.amp?videocodec=h264" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/cam" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/cam/realmonitor" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/cam/realmonitor?channel=0&subtype=0" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/cam/realmonitor?channel=1&subtype=0" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/cam/realmonitor?channel=1&subtype=1" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/cam/realmonitor?channel=1&subtype=1&unicast=true&proto=Onvif" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/cam0" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/cam0_0" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/cam0_1" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/cam1" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/cam1/h264" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/cam1/h264/multicast" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/cam1/mjpeg" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/cam1/mpeg4" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/cam1/mpeg4?user='username'&pwd='password'" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/cam1/onvif-h264" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/camera.stm" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/ch0" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/ch00/0" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/ch001.sdp" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/ch01.264" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/ch01.264?" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/ch01.264?ptype=tcp" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/ch1_0" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/ch2_0" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/ch3_0" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/ch4_0" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/ch1/0" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/ch2/0" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/ch3/0" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/ch4/0" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/ch0_0.h264" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/ch0_unicast_firststream" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/ch0_unicast_secondstream" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/ch1-s1" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/channel1" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/gnz_media/main" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/h264" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/h264.sdp" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/h264/ch1/sub/av_stream" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/h264/media.amp" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/h264Preview_01_main" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/h264Preview_01_sub" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/h264_vga.sdp" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/h264_stream" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/image.mpg" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/img/media.sav" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/img/media.sav?channel=1" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/img/video.asf" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/img/video.sav" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/ioImage/1" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/ipcam.sdp" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/ipcam_h264.sdp" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/ipcam_mjpeg.sdp" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/live" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/live.sdp" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/live/av0" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/live/ch0" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/live/ch00_0" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/live/ch01_0" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/live/h264" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/live/main" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/live/main0" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/live/mpeg4" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/live1.sdp" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/live3.sdp" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/live_mpeg4.sdp" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/live_st1" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/livestream" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/main" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/media" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/media.amp" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/media.amp?streamprofile=Profile1" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/media/media.amp" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/media/video1" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/medias2" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/mjpeg/media.smp" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/mp4" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/mpeg/media.amp" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/mpeg4" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/mpeg4/1/media.amp" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/mpeg4/media.amp" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/mpeg4/media.smp" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/mpeg4unicast" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/mpg4/rtsp.amp" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/multicaststream" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/now.mp4" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/nph-h264.cgi" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/nphMpeg4/g726-640x" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/nphMpeg4/g726-640x48" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/nphMpeg4/g726-640x480" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/nphMpeg4/nil-320x240" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/onvif-media/media.amp" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/onvif1" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/[email protected]:6667/blinkhd" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/play1.sdp" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/play2.sdp" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/profile2/media.smp" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/profile5/media.smp" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/rtpvideo1.sdp" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/rtsp_live0" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/rtsp_live1" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/rtsp_live2" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/rtsp_tunnel" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/rtsph264" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/rtsph2641080p" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/snap.jpg" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/stream" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/stream/0" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/stream/1" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/stream/live.sdp" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/stream.sdp" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/stream1" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/streaming/channels/0" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/streaming/channels/1" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/streaming/channels/101" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/stream_ch00_0" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/stream_ch00_1" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/tcp/av0_0" (auth 2): curl: Couldn't connect to server

    Perform failed for "rtsp://:@192.168.0.59:554/test" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/tmpfs/auto.jpg" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/trackID=1" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/ucast/11" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/udp/av0_0" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/udp/unicast/aiphone_H264" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/udpstream" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/user.pin.mp2" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/user=admin&password=&channel=1&stream=0.sdp?" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/user=admin&password=&channel=1&stream=0.sdp?real_stream" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/user=admin_password=?????_channel=1_stream=0.sdp?real_stream" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/user=admin_password=R5XFY888_channel=1_stream=0.sdp?real_stream" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/user_defined" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/v2" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/video" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/video.3gp" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/video.h264" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/video.mjpg" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/video.mp4" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/video.pro1" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/video.pro2" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/video.pro3" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/video0" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/video0.sdp" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/video1" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/video1.sdp" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/video1+audio1" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/videoMain" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/videoinput_1/h264_1/media.stm" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/videostream.asf" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/vis" (auth 2): curl: Couldn't connect to server Perform failed for "rtsp://:@192.168.0.59:554/wfov" (auth 2): curl: Couldn't connect to server Validating that streams are accessible...* Closing connection 0 ok Perform failed for "rtsp://:@192.168.0.59:554//" (auth 2): curl: Couldn't connect to server ✖ Admin panel URL: http://192.168.0.59/ You can use this URL to try attacking the camera's admin panel instead. Available: ✖ IP address: 192.168.0.59 RTSP port: 554 Auth type: digest Username: not found Password: not found RTSP routes: '''

    waiting for feedback possible bug 
    opened by stopwater87 3
  • Skip the nmap scan, if target list is full of open rtsp IPs

    Skip the nmap scan, if target list is full of open rtsp IPs

    Is there a way to skip the nmap scan and go straight to the attacking routes? In case i already know the target list is full of open rtsp port IPs.

    enhancement help wanted good first issue feature 
    opened by bejaranoo 1
  • Perform failed for <rtsp url here> curl: Timeout was reached

    Perform failed for curl: Timeout was reached

    Context

    Please select one:

    • [ ] I use the docker image ullaakut/cameradar

    Please select one:

    • [ ] I use the latest commit of the master branch

    Environment

    My operating system:

    • [ ] Linux

    OS version: Linux ubuntu 5.4.0-40-generic #44-Ubuntu SMP Tue Jun 23 00:01:04 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux OS architecture:

    Issue

    Getting Timeout was reached and only the first username:password combination is used - moreover I see that it's saying that "This camera does not require authentication" even if it clearly does

    What was expected

    Find or at least try all the routes and user:pass combination on that IP not only the first 2 occurrences (joe for the user and firstpass for the password). Also, even if I manually added some cutom routes in the /tmp/routes.json file I don't see anything that resembles what I have on the first line of this file (/tmp/routes.json) which is "/hlbenefits"

    What happened

    I guess the issue was because of the timeout and even when tried to increase the timeout to -T 100000ms the issue still persisted

    Logs

    If your issue is with Cameradar's binary or docker image, please run it with -v to print verbose logs, and paste them here:

    [email protected]:~# docker run -t -v /tmp:/tmp ullaakut/cameradar -c "/tmp/mycredentials.json" -r /tmp/routes.json -t 192.168.1.52 -T 10000ms -d
    Loading credentials...ok
      > Loading credentials dictionary from path "/tmp/mycredentials.json"
      > Loaded 15 usernames and 39 passwords
    Loading routes...ok
      > Loading routes dictionary from path "/tmp/routes.json"
      > Loaded 195 routes
    Scanning the network...ok
      > Found 1 RTSP streams
    Attacking routes of 1 streams...ok
      > DESCRIBE rtsp://:@192.168.1.52:554//0x8b6c42 RTSP/1.0 > 200
    Attempting to detect authentication methods of 1 streams...ok
      > DESCRIBE rtsp://192.168.1.52:554// RTSP/1.0 > 0
      > Stream rtsp://:@192.168.1.52:554// uses no authentication method
    Attacking credentials of 1 streams...ok
      > DESCRIBE rtsp://joe:[email protected]:554// RTSP/1.0 > 200
    Validating that streams are accessible...ok
      > Perform failed for "rtsp://joe:[email protected]:554//" (auth 0): curl: Timeout was reached
    Second round of attacks...ok
      > DESCRIBE rtsp://joe:[email protected]:554//0x8b6c42 RTSP/1.0 > 200
    Validating that streams are accessible...ok
      > Perform failed for "rtsp://joe:[email protected]:554//" (auth 0): curl: Timeout was reached
    ✖	Admin panel URL:	http://192.168.1.52/ You can use this URL to try attacking the camera's admin panel instead.
    	Available:		✖
    	Device model:		H264DVR rtspd
    
    	IP address:		192.168.1.52
    	RTSP port:		554
    	This camera does not require authentication
    	Username:		joe
    	Password:		firstpass
    	RTSP routes:
    				//
    				//
    
    
    ✖ Streams were found but none were accessed. They are most likely configured with secure credentials and routes. You can try adding entries to the dictionary or generating your own in order to attempt a bruteforce attack on the cameras.
    
    waiting for feedback possible bug 
    opened by aldabrada 2
Releases(v5.0.1)
  • v5.0.0(May 4, 2020)

    Features

    Bugfixes

    Misc

    • Move issue template to .github and remove old changelog file
    • Reword error message when no stream is found
    • Remove unnecessary import alias
    Source code(tar.gz)
    Source code(zip)
  • v4.1.3(Jan 21, 2020)

  • v4.1.2(Jan 17, 2020)

  • v4.1.1(Dec 2, 2019)

    v4.1.1 (2019-11-30)

    All Commits

    Enhancements:

    • [binary,enhancement,library] Add scan interval option (#245 by Ullaakut)
    • [enhancement] Update dictionaries & dependencies for dictionary fetch tool (#240 by Ullaakut)

    Bug fixes:

    Misc:

    Source code(tar.gz)
    Source code(zip)
  • v4.0.0(May 26, 2019)

    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
      • Spinner removed (#211)
      • Better logs using disgo
      • Two new verbosity levels: debug being the default and verbose showing extra logs for each curl request
    • 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

    Screenshot 2019-05-25 at 4 11 07 PM

    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)

    Source code(tar.gz)
    Source code(zip)
  • v3.0.1(Jan 24, 2019)

    Bugfixes

    • Fixes a bug where the 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)
    • Fixes a bug where it was impossible to override the default dictionaries using the docker image. (#189)
    Source code(tar.gz)
    Source code(zip)
  • v3.0.0(Jan 22, 2019)

    Enhancements

    • The cameradar library is now more intuitive and easier to use by removing useless arguments from the Discover method
    • Added more routes and credentials to the dictionaries #185
    • Cameradar scans one more port by default (5554) #186
    • Cameradar uses nmap to improve error handling, make cameradar faster and easier to read #187
    • Removed legacy code #187
    • Finally reached 100% test coverage by completely mocking nmap #187

    Disclaimer

    This 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.

    Source code(tar.gz)
    Source code(zip)
  • v2.1.0(Nov 12, 2018)

    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
    Source code(tar.gz)
    Source code(zip)
  • 2.0.0(Sep 19, 2017)

    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
    Source code(tar.gz)
    Source code(zip)
    cameradar(5.84 MB)
  • 1.1.4(Jan 18, 2017)

    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.
    Source code(tar.gz)
    Source code(zip)
    cameradar_1.1.4_Release_Linux.tar.gz(788.40 KB)
  • 1.1.3(Nov 23, 2016)

    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
    Source code(tar.gz)
    Source code(zip)
    cameradar_1.1.3_Release_Linux.tar.gz(794.88 KB)
  • 1.1.1(Nov 12, 2016)

    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.
    Source code(tar.gz)
    Source code(zip)
  • 1.1.0(Oct 29, 2016)

    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
    Source code(tar.gz)
    Source code(zip)
    cameradar_1.1.0_Release_Linux.tar.gz(794.22 KB)
  • 1.0.4(Aug 31, 2016)

    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
    Source code(tar.gz)
    Source code(zip)
  • 1.0.0(Jun 21, 2016)

  • 0.2.2(May 27, 2016)

    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
    Source code(tar.gz)
    Source code(zip)
  • 0.2.1(May 24, 2016)

    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
    Source code(tar.gz)
    Source code(zip)
  • 0.1.1(May 21, 2016)

    This version is a patch of the 0.1.0 release.

    Changelog

    Major changes

    • Added a quick Docker deployment process
    • Added automatic dependencies downloading through CMake for the manual installation
    • Added CPack packaging for the Docker deployment

    Minor changes

    • Changed recommended cloning method to HTTPS
    • Added lots of informations to README.md
    Source code(tar.gz)
    Source code(zip)
  • 0.1.0(May 20, 2016)

Owner
Brendan Le Glaunec
Software Engineer @traefik & previously R&D Software Engineer @EtixLabs / Go Contractor @fresh8
Brendan Le Glaunec
How to systematically secure anything: a repository about security engineering

How to Secure Anything Security engineering is the discipline of building secure systems. Its lessons are not just applicable to computer security. In

Veeral Patel 6.1k Sep 26, 2021
DockerSlim (docker-slim): Don't change anything in your Docker container image and minify it by up to 30x (and for compiled languages even more) making it secure too! (free and open source)

Minify and Secure Docker containers (free and open source!) Don't change anything in your Docker container image and minify it by up to 30x making it

docker-slim 10.7k Sep 23, 2021
Gorsair hacks its way into remote docker containers that expose their APIs

Gorsair Gorsair is a penetration testing tool for discovering and remotely accessing Docker APIs from vulnerable Docker containers. Once it has access

Brendan Le Glaunec 730 Sep 20, 2021
Automatic HTTPS for any Go program: fully-managed TLS certificate issuance and renewal

Easy and Powerful TLS Automation The same library used by the Caddy Web Server Caddy's automagic TLS features—now for your own Go programs—in one powe

Caddy 3.7k Sep 13, 2021
Cossack Labs 800 Sep 17, 2021
✒ A self-hosted, cross-platform service to sign iOS apps using any CI as a builder

iOS Signer Service A self-hosted, cross-platform service to sign iOS apps using any CI as a builder Introduction There are many reasons to install app

null 459 Sep 16, 2021
Design, compile and deploy your own Endlesss soundpacks with rapid iteration in Studio and iOS

Squonker is a tool for building and installing your own custom Endlesss instruments.

Unbundlesss 3 Sep 15, 2021
SourcePoint is a C2 profile generator for Cobalt Strike command and control servers designed to ensure evasion.

SourcePoint SourcePoint is a polymorphic C2 profile generator for Cobalt Strike C2s, written in Go. SourcePoint allows unique C2 profiles to be genera

Tylous 400 Sep 17, 2021
PHP functions implementation to Golang. This package is for the Go beginners who have developed PHP code before. You can use PHP like functions in your app, module etc. when you add this module to your project.

PHP Functions for Golang - phpfuncs PHP functions implementation to Golang. This package is for the Go beginners who have developed PHP code before. Y

Serkan Algur 42 Aug 19, 2021
A tool to check for vulnerabilities in your Golang dependencies, powered by Sonatype OSS Index

Nancy nancy is a tool to check for vulnerabilities in your Golang dependencies, powered by Sonatype OSS Index, and as well, works with Nexus IQ Server

Sonatype Community 318 Sep 22, 2021
A rest application to update firewalld rules on a linux server

Firewalld-rest A REST application to dynamically update firewalld rules on a linux server. Firewalld is a firewall management tool for Linux operating

Prashant Gupta 309 Sep 12, 2021
Go package to embed the Mozilla Included CA Certificate List

rootcerts Package rootcerts provides an embedded copy of the Mozilla Included CA Certificate List, more specifically the PEM of Root Certificates in M

Lucas Bremgartner 50 Aug 28, 2021
Tracee: Linux Runtime Security and Forensics using eBPF

Tracee is a Runtime Security and forensics tool for Linux. It is using Linux eBPF technology to trace your system and applications at runtime, and analyze collected events to detect suspicious behavioral patterns.

Aqua Security 1.3k Sep 26, 2021
🔑 A decentralized key derivation protocol for simple passphrase.

Throttled Identity Protocol (TIP) is a decentralized key derivation protocol, which allows people to obtain a strong secret key through a very simple passphrase, e.g. a six-digit PIN.

Mixin Network 25 Sep 17, 2021
Official library of StackPulse steps

StackPulse Steps This repository is the official library of StackPulse steps. StackPulse steps are containerized applications that can be composed tog

StackPulse 14 Jun 14, 2021
Nuclei is a fast tool for configurable targeted vulnerability scanning based on templates offering massive extensibility and ease of use.

Fast and customisable vulnerability scanner based on simple YAML based DSL. How • Install • For Security Engineers • For Developers • Documentation •

ProjectDiscovery 5.2k Sep 22, 2021
A scalable overlay networking tool with a focus on performance, simplicity and security

What is Nebula? Nebula is a scalable overlay networking tool with a focus on performance, simplicity and security. It lets you seamlessly connect comp

Slack 8k Sep 25, 2021
Not Yet Another Password Manager written in Go using libsodium

secrets Secure and simple passwords manager written in Go. It aims to be NYAPM (Not Yet Another Password Manager), but tries to be different from othe

Jarmo Pertman 25 Apr 12, 2021
:key: Idiotproof golang password validation library inspired by Python's passlib

passlib for go Python's passlib is quite an amazing library. I'm not sure there's a password library in existence with more thought put into it, or wi

Hugo Landau 250 Aug 19, 2021