Tag Info

New answers tagged

4

Some implementations of TLS 1.0 did not properly validate the padding as required by the TLS specification. This led to a situation in which the POODLE bug could be leveraged against TLS 1.0, despite the fact that it should be secure against the attack. Later versions of TLS (i.e. 1.1 and 1.2) are inherently secure against POODLE and other padding oracle ...


1

Just dredging up an old question. I recently had need to create a DH cert for test purposes. This is how to do it. First create DH parameters and private key as per Tom's answer: openssl dhparam -out dhparam.pem 1024 openssl genpkey -paramfile dhparam.pem -out dhkey.pem Next create the public key file: openssl pkey -in dhkey.pem -pubout -out dhpubkey.pem ...


1

I don't think you could do this with the usual applications.. If you have your own application using the OpenSSL library you could handle this condition inside the certificate verify_callback. This callback is called on verification for each certificate in the trust chain and you can distrust the certificate by just returning 0. Note that this will cause ...


3

By trusting the Root CA you're trusting their judgement in who they sign. As long as the intermediate CA is valid, not revoked, and you're trusting the Root CA... the chain will always be verified. Other applications (such as NSS) can add additional checks and functionality to provide this, but unless the application provides it it's not really part of the ...


1

As AJ Henderson suggested, the perfect solution would be to have the OpenPGP card sign the CSR. It turned out that is possible with the gpgsm CLI tool. Damien Goutte-Gattat from the GnuPG-user mailing list answered the question: Is there any way to create an X509 CSR signed with the private key stored on the card? Yes, you can use the ...


0

the Java keystore contains certificate information To be more precise it contains public keys or key pairs (public and private key). The keystore is protected by a password and every private key is also protected by a password. However you are able to change or remove passwords. It's up to you. A Java keystore is like a detached keystore of a web browser ...


0

My solution: openssl genrsa -rand large-file-of-quote-random-data -aes256 -out private.key 2048 You will be asked for a password to encrypt the private key. Next use openssl req -new -sha256 -key my-private.key -out csr.pem You will be asked for website params; search the web if you need to know the details. You can then use the contents of csr.pem to ...


0

Yes You are right, the password is protecting the private key. First question here is that already the key got revoked , why do you want to use it the revoked one again. Is there is a intentional reason to work on it ? You can open the public part by using the keytool command.The command follows here keytool -list -keystore -storetype pkcs12 -rfc It ...


1

AES-CTR-256 is only available since OpenSSL v1.0.1. It's possible to view the encoding ciphers by issueing the following command openssl enc help It will show all the available encoding ciphers. To check the current version of OpenSSL run the following command openssl version Note that the 0.9.8, 1.0.0 and 1.0.1 branches have been maintained in ...


1

Disabling SSL3.0 is one of the ways of mitigating POODLE attack. The other way is to apply the TLS_FALLBACK_SCSV patch. There are downsides for TLS_FALLBACK_SCSV as well: Microsoft doesn't support it yet. A bug has been raised in this regard: https://connect.microsoft.com/IE/feedback/details/1002874/internet-explorer-should-send-tls-fallback-scsv Both the ...


1

req -x509 (without -new) requires a CSR on input and you don't say anything about having created a CSR. -key requires a "private-key" file (which in the PKCS#1 CRT form which OpenSSL uses is really keypair) and you say you have that, although it would not normally use a .txt extension. -keyout and -nodes are useless when -key is input; they are for the case ...


0

This question (and answer) is a subset of http://stackoverflow.com/questions/1193529/how-to-store-retreieve-rsa-public-private-key/13104466#13104466 . To compress and tailor that: For an RSA public key you need the modulus and the exponent. It is very common to use either 3 or 65537 (aka F4, the fourth Fermat prime) as the exponent, but not mandatory or ...


2

There are two commonly used formats: DER - binary; data is stored in ASN.1 structure PEM - text; basically it is base64-encoded PEM You can inspect them both for example with openssl asn1parse command or online decoder.


2

Here's nice walkthrough of all the steps you need to do in order to generate self-signed ceritficate. http://www.akadia.com/services/ssh_test_certificate.html You are using wrong parameters. When you are generating new certificate, you've got two inputs - request and private key and one output - the signed certificate. The correct command therefore would ...


5

The TLS_FALLBACK_SCSV draft RFC protects against any downgrade attack. When a client's first handshake attempt fails and it falls back to a lower TLS version (including but not limited to SSL 3), it will include the SCSV, and the server can know that the client wants to support a higher version but was prevented from doing so. If the server also supports a ...


1

(I assume both the AES18 are typos for AES128.) Some early releases of OpenSSL 1.0.1 had a bug that caused a few of the new entries in the cipher table including this one to be selected incorrectly. Using patch e (Feb 2013) or later should fix it. (Or 1.0.2, just released a few weeks ago.) If interested you can see the issue by diffing ssl/s3_lib.c between ...



Top 50 recent answers are included