network profile
| bio | website | |
|---|---|---|
| location | Helsinki, Finland | |
| age | 34 | |
| visits | member for | 2 years, 6 months |
| seen | Jun 2 at 21:44 | |
| stats | profile views | 38 |
|
May 19 |
awarded | Good Question |
|
May 18 |
awarded | Notable Question |
|
May 2 |
awarded | Self-Learner |
|
Mar 19 |
awarded | Nice Answer |
|
Mar 18 |
comment |
How would one crack a weak but unknown encryption protocol? Not an unreasonable position, if you are proficient enough to combine the algorithms safely without introducing new vulnerabilities. Another choice, if you are proficient enough, is to make a trivial modification to a well known algorithm and keep the modification secret. However, in the real world, you are almost 100% guaranteed to make things worse by adding something to it - cryptography is hard, even though it might at times seem like it isn't. |
|
Mar 18 |
answered | How would one crack a weak but unknown encryption protocol? |
|
Mar 18 |
comment |
Converting keys between openssl and openssh I did, although I am beginning to doubt this will actually be useful for you - if you are still wishing for ideal back-and-forth conversion without losing data, that is just not a meaningful goal. |
|
Mar 18 |
revised |
Converting keys between openssl and openssh added one more way to call the commands |
|
Mar 18 |
comment |
Converting keys between openssl and openssh You can, the private key is already in a compatible format so you can just use that in the OpenSSL command. |
|
Mar 18 |
revised |
Converting keys between openssl and openssh added 64 characters in body |
|
Mar 18 |
revised |
Converting keys between openssl and openssh added 79 characters in body |
|
Mar 18 |
revised |
Converting keys between openssl and openssh added 79 characters in body |
|
Mar 18 |
answered | Converting keys between openssl and openssh |
|
Mar 18 |
answered | Is request signing (digesting the request body) in a REST API necessary? |
|
Mar 18 |
answered | Are passwords stored in memory safe? |
|
Mar 17 |
accepted | Standards for secure key backup of master keys with secret sharing |
|
Mar 17 |
comment |
Standards for secure key backup of master keys with secret sharing Thanks! I agree that any key backup of a non-exportable key must be proprietary, as it must somehow authenticate the backup device as "secure". However, I see no theoretical reason why PKCS#11 could not have a "export for multiple custodians" method in addition to the normal key wrapping method - although for practical reasons it doesn't. Also in many master key setups (such as a root CA key) the key actually is generated in a manner which allows a "portable" backup of the key by standard methods during key generation only - to avoid lock-in with a vendor, and to keep the key recoverable. |
|
Mar 16 |
revised |
Are any Java Card 3.0 smart cards available? Added a lot more information. |
|
Mar 16 |
answered | Are any Java Card 3.0 smart cards available? |
|
Mar 16 |
asked | Standards for secure key backup of master keys with secret sharing |
