![]() Tricking users into accepting fake identity keys is more of a social engineering attack than technical attack and has little to do with a server-side foothold. The public components are stored on the server, but are signed by the user’s (private) identity key, protecting them from tampering. The private components of app identity keys are secured in an encrypted client-side data store and out of reach of a server-side attacker. Trick a user into accepting a fake identity key for a target user, which would have the same effect as obtaining the user’s existing identity key. Obtain the private component of an app’s identity key, which could be used to produce authentic ephemeral messaging keys and authenticate messages sent from the app.ģ. ![]() Obtain the private component of a user’s identity key, which could be used to authenticate Wickr apps logged into the account.Ģ. To produce an authentic key (or message), an attacker would need to do one of the following:ġ. Trust is established by verifying the signature chain from a given object or cryptographic component to the root identity, or user (e.g., message to app, app to user). Wickr identities are rooted in asymmetric key pairs that are used to digitally sign and verify data. With these protections in place, attackers hoping to gain access to message content must seek to take control of a Wickr identity. This means that attackers have no ability to read or modify encrypted messages as they pass through the server and they cannot manipulate the key pools to execute man in the middle attacks. However, the messages are encrypted end-to-end and both the encrypted messages and keys in the key pools are authenticated end-to-end. Message securityīy compromising the server, the attacker gains access to encrypted messages as well as public ephemeral key pools. We discuss each type of attack in the sections that follow.
0 Comments
Leave a Reply. |