meta user
network profile
| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 1 year, 7 months |
| seen | 1 hour ago | |
| stats | profile views | 2 |
|
10h |
revised |
Is Base64(SHA1(GUID)) still unique like the original GUID? added 369 characters in body |
|
11h |
revised |
Is Base64(SHA1(GUID)) still unique like the original GUID? added 369 characters in body |
|
11h |
revised |
Is Base64(SHA1(GUID)) still unique like the original GUID? added 369 characters in body |
|
11h |
answered | Is Base64(SHA1(GUID)) still unique like the original GUID? |
|
May 15 |
awarded | Popular Question |
|
May 11 |
accepted | Recommended way of adding a pepper/secret key to password before hashing? |
|
May 8 |
revised |
Recommended way of adding a pepper/secret key to password before hashing? added 2 characters in body |
|
May 8 |
revised |
Recommended way of adding a pepper/secret key to password before hashing? added 114 characters in body |
|
May 8 |
comment |
Recommended way of adding a pepper/secret key to password before hashing? @Henrick Hellström: Changed. Thanks. :) I'm not sure I understand the reasoning. Feel free to edit the question to improve it. :) |
|
May 8 |
revised |
Recommended way of adding a pepper/secret key to password before hashing? edited body |
|
May 8 |
asked | Recommended way of adding a pepper/secret key to password before hashing? |
|
Jan 28 |
awarded | Critic |
|
Jan 26 |
comment |
Hashing passwords with a salt - why use different salt for everyone? @dchest if you're using a hash so computationally expensive that brute-forcing even a single password hash is unfeasible, then why bother with a 'static' pseudo-salt at all? The salt is there to prevent cost-sharing on brute-force attacks against KDFs; but you're proposing a KDF so heavy that brute-forcing it is unfeasible. But maybe you'd like to use a MAC together with a 'pepper' before the KDF: security.stackexchange.com/questions/3272/… |
|
Jan 26 |
revised |
Hashing passwords with a salt - why use different salt for everyone? added 23 characters in body |
|
Jan 25 |
awarded | Editor |
|
Jan 25 |
revised |
Hashing passwords with a salt - why use different salt for everyone? added 174 characters in body |
|
Jan 25 |
answered | Hashing passwords with a salt - why use different salt for everyone? |
|
Dec 30 |
comment |
Future-Proof Versioning and Validation @andrew cooke: Respectfully, perhaps you should consider contributing to Google Keyczar instead. Programmers need a small number of extremely well-tested crypto libs, because crypto is fiendishly difficult to implement. Here is an example from Keyczar: rdist.root.org/2009/05/28/… |
|
Oct 12 |
awarded | Yearling |
|
Jul 15 |
awarded | Nice Answer |
