Timeline for Is it safe to use a ECDSA public key as a password seed for GCM/AES?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 30, 2014 at 13:53 | vote | accept | ematiu | ||
| Apr 30, 2014 at 13:38 | comment | added | Tom Leek | It is a strange notion, to keep a public key "private". In particular, a public key can be recomputed from a signature (if the signed message is known), so it tends to "leak". In any case, PBKDF2 is meant to strengthen low-entropy secrets which are amenable to exhaustive search; if you "discreet keys" are really private (I doubt it, but hey, let's assume that it happens that way), they don't need PBKDF2; and if they are not private, then PBKDF2 won't make them "more private". | |
| Apr 30, 2014 at 12:57 | comment | added | ematiu | Thanks for your comment. pubkeys in this case are no public..., are derived public keys from a extended public key (en.bitcoin.it/wiki/BIP_0032), what are shared between the peers but not to strangers. | |
| Apr 30, 2014 at 11:28 | history | answered | Tom Leek | CC BY-SA 3.0 |