pgpfan:mdc
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
| pgpfan:mdc [2022/07/19 00:40] – Protection b.walzer | pgpfan:mdc [2022/07/22 15:50] – Readers might not know what a hash is. b.walzer | ||
|---|---|---|---|
| Line 13: | Line 13: | ||
| {{mdc1.svg}} | {{mdc1.svg}} | ||
| - | We create this by hashing the message. Then we append the hash to the end of the message. After that we encrypt everything; message and hash. To check for modification we hash the message and compare that hash to the hash appended to the message. | + | We create this by [[wp> |
| Let's consider the easiest situation for the attacker and assume they know the entire message. Then the attacker can hash that known message and will then know what the hash was before encryption. As a result they can modify the hash to any value they want by flipping bits as required. So the attacker can change the message to anything they want without restriction and can change the hash so that their changes would not be detected. If their target message is shorter than the original they can just generate the hash early and drop the extra part. So this is not entirely secure. | Let's consider the easiest situation for the attacker and assume they know the entire message. Then the attacker can hash that known message and will then know what the hash was before encryption. As a result they can modify the hash to any value they want by flipping bits as required. So the attacker can change the message to anything they want without restriction and can change the hash so that their changes would not be detected. If their target message is shorter than the original they can just generate the hash early and drop the extra part. So this is not entirely secure. | ||
pgpfan/mdc.txt · Last modified: 2023/12/11 13:30 by b.walzer