notes about hash security
This commit is contained in:
parent
d6ded4c8c3
commit
e00f8f1d1e
@ -24,3 +24,15 @@ In English: _Only inputs can find outputs, not the other way around._
|
|||||||
* Two-way property/ Collision-free Property
|
* Two-way property/ Collision-free Property
|
||||||
|
|
||||||
**2** identical data inputs will map to the same output
|
**2** identical data inputs will map to the same output
|
||||||
|
|
||||||
|
## What does a hash provide?
|
||||||
|
|
||||||
|
* Integrity checks
|
||||||
|
|
||||||
|
* Message Digest / Authentication
|
||||||
|
|
||||||
|
_Hashes are not secure ffs_. When we say authentication we really mean that we are checking to ensure there has been no changes to the original message.
|
||||||
|
_NOTE:_ this really doesn't guarantee anything in communications susceptible to man-in-the-middle attacks.
|
||||||
|
|
||||||
|
Let's get real for minute: Think of it this way a message is like a car and the key is our hash. If the key doesn't fit in the slot then its not our car, **but** if we sent our car + key oversees whoever steals the car + key has full control and we lose security effectively. Using SSL is _kinda_ like putting that car + key combo in a box that nobody except the recipient can open.
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user