rfc:timing_attack
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
rfc:timing_attack [2014/02/02 22:46] – realityking | rfc:timing_attack [2017/09/22 13:28] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Request for Comments: Timing attack safe string comparison function ====== | ====== Request for Comments: Timing attack safe string comparison function ====== | ||
- | * Version: 1.o | + | * Version: 1.0 |
* Date: 2013-12-22 | * Date: 2013-12-22 | ||
- | * Author: Rouven Weßling, me@rouvenwessling | + | * Author: Rouven Weßling, me@rouvenwessling.de |
- | * Status: | + | * Status: |
* First Published at: http:// | * First Published at: http:// | ||
Line 43: | Line 43: | ||
===== Vote ===== | ===== Vote ===== | ||
- | <doodle title=" | + | <doodle title=" |
* Yes | * Yes | ||
* No | * No | ||
Line 60: | Line 60: | ||
* 0.1 Initial publication | * 0.1 Initial publication | ||
* 0.2 Renamed to hash_compare, | * 0.2 Renamed to hash_compare, | ||
- | * 1.0 Moved function to ext/hash. Started voting. | + | |
+ | * 1.1 Added section about differences between RFC and implementation | ||
+ | |||
+ | ===== Differences between this RFC and the implementation ==== | ||
+ | * The function is now called hash_equals | ||
+ | * Both arguments passed to the function have to be strings, otherwise an E_WARNING is raised. |
rfc/timing_attack.1391381196.txt.gz · Last modified: 2017/09/22 13:28 (external edit)