What you have there is information about an [SSL](https://security.stackexchange.com/questions/83269/tpm-signing-key-or-attestation-identity-key) [certificate](https://en.wikipedia.org/wiki/Public_key_certificate). The certificate identifies a computer, or more precisely a service running on a computer. The numbers after “MD5” and “SHA-1” are “fingerprints” of the certificate: the computer says that it can prove that it knows some secret value which is associated with these fingerprints. (MD5 has known attacks and SHA-1 is deprecated though; today SHA-256 or SHA-512 should be used for this purpose.) There is no way to obtain the secret values from those fingerprints — they're hashes of a [public key](https://en.wikipedia.org/wiki/Public-key_cryptography), and the computer knows the corresponding private key. If you want to understand more about how this works, see https://security.stackexchange.com/questions/20803/how-does-ssl-tls-work The information you have here identify a service running on a computer (e.g. the RDP service). They do not identify a particular user of that computer. They have nothing to do whatsoever with any user's password or with any way in which a remote party could gain access to that computer. The information here is how another computer trying to talk to this computer can know that it's talking to the right computer. Despite the appearance of `sha1WithRSAEncryption`, the information here is related to signatures (roughly speaking, how this computer can sign “yes, I am me”), not to encryption. The word “encryption” here relates to what happens during the TLS protocol, but not to the part where the certificate is directly relevant.