New answers tagged

0

Meta: Doesn't add much to the dupe but on rereading I notice I missed the "D". Key establishment and encryption/decryption and authentication processes for TLSv1.2 are specified in RFC 5246 TLSv1.2 plus for ECC key exchanges (not here) RFC 4492 TLS ECC as amended by appendix A.7 of 5246. These processes also apply to DTLSv1.2 RFC 6347 DTLSv1.2, although the ...


1

Checking manual page for ssh-keygen gives hints about generating and verifying the parameters (moduli file): ssh-keygen -G moduli-2048.candidates -b 2048 ssh-keygen -T moduli-2048 -f moduli-2048.candidates which sounds for me like a proven way of doing this. But I also discourage you from doing that. The examples what can go wrong are answered in related ...


5

What is the prime represented in? Plain base 16 encoding of actual number. How can it be converted to an actual prime integer? Just convert from base 16. Like so: $ echo "ibase=16;0084F7D46A9654DA8EB0684D8F42FE52A14FDC05F70BF14AFDD\ D0A27B7B4C409DB4D80C2B046E0F6DCFEE29AD25CE87C6E9F81AABC4B8C6E67B5E5B\ 203B656D3C3" | bc ...


0

Stunnel is SSL and, in SSL, private keys never need to travel. The "SSL ethos" is that X.509 certificates are used to authenticate peers without a pre-distributed shared secret. For example, when you connect your Web browser to https://example.com, the SSL layer recognizes the server certificate and can make sure that it talks to the real "example.com" ...


0

No. If you want to use client certificate authentication, then you need to copy the client's private key and certificate to the client from the certificate authority. If you want to allow clients to authenticate a server, then you need to copy the server's private key and certificate from the certificate authority to the server. Exactly how you want to ...


0

Banners can be easily faked. However if a server answers with AES-GCM and TLS1.2 you know you got a pretty new OpenSSL on the other end. I would use nmap's ssl-cipher-enum plugin to determine what protocols and ciphers are available, and map those back to the versions that support them.


6

There is a very extensive article at Wikipedia and it does not make sense to reiterate everything here. But to give you some highlights: It replaces OpenSSL on OpenBSD, OS X since 10.11 and on some other systems. It started with throwing away lots of stuff which was considered useless for the target platforms or insecure by design and it also added some ...


2

There is nothing like a "TLS stack type and version" in the TLS specification. OpenSSL by itself has also no kind of non-standard feature which allows you to ask a server for the version. Thus you don't get such explicit information on the protocol level. You might try to guess the version based on behavior changes or specific ciphers which only exist since ...


0

An X.509 certificate is a format for sharing a public key along with the name of the entity that holds that public/private key pair and optional extensions such as usage. It is usually signed by a certificate authority in order that it is trusted. A X.509 certificate is used in many applications that rely on public/private keys for authentication and/or ...


0

X509 is the type for SSL certificates, these can differ in the purpose they have. When using a SSL connection with a server you use a X509 certificate with the purpose of server authentication: TLS Web Server Authentication (1.3.6.1.5.5.7.3.1) when using it for client authentication (2 way SSL) you need a certificate with TLS Web Client Authentication ...


7

My guess is that this site is using Server Name Indication (SNI). In this case the served certificates depends on the hostname specified in the SNI extension and will often differ if no SNI extension is used. I.e. it will be some completely different default certificate or it will be some old certificate because they only replaced the certificate used for ...


0

Using OpenSSL, this is what you would do: $ openssl req -out codesigning.csr -key private.key -new Where private.key is the existing private key. As you can see you do not generate this CSR from your certificate (public key). Also you do not generate the "same" CSR, just a new one to request a new certificate. As per your comment, if you do not have ...


3

"Insecure Renegotiation" is not about cipher suite selection; it is about a kind of Man-in-the-Middle attack that goes thus: Attacker connects to the server and performs a first handshake. Attacker pushes some data (e.g. an HTTP POST request). Client connects to attacker and sends its initial handshake sequence. Attacker forwards the client handshake ...


1

IF your curl was built to use OpenSSL -- as you tagged but which is not the only option for curl, verify with curl -V -- AND the server is correctly serving any/all intermediate cert(s), THEN to trust the server curl-with-openssl needs a local 'truststore' containing the root cert for the server's cert chain (NOT the server's cert itself) in PEM format. ...


1

Sorry, per the sourcecode you can't prevent the writing of $outdir/$serial.pem and still get your (desired) -out. You could put $outdir someplace like /tmp that gets discarded frequently; or on an OS that allows you to add new filesystem types (Linux at least) you could create a filesystem type that implements a directory such that anything created in it is ...


0

As described on the manpage for openSSL: -out filename the output file to output certificates to. The default is standard output. The certificate details will also be printed out to this file in PEM format (except that -spkac outputs DER format). So it seems this will always write the certificate in a PEM format. You could choose to write these to ...


2

I do not see any public key being "attached" into the CSR. It's there. Here's where: When you generate your key like so: $ openssl genrsa -out server.key 1024 Generating RSA private key, 1024 bit long modulus ....................................++++++ ......++++++ e is 65537 (0x10001) And you generate your CSR like so: $ openssl req -new -key ...


1

I don't want to change my gmail security settings. Is there any way to make an OpenSSL session meet google's security requirements? In theory you could probably do all the necessary communication with openssl. In practice this will probably too hard to do everything by hand. What you would need to do is to use oauth for the authentication, see ...


4

"openssl des3" is really "openssl enc -des3". The password-based key derivation is a custom, undocumented scheme which, as far as password-based key derivation schemes go, is quite weak; see this answer (especially at the end) for some details. Basically, this is equivalent to hashing the password with a couple of MD5 invocations. What matters for passwords ...


0

DES3 uses a maximum key size of 168 bits, so if you must use DES3 then go for the maximum key size. Since you're not memorizing the key yourself you should generate the key from a CPRNG. If you have the option you should consider AES which can have larger key sizes.


3

If openssl was patched recently and you have not restarted all services which are using libssl you may have to reboot your machine in order to complete the openssl patching. By running following command you can see what services are using libssl: lsof | grep -i libssl | grep DEL | awk '{print $1}' | sort | uniq


2

This is a compile-time option, not a run-time option. If you run ./configure --help on the cryptsetup source code, it'll reveal that --with-crypto_backend=openssl will do what you want.



Top 50 recent answers are included