Open fabioz23 opened 9 months ago
Hi @rroller ,
do you've already seen this new auth handshake method? If you prefer we can take a look deeper, cab be the "opaque" token used for a 2nd hashing phase?
Hi @fabioz23,
I experienced a similar problem with another camera (DH-IPC-HDW3549H-AS-PV), and temporarily fixed it by restoring the "Compatibility" Authentication method, see #344 .
However, two DH-IPC-PFW3849S-A180-AS-PV cameras with Firmware: 3.140.0000000.10.R,build:2024-01-16 were installed flawlessly (at least, as for access and basic functions, since I just started working on their integration in HA).
With DH-IPC-PFW3849S-A180-AS-PV cameras I experienced another problem, not directly related to HA integration. While installing/setting them using a Dahua NVR, the firmware was only updated to the most recent version for this model (3.140.0000000.10.R,build:2024-01-16) on the first (out of four) installed cameras. I had to manually download and update it for the other three, although model and starting kernel versions were the same for all four cameras.
Hi,
I've tried with a newer cam (DH-IPC-PFW3849S-A180-AS-PV) with fw ver V3.140.0000000.4.R, Build Date: 2023-11-22 and the auth process seems changed and fails.
I've compared an older webUI and this newer cam webUI and in fact the RPC2_Login and RPC2 calls and handshake are a little bit different. In the newer model there's some AES key received by cam and in the RPC2_Login there's an "opaque" token that in the previous version is absent.
I attach the browser recording of new Dahua fw.
Dahua-fw-v3.x.har.zip
Any idea on what changes are made in the auth process?