network profile
| bio | website | goodenoughsecurity.blogspot.c… |
|---|---|---|
| location | Jerusalem, Israel | |
| age | ||
| visits | member for | 9 months |
| seen | Oct 15 '12 at 11:41 | |
| stats | profile views | 0 |
|
Oct 2 |
comment |
How to avoid a chicken and egg scenario with encrypting passwords? I think this statement is meant as a justification for storing the private decrypted key in the http session (because it is very hard to "get a private key out of the RAM of a running process"). In any case, I don't see how keeping a second copy of the private key encrypted with the administrator's public key would make this any worse. |
|
Oct 2 |
awarded | Teacher |
|
Oct 1 |
answered | How to avoid a chicken and egg scenario with encrypting passwords? |
|
Sep 29 |
awarded | Supporter |
|
Sep 29 |
comment |
Self-expiring symmetric keys, or: cryptography in absence of secure deletion But don't they need to store Priv? If not - how can they access their data? |
|
Sep 27 |
comment |
Self-expiring symmetric keys, or: cryptography in absence of secure deletion "My goal is to only bring around Priv, and keep both C and H on a public server." May I ask why you want to keep H on the public server? |
