Timeline for Cipher for Product Registration?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 22, 2011 at 0:09 | vote | accept | Anti Earth | ||
| Nov 15, 2011 at 15:06 | comment | added | Stefano Palazzo | If you're going to send binary data to the user, it makes sense to encode it in something other than hexadecimal. Take a look at Crockford's Base32, which avoids characters that can be confused easily. | |
| Nov 14, 2011 at 21:20 | comment | added | Anti Earth | That's what I originally intended to do, but with DES. Yeah, maybe I will. | |
| Nov 14, 2011 at 16:52 | comment | added | woliveirajr | I thought the OP just wanted a very simple "make the regular user contact me to get a very short key" kind of protection, and the solution I provided is more than enought for that. | |
| Nov 14, 2011 at 16:02 | comment | added | Ilmari Karonen | @Paŭlo: Generally I'd agree, but in this case that's a bit like recommending the use of packing tape instead of office tape for holding a cardboard house together. Technically, your advice is good, but the hash is far from the weakest link here. | |
| Nov 14, 2011 at 12:03 | comment | added | Paŭlo Ebermann |
Preferably use MAC(secret, username) instead of a simple hash (use HMAC, for example).
|
|
| Nov 14, 2011 at 11:40 | history | answered | woliveirajr | CC BY-SA 3.0 |