Hi,
I am implementing ECDH- Group19 (NID_X9_62_prime256v1). I followed the below
sequence.
1. ecdh_group = EC_GROUP_new_by_curve_name(NID_X9_62_prime256v1); //
NID_X9_62_prime256v1 or NID_secp256k1
2. ecdh_keys = EC_KEY_new();
3. ret = EC_KEY_set_group(ecdh_keys, ecdh_group);
4
Hi,
I am implementing ECDH- Group19 (NID_X9_62_prime256v1). I followed the below
sequence.
1. ecdh_group = EC_GROUP_new_by_curve_name(NID_X9_62_prime256v1); //
NID_X9_62_prime256v1 or NID_secp256k1
2. ecdh_keys = EC_KEY_new();
3. ret = EC_KEY_set_group(ecdh_keys, ecdh_group);
4
Hi OpenSSL users,
We are planning to use ECDH Algorithm(Group 19) in an Embedded System Product
for the shared secret key generation.
When I go through the code, I understand that it requires engine
libraries/files from the following folders:
\openssl-3_1_3\crypto\engine\
\openssl-3_1_3
Hi,
I am looking for a example code for ECDH - Group19, There are many API's in the
lib. If you could help me with a simple code with:
1. Initializing the context if any?
2. Selecting ECDH Group 19
3. Private/Public Key Generation
4. Shared secret Key Generation
Or any other
, OpenSSL
On Mon, 2024-07-08 at 12:47 +, Vishal Kevat via openssl-users
wrote:
>
>
>
> Hi OpenSSL,
>
> I am using group 19 which is ECDH elliptic curve group
> (NID_X9_62_prime256v1)and is giving 32 bytes/256 bit of shared secret
> key.
>
> I want to u
Hi OpenSSL,
I am using group 19 which is ECDH elliptic curve group (NID_X9_62_prime256v1)
and is giving 32 bytes/256 bit of shared secret key.
I want to use it to work with AES-128 CBC encryption algorithm. As the key
length generated by ECDH is 32 bytes, is there any way to generate the key
On 18/11/2022 05:53, Viktor Dukhovni wrote:
On Fri, Nov 18, 2022 at 05:12:09AM +, Raman, Ina wrote:
I was trying to test TLS call with cipher suite :
tls_ecdh_ecdsa_with_aes_256_cbc_sha384 but it fails.
You probably actually wanted "ecdhe" not "ecdh", but see belo
On Fri, Nov 18, 2022 at 05:12:09AM +, Raman, Ina wrote:
> I was trying to test TLS call with cipher suite :
> tls_ecdh_ecdsa_with_aes_256_cbc_sha384 but it fails.
You probably actually wanted "ecdhe" not "ecdh", but see below.
> It fails on SSL_set_cipher_list A
Hi ,
I was trying to test TLS call with cipher suite :
tls_ecdh_ecdsa_with_aes_256_cbc_sha384 but it fails .
It fails on SSL_set_cipher_list API . The list contains the mentioned cipher
but still it is failing to set that .
On SIPp UAC side it shows errno = 107 (Transport endpoint is not conne
thing is documented and I'd recommend starting with the migration guide
manual page and working from there.
In my opinion, the 1.0 -> 1.1 transition is the more onerous part.
Pauli
On 23/9/21 3:44 am, Kory Hamzeh wrote:
I have an OpenSSL app which performs ECDH-KAS using openssl-1.0.1g +
erties via config too.
Everything is documented and I'd recommend starting with the migration
guide manual page and working from there.
In my opinion, the 1.0 -> 1.1 transition is the more onerous part.
Pauli
On 23/9/21 3:44 am, Kory Hamzeh wrote:
I have an OpenSSL app which perfo
I have an OpenSSL app which performs ECDH-KAS using openssl-1.0.1g +
openssl-fips-2.0.5. It needs to be FIPS compatible. The app was written using
the low level ECDH functions similar to what is documented here:
https://wiki.openssl.org/index.php/Elliptic_Curve_Diffie_Hellman
on behalf of Henning
Krause via openssl-users
Sent: Sunday, May 23, 2021 2:45 PM
To: openssl-users@openssl.org
Subject: Support for ECDH One-pass in "openssl cms enc"
Hi,
I'm trying to encrypt an email using the ECDH One-Pass algorithm. I've first
created an X509 certific
Hi,
I'm trying to encrypt an email using the ECDH One-Pass algorithm. I've first
created an X509 certificate with an EDSA key based on the curve prime256v1.
Then, I ran this command:
openssl cms -encrypt -in Unencrypted.eml -binary -recip ecc.cer -aes256 -keyopt
ecdh_kdf_md:sha2
On Sun, 2021-03-28 at 09:41 +, Jesús Molina Roldán wrote:
> I would like to know if there is a way to calculate the time spend in
> generate a key pair and in compute the shared secret for the ecdh
> algorithm.
>
> "openssl speed ecdh" only calculate the number of
I would like to know if there is a way to calculate the time spend in generate
a key pair and in compute the shared secret for the ecdh algorithm.
"openssl speed ecdh" only calculate the number of operations in 10s.
Jesus Molina
@openssl.org <mailto:m...@openssl.org>
> <mailto:m...@openssl.org <mailto:m...@openssl.org>>
> > <mailto:m...@openssl.org <mailto:m...@openssl.org>
> <mailto:m...@openssl.org <mailto:m...@openssl.org>>>>
> >
gt; > Matt
> > > >
> > > > >
> > > > > On Tue, Aug 6, 2019 at 3:04 PM Matt Caswell <
> m...@openssl.org
> > <mailto:m...@openssl.org>
> > > <mailto:m...@ope
g Srivastava wrote:
> > > Hi,
> > >
> > > I am implementing HTTPs server using openssl 1.1.1b.
> > > Is it mandatory to setup these API's while creating ssl context ?
> > >
> > > SSL_CTX_set_tmp_ecdh
> > >
&g
gt; > >
> > > I am implementing HTTPs server using openssl 1.1.1b.
> > > Is it mandatory to setup these API's while creating ssl context ?
> > >
> > > SSL_CTX_set_tmp_ecdh
> > >
> > > SSL_CTX_set_tmp_dh
> >
> >
t; On 06/08/2019 09:42, Chitrang Srivastava wrote:
> > Hi,
> >
> > I am implementing HTTPs server using openssl 1.1.1b.
> > Is it mandatory to setup these API's while creating ssl context ?
> >
> > SSL_CTX_set_tmp_ecdh
> >
&
Chitrang Srivastava wrote:
> > Hi,
> >
> > I am implementing HTTPs server using openssl 1.1.1b.
> > Is it mandatory to setup these API's while creating ssl context ?
> >
> > SSL_CTX_set_tmp_ecdh
> >
> > SSL_CTX_set_tmp_dh
>
> By default OpenSSL will
On 06/08/2019 09:42, Chitrang Srivastava wrote:
> Hi,
>
> I am implementing HTTPs server using openssl 1.1.1b.
> Is it mandatory to setup these API's while creating ssl context ?
>
> SSL_CTX_set_tmp_ecdh
>
> SSL_CTX_set_tmp_dh
By default OpenSSL will automati
Hi,
I am implementing HTTPs server using openssl 1.1.1b.
Is it mandatory to setup these API's while creating ssl context ?
SSL_CTX_set_tmp_ecdh
SSL_CTX_set_tmp_dh
Also any suggestion what all options one should set while setting up server
like
SSL_CTX_set_options like SSL_OP_NO_SSLv2 |SSL_OP_NO
Node.js has a bug report and repro of ocsp status not being sent from
a node server to the openssl CLI when TLS1.3 is being used, but only
when server is setting an ecdh curve, with SSL_CTX_set1_curves_list()
repro is https://github.com/sam-github/node-ocsp-bug-repro
TLS trace of success is
enSSL 1.0.2l only ECDHE and DHE are
available, but I do not have the option to define a key length,
so I assume OpenSSL's default key length will be used.
What is the default key length of OpenSSL for DH, DHE, ECDH and ECDHE?
For DHE, the key size is set by the group parameters, for
which t
For the elliptic curve choices, the curve picked (NIST256, NIST384, whatever)
determines the keysize.
--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
, but I
do not have the option to define a key length,
so I assume OpenSSL's default key length will be used.
What is the default key length of OpenSSL for DH, DHE, ECDH and ECDHE?
Thank you and regards,
SaAtomic
--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailma
> with a host device which will be ported with FIPS compliant OpenSSL library.
> Our embedded device will be using ECDSA (FIPS 186-3) and ECDH (FIPS
> SP800-56A) by calling APIs of ATECC508A SDK. Is there any compatibility
> issue?
There shouldn't be. But interop is a
Hi,
We are planning to designing an embedded device integrating ATECC508A module
for PKI support. The embedded device is planned to communicate with a host
device which will be ported with FIPS compliant OpenSSL library. Our embedded
device will be using ECDSA (FIPS 186-3) and ECDH (FIPS
Hi,
I'm trying to establish a TLS/SSL connection between 2 back-end using OpenSSL
library.
The algorithm I would like to use is ECDHE-RSA-AES256-SHA.
At first, I want to generate 2 pairs of ECDH-RSA certificate/key, 1 for the
server & 1 for the client using a root CA as a signed auth
c: w...@openssl.org
Subject: [openssl-users] How to choose ECDH and ECDHE with curve more than
192
Hi,
I am using tomcat server, where I came across a situation where
TestSSLServer(http://www.bolet.org/TestSSLServer/) tool reports the below,
Highly appreciate your expertise in recommendi
HI,
Which is the default and minimum Curve size for ECDH and ECDHE in openssl.
Is it 256 by default?
Thanks & Regards
Raakesh. T
---
[ C-DAC i
Hi,
I am using tomcat server, where I came across a situation where
TestSSLServer(http://www.bolet.org/TestSSLServer/) tool reports the below,
Highly appreciate your expertise in recommending a solution to the finding
where I can choose ECDH curve size greater than 192. In the server
Hello Jakob,
> How does this all compare to the EVP API for traditional
> DH?, I think this is a closer equivalent for API design
> than ECDSA.
Good point. For traditional DH, no Key Derivation Function is mentioned
anywhere. It has a larger associated set of methods (see below) than
On 28/06/2015 04:55, Reinier Torenbeek wrote:
Hi again,
After digging into the ECDH code a bit more, I (sort of) found an answer
to my question.
My reason to look at using the KDF is to apply a hash to the shared
secret to compute a useable key within the derive function. There is a
control
and runnable code, but the EVP_PKEY_CTX_ctrl
invocation is essentially ignored at this moment. Therefore the sha256 does
not actually take place.
On Sat, Jun 27, 2015 at 7:55 PM, Reinier Torenbeek <
reinier.torenb...@gmail.com> wrote:
> Hi again,
>
> After digging into the ECDH code
Hi again,
After digging into the ECDH code a bit more, I (sort of) found an answer
to my question.
My reason to look at using the KDF is to apply a hash to the shared
secret to compute a useable key within the derive function. There is a
control value called EVP_PKEY_CTRL_MD which seems like it
Hi,
My goal is to implement ECDH in my own engine. The snippet below shows
the struct that needs to be filled and set as the engine's ECDH method:
struct ecdh_method {
const char *name;
int (*compute_key) (void *key, size_t outlen, const EC_POINT *pub_key,
E
On Sat, Apr 18, 2015, Q Rius wrote:
> I'm trying to implement CMS encrypt using ECDH keys. Ref openssl CMS with
> ECDH EnvelopedData
> <http://stackoverflow.com/questions/29280688/openssl-cms-with-ecdh-envelopeddata>
> The command line works flawlessly but my pro
I'm trying to implement CMS encrypt using ECDH keys. Ref openssl CMS with
ECDH EnvelopedData
<http://stackoverflow.com/questions/29280688/openssl-cms-with-ecdh-envelopeddata>
The command line works flawlessly but my program is giving an error -
Error Encrypting Data
1405085242
>> Hi,
>> I am playing with openssl 1.0.2a - specifically CMS support for ECC.
>> But what I think should work doesn't.
>> Commands used and parsed data shown.
>> (I gave an RSA example as a known good working example)
>>
>> ./openssl version
>> OpenSSL 1.0.2a 19 Mar 2015
>>
>> echo -n 123456781234
On Thu, Mar 26, 2015, Chris Madden wrote:
> Hi,
> I am playing with openssl 1.0.2a - specifically CMS support for ECC.
> But what I think should work doesn't.
> Commands used and parsed data shown.
> (I gave an RSA example as a known good working example)
>
> ./openssl version
> OpenSSL 1.0.2a 19
Hi,
I am playing with openssl 1.0.2a - specifically CMS support for ECC.
But what I think should work doesn't.
Commands used and parsed data shown.
(I gave an RSA example as a known good working example)
./openssl version
OpenSSL 1.0.2a 19 Mar 2015
echo -n 12345678123456781234567812345678 > sess.
On 23/03/15 14:19, Jakob Bohm wrote:
> On 23/03/2015 14:48, Matt Caswell wrote:
>> On 23/03/15 13:45, Viktor Dukhovni wrote:
>>> On Mon, Mar 23, 2015 at 01:01:29PM +, Matt Caswell wrote:
>>>
> As Viktor states RFC 4492 says if the client sends no TLS extension
> containing the curves
On 23/03/2015 14:48, Matt Caswell wrote:
On 23/03/15 13:45, Viktor Dukhovni wrote:
On Mon, Mar 23, 2015 at 01:01:29PM +, Matt Caswell wrote:
As Viktor states RFC 4492 says if the client sends no TLS extension
containing the curves supported then the server can choose any supported
curve. S
On 23/03/15 13:45, Viktor Dukhovni wrote:
> On Mon, Mar 23, 2015 at 01:01:29PM +, Matt Caswell wrote:
>
>>> As Viktor states RFC 4492 says if the client sends no TLS extension
>>> containing the curves supported then the server can choose any supported
>>> curve. So your fix is to continue w
On Mon, Mar 23, 2015 at 01:01:29PM +, Matt Caswell wrote:
> > As Viktor states RFC 4492 says if the client sends no TLS extension
> > containing the curves supported then the server can choose any supported
> > curve. So your fix is to continue when we reach the second iteration if
> > there a
h
>>> using the \
>>> following cipher/protocol combinations:
>>> ECDH-ECDSA-AES128-SHA ssl3
>>> ECDH-ECDSA-AES256-SHA ssl3
>>> ECDH-ECDSA-DES-CBC3-SHAssl3
>>> ECDH-ECDSA-RC4-SHA ssl3
On 20/0315 15:51, Matt Caswell wrote:
>On 20/03/15 12:44, Linsell, StevenX wrote:
>> On Thu, Mar 19, 2015, Steve Linsell wrote:
>> >
>> Following further testing I see identical failures in the master branch
>> using the \
>> following cipher/protocol com
e that's a bug. I recall a recent discussion that
> specifically pointed out that we should not negotiate ECDH when
> the relevant extension is not sent. We have no idea which curves
> the client supports, and therefore can't choose any.
>
> IIRC the current behaviour is
On Fri, Mar 20, 2015 at 03:51:17PM +, Matt Caswell wrote:
> >> I am trying to use ECDH-RSA-AES256-SHA with ssl3 with s_client and
> >> s_server on
> >> the master branch. (cloned at commit
> >> f7683aaf36341dc65672ac2ccdbfd4a232e3626d) and then ret
On 20/03/15 12:44, Linsell, StevenX wrote:
> On Thu, Mar 19, 2015, Steve Linsell wrote:
>>
>> I am trying to use ECDH-RSA-AES256-SHA with ssl3 with s_client and s_server
>> on
>> the master branch. (cloned at commit
>> f7683aaf36341dc65672ac2ccdbfd4a232e3626
On Thu, Mar 19, 2015, Steve Linsell wrote:
>
> I am trying to use ECDH-RSA-AES256-SHA with ssl3 with s_client and s_server on
> the master branch. (cloned at commit
> f7683aaf36341dc65672ac2ccdbfd4a232e3626d) and then retested with a more
> recent
I am trying to use ECDH-RSA-AES256-SHA with ssl3 with s_client and s_server on
the master branch. (cloned at commit f7683aaf36341dc65672ac2ccdbfd4a232e3626d)
and then retested with a more recent clone: (commit
da27006df06853a33b132133699a7aa9d4277920).
We are running a test suite that tests
Hi All,
I have to prove below things using openssl.
Ca.Sa.G = Sa.Ca.G
* Client *:- private = Ca , public= Ca,G and *Server*:- private=Sa, pub =
Sa.G
I have written the below code for that but dont know how to proceed further
. Please help
void handleErrors(void){
printf("\n Error ");
}
voi
Thanks .. that helps!
-pratyush
On Jun 23, 2014 7:44 PM, "Viktor Dukhovni"
wrote:
> On Mon, Jun 23, 2014 at 07:18:06PM -0400, pratyush parimal wrote:
>
> > Thanks a lot for the clarification. I understand now.
> >
> > Could you also let ne know the same about normal DH operations (not the
> ec
>
On Mon, Jun 23, 2014 at 07:18:06PM -0400, pratyush parimal wrote:
> Thanks a lot for the clarification. I understand now.
>
> Could you also let ne know the same about normal DH operations (not the ec
> counterparts)? Are they supported in v0.9.8 then?
Prime DH is supported in 0.9.8.
--
Hi,
Thanks a lot for the clarification. I understand now.
Could you also let ne know the same about normal DH operations (not the ec
counterparts)? Are they supported in v0.9.8 then?
Regards,
Pratyush.
On Jun 23, 2014 7:07 PM, "Viktor Dukhovni"
wrote:
> On Mon, Jun 23, 2014 at 06:46:29PM -0400
On Mon, Jun 23, 2014 at 06:46:29PM -0400, pratyush parimal wrote:
> So does anyone know how to get the secret derivation working in OpenSSL
> v0.9.8?
The EC support in 0.9.8 is incomplete, and disabled by default.
You should treat 0.9.8 as NOT capable of doing EC.
> Because from what I read I th
Hello users,
I recently wrote a program to do ECDH secret derivation, using OpenSSL
v1.0.1f.
I actually followed the example given at
http://wiki.openssl.org/index.php/Elliptic_Curve_Diffie_Hellman, and I was
able to make it work.
But I need to make the program work on a machine with OpenSSL
On Mon, Jan 20, 2014, Chinmaya Dwibedy wrote:
> Hi Dr. Stephen,
> I had downloaed the openssl-1.0.0d.tar.gz
> from http://www.openssl.org/source/.
> After installation in my Linux system , the #openssl version shows the openSSL
> 1.0.0d-fips.
>
By default OpenSSL is installed under /usr/local/
, 2014, Chinmaya Dwibedy wrote:
> Hi All,
> I downloaded the openssl-1.0.0d.tar.gz. Build the openssl with
> enabled the ec and ecdh (Elliptic curve Diffie???Hellman Group) support as
> stated
> below.
> 1. ./config enable-ec enable-ecdh
> 2. make
> 3. make te
On Mon, Jan 20, 2014, Chinmaya Dwibedy wrote:
> Hi All,
> I downloaded the openssl-1.0.0d.tar.gz. Build the openssl with
> enabled the ec and ecdh (Elliptic curve Diffie???Hellman Group) support as
> stated
> below.
> 1. ./config enable-ec enable-ecdh
> 2. make
Hi All,
I downloaded the openssl-1.0.0d.tar.gz. Build the openssl with
enabled the ec and ecdh (Elliptic curve Diffie–Hellman Group) support as stated
below.
1. ./config enable-ec enable-ecdh
2. make
3. make test
4. make install
But upon checking whether ECDH has
create
> and use keys.
To further build on Dave's comments, there is a discussion on how to
use ECDH in OpenSSL on the Wiki here:
http://wiki.openssl.org/index.php/Elliptic_Curve_Diffie_Hellman
Matt
__
OpenSSL Project
wner-openssl-us...@openssl.org
[mailto:owner-openssl-us...@openssl.org] On Behalf Of M.W. Aruna Withanage
Sent: Monday, September 30, 2013 12:24
To: openssl-users@openssl.org
Subject: *** Spam *** openssl ECDH random number
Hi,
For my MSc project I am using openSSL for encryption and key distribution. I
Hi,
For my MSc project I am using openSSL for encryption and key distribution.
I have a requirement to replace the secret random number(private key)
generated for ECDH with my own random number.
I hope to edit the openSSL source. For that I need to know what is the
source file I need to look at
It appears that the current version of OpenSSL (1.0.1e) disregards the
"no-ec2m" build option (OPENSSL_NO_EC2M) when populating the contents of the
Supported Elliptic Curves Client Hello extension. In other words, the TLS
client code always generates the same 25-element elliptic curve list,
reg
It would be nice to have these in the same way as
SSL_CTX_set_default_passwd_cb_userdata.
k
__
OpenSSL Project http://www.openssl.org
User Support Mailing Listopenssl-users@opens
Just for everyone's benefit, there is a bug in OpenSSL that prevents ECDH-RSA
cipher suites to be negotiated and this has been fixed in the latest stable
snapshot.
For all the folks who recommends that ECDH-RSA and ECDH-ECDSA cipher suites
should not be supported, can you point to liter
parameters needed to
keep DSA and ECDSA safe from attackers, I don't think using the same
private key for ECDSA and ECDH is a good/safe idea.
However I am not a genius cryptanalyst, so I cannot guarantee that
this is really dangerous, it is just a somewhat educated guess.
Not at all - its
e mathematical restrictions on parameters needed to
>>> keep DSA and ECDSA safe from attackers, I don't think using the same
>>> private key for ECDSA and ECDH is a good/safe idea.
>>>
>>> However I am not a genius cryptanalyst, so I cannot guarantee that
>>&g
g the same
private key for ECDSA and ECDH is a good/safe idea.
However I am not a genius cryptanalyst, so I cannot guarantee that
this is really dangerous, it is just a somewhat educated guess.
Not at all - its good advice. Its called Key Separation, and its
covered in the Handbook of Applied Cryptog
eement to the ECC certificate but even then it
> > does not work. Pre-TLS 1.2 cipher suites such as
> > ECDH-RSA-AES128-SHA work fine but just not the TLS 1.2 cipher
> > suites with AESGCM.
>
> Looks like a bug to me. (1.0.1c) s3_lib.c ciphers C031 and C032
> have kE
2 cipher suites such as
> ECDH-RSA-AES128-SHA work fine but just not the TLS 1.2 cipher
> suites with AESGCM.
Looks like a bug to me. (1.0.1c) s3_lib.c ciphers C031 and C032
have kECDHe when it appears they should have kECDHr .
_
On Fri, Nov 2, 2012 at 4:30 PM, Jakob Bohm wrote:
> (continuing TOFU posting to keep the thread somewhat consistent)
>
> Given some of the mathematical restrictions on parameters needed to
> keep DSA and ECDSA safe from attackers, I don't think using the same
> private key for
(continuing TOFU posting to keep the thread somewhat consistent)
Given some of the mathematical restrictions on parameters needed to
keep DSA and ECDSA safe from attackers, I don't think using the same
private key for ECDSA and ECDH is a good/safe idea.
However I am not a genius cryptan
I thought the keys in ECC certificates can be used for both ECDH key agreement
and ECDSA digital signature.
-Original Message-
From: owner-openssl-us...@openssl.org [mailto:owner-openssl-us...@openssl.org]
On Behalf Of Erik Tkal
Sent: Friday, November 02, 2012 8:24 AM
To: openssl-users
> Well one reason is that the fixed ECDH cipher suites do not support forward
> secrecy because they always use the same ECDH key.
ECDHE cipher suites as implemented in OpenSSL don't necessarily
support forward secrecy either. I wonder what it takes to get
SSL_OP_SINGLE_ECDH_USE option
What if the server has an ECDH certificate? Would that then be the appropriate
set of suites?
Erik Tkal
Juniper OAC/UAC/Pulse Development
-Original Message-
From: owner-openssl-us...@openssl.org [mailto:owner-openssl-us...@openssl.org]
On Behalf
On Fri, Nov 02, 2012, Abhiram Shandilya wrote:
> Hi Steve, Thanks for your response. I'm just trying to figure out what it
> takes to get this working - are you of the opinion that an SSL server should
> not support TLS 1.2 ECDH-RSA cipher suites? Could you also mention why?
>
Hi Steve,
Thanks for your response. I'm just trying to figure out what it takes to get
this working - are you of the opinion that an SSL server should not support TLS
1.2 ECDH-RSA cipher suites? Could you also mention why?
I configured my openssl RSA CA to add the key usage extension fo
On Thu, Nov 01, 2012, Abhiram Shandilya wrote:
> I ran openssl s_server with an ECC certificate signed by an RSA Root CA. When
> I try to connect using s_client and a TLS 1.2 ECDH-RSA cipher suite (eg
> ECDH-RSA-AES128-SHA256 or ECDH-RSA-AES128-GCM-SHA256), the connection fails
> w
I ran openssl s_server with an ECC certificate signed by an RSA Root CA. When I
try to connect using s_client and a TLS 1.2 ECDH-RSA cipher suite (eg
ECDH-RSA-AES128-SHA256 or ECDH-RSA-AES128-GCM-SHA256), the connection fails
with s_server printing the following error: "3086918464:
ere it goes:
>>
>> In DH you must exchange the parameters in order to generate the keys for
>> the algorithm to work properly. (Am I wrong?)
>>
>> But in ECDH (accordingly to the code above) I only needed to exchange the
>> public keys without
>> exchanging
On 15/05/12 20:21, Fábio Resner wrote:
I don`t know if this is the correct place to make this conceptual
question but here it goes:
In DH you must exchange the parameters in order to generate the keys
for the algorithm to work properly. (Am I wrong?)
But in ECDH (accordingly to the code
ut in ECDH (accordingly to the code above) I only needed to exchange the
public keys without
exchanging any parameters for key's generation.
Is this particular for ECDH or are the parameter exchange being hidden for
the library?
Thanks,
On Tue, May 15, 2012 at 1:07 PM, Rick Lopes de Souza
wr
tic const int KDF1_SHA1_len = 20;
unsigned char *abuf = NULL;
unsigned char *bbuf = NULL;
OpenSSL_add_all_ciphers();
OpenSSL_add_all_algorithms();
EC_KEY *ecdh = NULL;
EC_KEY *ecdh2 = NULL;
//Generate Public
ecdh = EC_KEY_new_by_curve_name(NID_secp521r
On 15 May 2012 15:22, Fábio Resner wrote:
> Hi,
>
> I'm trying to write an app to generate public/private/shared key for ECDH.
> Here is what I was able to build based on examples:
>
> #include
>
> #define ECDH_SIZE 67
>
> int main() {
> EC_KEY *ecdh =
Hi,
I'm trying to write an app to generate public/private/shared key for ECDH.
Here is what I was able to build based on examples:
#include
#define ECDH_SIZE 67
int main() {
EC_KEY *ecdh = EC_KEY_new();
const EC_POINT *point = NULL;
EC_POINT *point2;
const EC_GROUP *group;
// const
ECDHE is the E=Ephemeral version where you get a distinct DH key for
every handshake.
ECDH has a fixed DH key; one side of the handshake doesn't change from
one instance to the next.
ECDHE gives you forward secrecy; ECDH does not.
ECDHE is less efficient than ECDH; it requires more c
Hello,
I'm trying to make sense out of the various abbrevations used for the
SSL cipher suites listed by openssl ciphers.
I've googled, but found no explanation of what ECDHE is and how it
compares to ECDH.
I'm aware that ECDH stands for "elliptic curve diffie hellman ke
On Nov 21, 2011, at 12:01 , Bodo Moeller wrote:
> On Mon, Nov 21, 2011 at 10:51 AM, Marco Molteni wrote:
>
> The OpenSSL security advisory of 2011-09-06
> (http://www.mail-archive.com/openssl-announce@openssl.org/msg00108.html),
> regarding "TLS ephemeral ECDH crashe
On Mon, Nov 21, 2011 at 10:51 AM, Marco Molteni wrote:
> The OpenSSL security advisory of 2011-09-06 (
> http://www.mail-archive.com/openssl-announce@openssl.org/msg00108.html),
> regarding "TLS ephemeral ECDH crashes in OpenSSL" states that the issue,
> for branch 0.9.
Hi all,
I would like to validate my understanding, please excuse my lack of familiarity
with OpenSSL versioning :-)
The OpenSSL security advisory of 2011-09-06
(http://www.mail-archive.com/openssl-announce@openssl.org/msg00108.html),
regarding "TLS ephemeral ECDH crashes in OpenSSL&qu
On Fri, Nov 4, 2011 at 5:23 PM, John Foley wrote:
> None of the ECDH-RSA cipher suites appear to work in 0.9.8r. Yet they
> work in 1.0.0. Is this expected?
>
Yes -- the OpenSSL 0.9.8 branch includes basic support for elliptic-curve
cryptography, but TLS integration wasn't fini
None of the ECDH-RSA cipher suites appear to work in 0.9.8r. Yet they
work in 1.0.0. Is this expected?
Looking at s3_lib.c, all the older DH-RSA cipher suites are disabled
(SSL_CIPHER->valid=0). But the ECDH-RSA ciphers listed in s3_lib.c are
enabled. This leads to the following questions:
On 08/16/2011 02:58 PM, Dr. Stephen Henson wrote:
> Can you give me a more complete report?
I detailed my situation in a previous recent thread ( Please help:
OpenSSL + OpenVPN Elliptic Curves (SHA512, ECDSA, ECDH, Linux, Debian) ).
Briefly:
- I want to use ECDSA+SHA512 for Open
k for me :(
Can you give me a more complete report?
With me before this change OpenSSL 1.0.0 and later couldn't handle anything
other than SHA1 signed ECDSA certificates for static ECDH ciphersuites, after
this change it worked fine.
Steve.
--
Dr Stephen N. Henson. OpenSSL project cor
1 - 100 of 147 matches
Mail list logo
