-
-
Notifications
You must be signed in to change notification settings - Fork 514
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to access camera with custom password #255
Comments
> DESCRIBE rtsp://admin:[email protected]:8554/live.sdp RTSP/1.0 > 401
EDIT: Nevermind, I made a mistake when setting up the camera. It works on my side now 🤔 Could you please share the full log of cameradar for me to figure out what's wrong? |
Sending log file. VLC can monitor the Besder 6024PB-JW201 1080p camera via this link: |
The issue you have is a duplicate of #247, which has been fixed in #252 :) * Trying 192.168.0.226:554...
* TCP_NODELAY set
* Connected to 192.168.0.226 (192.168.0.226) port 554 (#0)
* Server auth using Digest with user 'admin'
> DESCRIBE rtsp://admin:[email protected]:554/ RTSP/1.0
CSeq: 1
Accept: application/sdp
< RTSP/1.0 401 Unauthorized
< CSeq: 1
< WWW-Authenticate: Digest realm="HIipCamera",nonce="e410540f98c2aca4da5d729a3304090c"
<
* Connection #0 to host 192.168.0.226 left intact
* Issue another request to this URL: 'rtsp://admin:[email protected]:554/'
* Protocol "rtsp" not supported or disabled in libcurl
* Closing connection -1 All you need to do is to upgrade to the latest version of cameradar ( |
While using the VLC I can monitor the Besder 6024PB-JW201 1080p camera via this link:
rtsp://admin:[email protected]:554/onvif1
I did a test by my camera with "Cameradar v4.1.2", I inserted the password "password123" into the "credentials.json" file. The required route "onvif1" already exists in the "routes" file.
then I started the "Cameradar"
./cameradar -t 192.168.0.228
When I run the "Cameradar" on the screen, I see "Cameradar" trying different combinations of usernames and passwords.
For example:
Later the program starts checking the routes, but as far as I can see the front of the rtsp:// link no longer has username and password values
"rtsp://:@192.168.0.228: 554/cam/realmonitor"
For example:
The program reports when the job is complete - that did not find the correct username and password Also prints wrong path "RTSP route: /cam/realmonitor"
For example:
Am I doing something wrong, or is there a bug in the program?
Maybe you can create an option when the route is known, "Cameradar" would bruteforce only the username and password?
The text was updated successfully, but these errors were encountered: