Tag Info

New answers tagged

0

Using a private key to encrypt a message that will be decrypted by a public key is a mechanism used, not to ensure privacy, but to ensure non-repudiation, authentication and integrity. These 3 elements form what is commonly known as a digital signature. Of course, you have to know that this process does not disclose your private key.


3

This is the path used when proving the encrypted data hasn't been tempered with, commonly known as a digital signature[1]. The part the diagram leaves out is that the commonly accepted technique for digital signatures is to use a hash function, like SHA-256, to represent the data, then sign the hash. It reduces the amount of data being transmitted and ...


0

Perform some sort swizzle monitoring as mentioned in the guidance found in the OWASP document on Technical Risks of Reverse Engineering and Unauthorized Code Modification This may not solve all attempts at hooking, but it would be a step in the right direction.


2

Currently, Android's device encryption uses dm-crypt and indeed seems to be susceptible to the kind of brute-force attack you mention, because the PIN/password is more or less directly used to derive the key that decrypts the AES key stored in the volume header. To protect against such brute-force attacks, the password has to be of sufficiently high entropy ...



Top 50 recent answers are included