| bio | website | xeoncross.com |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 1 year, 9 months |
| seen | Apr 8 at 16:59 | |
| stats | profile views | 3 |
Another PHP programmer responsible for things like the MicroMVC PHP framework.
You may notice that some of my questions run very deep into the heart of certain issues because I strive for the highest optimization that is possible in my apps.
You may notice that some of my questions run very deep into the heart of certain issues because I strive for the highest optimization that is possible in my apps.
|
May 6 |
awarded | Popular Question |
|
Mar 28 |
comment |
It is reasonably safe to leave a SSH private key with a 30+ character passphrase public? Actually, multiple parties can have a whole copy of the key. There is no sharding/splitting of the key and the only thing remembered is by the original human is the passphrase - the private key is stored somewhere out in the public. |
|
Mar 28 |
revised |
It is reasonably safe to leave a SSH private key with a 30+ character passphrase public? added 500 characters in body |
|
Mar 28 |
comment |
It is reasonably safe to leave a SSH private key with a 30+ character passphrase public? They don't, the physical user of the owning entity must remember it. (If they could remember the RSA key the problem would be solved right there). |
|
Mar 28 |
comment |
It is reasonably safe to leave a SSH private key with a 30+ character passphrase public? The RSA key will be returned to the owning party when it's needed which will then use it to do what it needs done. The problem is that the owning party can't store the key. |
|
Mar 28 |
comment |
It is reasonably safe to leave a SSH private key with a 30+ character passphrase public? The entity to which the private key belongs cannot store it themselves and must use a/multiple 3rd parties to store it. |
|
Mar 28 |
awarded | Editor |
|
Mar 28 |
revised |
It is reasonably safe to leave a SSH private key with a 30+ character passphrase public? added 56 characters in body |
|
Mar 28 |
asked | It is reasonably safe to leave a SSH private key with a 30+ character passphrase public? |
|
Dec 13 |
asked | A single password manager vs password generator/hash |
|
Nov 7 |
comment |
Slow hash algorithm that does not require salt? @StephenTouset, yes. Could be as small as 12 bytes. |
|
Nov 7 |
comment |
Slow hash algorithm that does not require salt? It's for creating slow hashes of objects, using the output, and then discarding it rather than storing it. |
|
Nov 7 |
comment |
Slow hash algorithm that does not require salt? +1 duh, just use a constant salt. I'm not sure why I didn't think of that. |
|
Nov 7 |
accepted | Slow hash algorithm that does not require salt? |
|
Nov 7 |
asked | Slow hash algorithm that does not require salt? |
|
Oct 9 |
accepted | Strength of multiple hash iterations? |
|
Oct 3 |
comment |
When is each key used when encrypting an email using OpenPGP? So if I only had a user's public key - I could encrypt a message just for them (but they won't know if it actually came from me). Likewise, if the person I was sending the message too didn't have a key-pair, all I could do would be sign the message assuming they can get a copy of my public key. |
|
Oct 2 |
comment |
When is each key used when encrypting an email using OpenPGP? So it's possible to only sign or only encrypt a message as well. The reason is I'm wondering what I can do with a sender which has keys and recipient who does not (and vice versa). |
|
Oct 2 |
accepted | When is each key used when encrypting an email using OpenPGP? |
|
Oct 1 |
asked | When is each key used when encrypting an email using OpenPGP? |