![Remote Remote](/uploads/1/2/5/4/125447164/807148449.png)
I installed the root cert from my local CA in the System keychain and set it to Always Trust, then on the Windows Server side, using Administrative Tools -> Remote Desktop Services -> Remote Desktop Session Host configuration, I updated the certificate assigned to the RDP-Tcp connection. Right-click RDP-Tcp Connection, choose Properties. Install the certificate used by the remote machine into your local machine Trusted Root Certification Authorities store Use a certificate signed by someone both computers trust The first option is what most people do and it is perfectly fine to do that.
This APK is signed by AnyDesk Software GmbH and certificated by APKdot. File hashes: MD5: 871e16a1bcb57da1102cf82a8582c5e9 SHA-1: aae0ff062260c721d1fe54cd3c1fc0 Why using SHA1 to check the identification of certificate is safe?
That’s a cryptography problem. Please refer to the following authoritative information to check the reason. How do we make sure the updated Apps are real and created by the respective developers?
All APKdot.com apps are verified prior to publishing. We make sure that the cryptographic signatures for new versions of all previously published apps match the original ones, which means we know if the new version APKs were signed by the real devs or someone pretending to be them. For new apps that have never been published on APKdot.com, we try to match the signatures to other existing apps by the same developer. If there’s a match, it means that the same key was used to sign a previously known legitimate app, therefore validating the new upload. If we’re unable to verify the legitimacy of a new APK, we will simply not publish it on APKdot.com.