New answers tagged key-generation
des-ede3-cbc OpenSSL will tell you that encryption is des-ede3-cbc if you use asn1parse. Command: $ openssl asn1parse -in privkey.pem -i -dlimit 16 Output: 0:d=0 hl=4 l=1294 cons: SEQUENCE 4:d=1 hl=2 l= 64 cons: SEQUENCE 6:d=2 hl=2 l= 9 prim: OBJECT :PBES2 17:d=2 hl=2 l= 51 cons: SEQUENCE 19:d=3 hl=2 l= ...
If you have control over the environment in which the application runs — basically, if you have access to the account under which the application runs — then you can observe everything it does. Simply run the application under a debugger and put a breakpoint or a trace on calls to CryptGenRandom. If you don't have control over the execution of the program, ...
Look into brute force factorization. If you can leverage a weakness in the PRNG then your factorization time is substantially diminished.
There is a variation of TLS that uses a Pre-Shared Key instead of certificates, called TLS-PSK. This basically works the same way as usual TLS except the session key is generated in a different way. You should take a look at this.
As far as I do understand, you want to convert an authentication subkey to an SSH key, and authenticate using this. If I generate a PGP subkey that only has the authentication capablity and use this to generate an SSH keypair to authenticate Git for example, does this pose a security threat? Whether this is reasonable or not depends on what you're ...
The problem is probably not so much algorithmic security. The problem is that if there is a security problem with one of the applications that you also have a security problem the other application. Furthermore, it may be that some kind of attacks on the protocol may be made possible because you share keys. In other words, this is not a good idea with ...
Top 50 recent answers are included