Timeline for Key-size of encryption method
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2017 at 12:48 | history | edited | CommunityBot |
replaced http://crypto.stackexchange.com/ with https://crypto.stackexchange.com/
|
|
| Oct 18, 2013 at 20:03 | comment | added | e-sushi | @PaŭloEbermann Valid point. But I have good hopes OP discovered the different hash-types PHP offers in that functions. ;) | |
| Oct 18, 2013 at 19:47 | comment | added | Paŭlo Ebermann | For password based keys derivation (i.e. where the input entropy is significantly below your key size), you should better use a slow hash function instead of any fast one like SHA-256. | |
| Oct 11, 2013 at 15:40 | comment | added | e-sushi |
@stUrb Absolutely correct. That's one of many reasons why I recommended it… ;) As noted, remember to set that 3rd parameter to TRUE to be sure you get binary instead of hex characters in your $sleutel. (Btw.: Vlaams of Nederlands? In ieder geval, graag gedaan!)
|
|
| Oct 11, 2013 at 15:38 | vote | accept | stUrb | ||
| Oct 11, 2013 at 15:37 | comment | added | stUrb |
Wow. Thank you e-sushi for this elaborate answer! Am I correct that with your recommended solution I always will produce a correct size key, no matter the size of $this-sleutel.$this->userKey ?
|
|
| Oct 11, 2013 at 14:52 | history | edited | e-sushi | CC BY-SA 3.0 |
added 12 characters in body
|
| Oct 11, 2013 at 14:46 | history | edited | e-sushi | CC BY-SA 3.0 |
added 132 characters in body
|
| Oct 11, 2013 at 14:33 | history | edited | e-sushi | CC BY-SA 3.0 |
added 132 characters in body
|
| Oct 11, 2013 at 14:21 | history | edited | e-sushi | CC BY-SA 3.0 |
Added final line to wrap up the answer.
|
| Oct 11, 2013 at 14:16 | history | answered | e-sushi | CC BY-SA 3.0 |