Regarding supported Extension

Hi , I want to add supported extension tag in Client Hello message of DTLS, to tell server that client supports srtp (use_srtp extension) without specifying profile details. How to add extension in the message? Does it require some API call or it reads from some configuration file? Please help

Re: Unable to compile snapshot view (20131115) with fips

Thanks Dr Stephen, I downloaded latest 1.0.2 snapshot and things seem to be working fine. Another query when can we expect 1.1.0 stable release. With regards, Nimit On Mon, Nov 18, 2013 at 6:16 PM, Dr. Stephen Henson st...@openssl.orgwrote: On Mon, Nov 18, 2013, Nimit Gupta wrote: Hi,

OpenSSL FIPS fails with FIPS_DIGESTINIT:disabled for fips

hi all, I compiled openssl 1.0.1e with fips object module 2.0.5. and encrypting with aes256 give me an error in the digest. What digest is it trying to use that's not supported by FIPS? btw, i'm running on windows and compiled openssl to use dynamic libraries instead of statically linking

[openssl.org #3175] [PATCH]

Dear all, there is bad code in test/ideatest.c, line 205: It is not in effect, since the first part (17 Bytes) is larger than one block (line 202). This means the first two blocks (i.e., the whole message) are decrypted correctly. If the second part of CFB_TEST_SIZE-17 bytes is decrypted with the

[openssl.org #3176] Locking problem in fips_drgb_rand.c

The fips_drbg_bytes() function calls CRYPTO_w_lock(CRYPTO_LOCK_RAND); unfortunately the FIPS_drbg_generate() function can eventually call drbg_reseed() if sufficiently enough bytes are pulled out of the DRBG. This function in turn pulls bytes from the MD rand using the RAND_SSLeay()-bytes().

[PATCH 1/4] perlasm/ppc-xlate.pl: VMX and VSX register support

Remove prefix from vrX and vsX registers. --- crypto/perlasm/ppc-xlate.pl | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/crypto/perlasm/ppc-xlate.pl b/crypto/perlasm/ppc-xlate.pl index c075d5f..fc84766 100755 --- a/crypto/perlasm/ppc-xlate.pl +++ b/crypto/perlasm/ppc-xlate.pl

[PATCH 3/4] ppc: include probe for vcipher support

--- crypto/ppccap.c| 8 crypto/ppccpuid.pl | 9 + 2 files changed, 17 insertions(+) diff --git a/crypto/ppccap.c b/crypto/ppccap.c index 2e2f3fc..b38fc09 100644 --- a/crypto/ppccap.c +++ b/crypto/ppccap.c @@ -12,6 +12,7 @@ #define PPC_FPU64 (10) #define PPC_ALTIVEC

[PATCH 0/4] Initial POWER8 support

This patch series adds the initial support for POWER8 new cryptographic instructions. Different versions of the ppc_vcipher_AES_[en|de]crypt were tested and no significant performance gains where found, even using multiple vector registers to load all sub-keys in advance. Because of that, the

[PATCH 4/4] ppc: add AES support for POWER8

Include support for new POWER8 vcipher instructions. It uses OPENSSL_ppccap_P to choose which implementation to use, regular or POWER8. Vcipher instructions use the straightforward decryption described in FIPS-197 instead of the equivalent decryption that requires MixColumns to be applied to

Re: [openssl.org #3157] AutoReply: PATCH Win32/64 openssl 1.0.1e fixes

To make the patch easier to apply, I've attached a patch file which can be applied with: cd directory-holding-openssl-1.0.1e patch -p1 openssl.patch openssl.patch Description: Binary data Leigh -- Leigh M. Smith iZotope, Inc. lsm...@izotope.com +1 (646) 250-1134

Re: [PATCH 4/4] ppc: add AES support for POWER8

Hi, Include support for new POWER8 vcipher instructions. It uses OPENSSL_ppccap_P to choose which implementation to use, regular or POWER8. Nice! We should be able to speed up parallelizable AES block modes like AES-CTR even more. From some test loops I wrote, overlapping 6 iterations should