When the node connects to the server, it announces which key it expects the server to have.

Hamachi nodes authenticate LogMeIn's servers using an RSA keypair.

The server verifies the signature and this authenticates the client.

To log in, the node submits its Hamachi identifier and uses its private key to sign the server's challenge. The LogMeIn servers authenticate Hamachi nodes using an RSA keypair.

Authentication ensures that the identities of everyone in your Hamachi networks, from the LogMeIn Hamachi servers to your Hamachi nodes, are verified.This step, at the beginning of a connection, ensures that data is only exchanged between the correct parties. AuthenticationĪuthentication, in short, is the process of verifying endpoint, user and server identities. While node-to-node traffic (that is, regular VPN flow) typically bypasses LogMeIn's servers and is sent directly from one point to the other, even traffic that has to be relayed through a server is secured and encrypted at the endpoints. LogMeIn Hamachi's security is end-to-end: two Hamachi nodes exchange information with each other after mutual authentication and session key agreement. Nobody will be able to see or access the data transmitted between your computers - not even us. As part of this commitment our datacenters and source code are continually reviewed by independent, accredited third party audit firms to ensure data that your information remains confidential.Īll communications by LogMeIn products use industry-standard algorithms and protocols for encryption and authentication. Our products are architected with security being the most important design objective. At LogMeIn, we take the security and protection of your important files, data, and personal information very seriously.

Download hamachi log me in