Re: [openssl-users] Better understanding of EC encryption API

2015-12-02 Thread Jeffrey Walton
> In the past BouncyCastle and Crypto++ could not interop even though > they both claim to follow P1363. IEEE did not publish test vectors, so > each library had a misinterpretation that ensured they did not > interop. Here were the issues for each library: > > * BouncyCastle > - Label shou

Re: [openssl-users] Better understanding of EC encryption API

2015-11-27 Thread Viktor Dukhovni
On Fri, Nov 27, 2015 at 09:36:41AM +, Matt Caswell wrote: > >> OpenSSL only supports ECDH and ECDSA, neither of which can be used to > >> perform encryption. > > > > This is not entirely true, in sufficiently recent versions of > > OpenSSL, ECDSA keys can be used with CMS to encrypt keys. >

Re: [openssl-users] Better understanding of EC encryption API

2015-11-27 Thread Jeffrey Walton
>OpenSSL doesn't support it out of the box. What you're looking for > is something akin to > https://en.wikipedia.org/wiki/Integrated_Encryption_Scheme. +1 on ECIES. If OpenSSL provided one additional, non core feature, ECIES would be at the top of my list. Its hard to use incorrectly, and e

Re: [openssl-users] Better understanding of EC encryption API

2015-11-27 Thread Matěj Cepl
On 2015-11-27, 09:28 GMT, Tim Hudson wrote: > http://www.mail-archive.com/openssl-dev@openssl.org/msg28042.html That’s http://article.gmane.org/gmane.comp.encryption.openssl.devel/17997/ for those afflicted with gmane’s mangling of anything looking like an email address. Matěj -- https://mat

Re: [openssl-users] Better understanding of EC encryption API

2015-11-27 Thread Matt Caswell
On 27/11/15 04:07, Viktor Dukhovni wrote: > On Thu, Nov 26, 2015 at 07:59:22PM +, Matt Caswell wrote: > >> On 26/11/15 19:18, Matt Loah wrote: >>> While the public key in the context of OpenSSL Elliptic Curves algorithm >>> is stored as a EC_POINT pointer... and the private key as a BIGNUM >

Re: [openssl-users] Better understanding of EC encryption API

2015-11-27 Thread Tim Hudson
On 27/11/2015 8:26 AM, Jan Danielsson wrote: > On 26/11/15 20:18, Matt Loah wrote: >> While the public key in the context of OpenSSL Elliptic Curves algorithm is >> stored as a EC_POINT pointer... and the private key as a BIGNUM pointer... >> which functions (or which kind of them) should be called

Re: [openssl-users] Better understanding of EC encryption API

2015-11-26 Thread Viktor Dukhovni
On Thu, Nov 26, 2015 at 07:59:22PM +, Matt Caswell wrote: > On 26/11/15 19:18, Matt Loah wrote: > > While the public key in the context of OpenSSL Elliptic Curves algorithm > > is stored as a EC_POINT pointer... and the private key as a BIGNUM > > pointer... which functions (or which kind of t

Re: [openssl-users] Better understanding of EC encryption API

2015-11-26 Thread Jan Danielsson
On 26/11/15 20:18, Matt Loah wrote: > While the public key in the context of OpenSSL Elliptic Curves algorithm is > stored as a EC_POINT pointer... and the private key as a BIGNUM pointer... > which functions (or which kind of them) should be called to encrypt & to > decrypt a message in C/C++ ?

Re: [openssl-users] Better understanding of EC encryption API

2015-11-26 Thread Matt Caswell
On 26/11/15 19:18, Matt Loah wrote: > While the public key in the context of OpenSSL Elliptic Curves algorithm > is stored as a EC_POINT pointer... and the private key as a BIGNUM > pointer... which functions (or which kind of them) should be called to > encrypt & to decrypt a message in C/C++ ?

[openssl-users] Better understanding of EC encryption API

2015-11-26 Thread Matt Loah
Hi all, While the public key in the context of OpenSSL Elliptic Curves algorithm is stored as a EC_POINT pointer... and the private key as a BIGNUM pointer... which functions (or which kind of them) should be called to encrypt & to decrypt a message in C/C++ ? Matt L.