[openssl-users] Reg : SCEP using OPENSSL

Hi all, I need guidance in understanding as to how SCEP server can be used & integrated with OpenSSL. My understanding is that SCEP can be used to enroll devices & then it communicates to Certificate Authority that generate certificates. Can some one point me in right direction ? Basically i am

[openssl-users] SSL_ERROR_WANT_READ but nothing to read

HI, I have a client application using a single read-write socket in non-blocking mode. In C, on Linux, using openssl 1.0.1e. After the connection is established and all the initial handshaking is done, the client issues SSL_read(), then enters a loop of: - Interpret results (such as b

Re: [openssl-users] Forthcoming OpenSSL releases

Thanks for the heads up. Just to confirm, is this "highest severity defect" a yet-to-be-disclosed vulnerability, or a fix for an already known one? Sent from my mobile > On Mar 16, 2015, at 3:05 PM, Matt Caswell wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > > Forthcoming Ope

Re: [openssl-users] How to select supported signature algorithms

On Mon, Mar 16, 2015, Jacques FLORENCE wrote: > Hello, > I am developing a simple client/server application with openSSL. > > Using wireshark, I can see in the Client Hello message that there is an > extension signature_algorithms, in which are fields Signature Hash > Algorithms. > I can see a lo

[openssl-users] How to select supported signature algorithms

Hello, I am developing a simple client/server application with openSSL. Using wireshark, I can see in the Client Hello message that there is an extension signature_algorithms, in which are fields Signature Hash Algorithms. I can see a lot of supported algorithms, such as RSA, DSA, ECDSA in the fie

[openssl-users] Forthcoming OpenSSL releases

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Forthcoming OpenSSL releases The OpenSSL project team would like to announce the forthcoming release of OpenSSL versions 1.0.2a, 1.0.1m, 1.0.0r and 0.9.8zf. These releases will be made available on 19th March. They will

Re: [openssl-users] FIPS: ECC licensing

On 03/16/2015 01:55 PM, jonetsu wrote: > Hello, > > The licenses, patents for ECC was noticed. In short, if we do not > care about this in the sense of not willing to be in any patent > infringement situation down the road, the -ecb archive should be > used, is that right ? It's "ecp", not "ecb"

Re: [openssl-users] FIPS: Converting AES_ctr128_encrypt() to EVP_ methods

On Mon, Mar 16, 2015, jonetsu wrote: > Hello, > > An application that needs converting to FIPS is currently using > AES_ctr128_encrypt().  That function calls in turn > CRYPTO_ctr128_encrypt() which then does some internal > computations.  They are not documented in the 'full list of > crypto API

[openssl-users] FIPS: ECC licensing

Hello,   The licenses, patents for ECC was noticed.  In short, if we do not care about this in the sense of not willing to be in any patent infringement situation down the road, the -ecb archive should be used, is that right ?  Also, there is a mention of a NSA-PLA.pdf agreemnet statement.  The

[openssl-users] FIPS: Converting AES_ctr128_encrypt() to EVP_ methods

Hello, An application that needs converting to FIPS is currently using AES_ctr128_encrypt().  That function calls in turn CRYPTO_ctr128_encrypt() which then does some internal computations.  They are not documented in the 'full list of crypto APIs'.  What would be the FIPS-compatible EVP equivalen