RE: FIPS verification for AES XTS

I also need to test CCM and GCM mode and realized that I cannot use the CLI for that. So, I started writing a program to do the tests (wanted to avoid this). The XTS works with the data from the one file, but I still do not understand how to make use of the data unit sequence number - anybody!?

Re: FIPS verification for AES XTS

On 11/25/2013 05:51 AM, Leon Brits wrote: Hi, I need to perform some Known-Answer-Tests with every start-up of my system. ... You're trying for your own private label validation. The OpenSSL FIPS Object Module was a good model for that (by design), but note the CMVP has recently introduced

[openssl.org #3182] Bug in OpenSSL 1.0.1e 586 assembly optimized AES_cbc_encrypt

I've noticed what appears to be a bug in the 586 assembly-optimized AES_cbc_encrypt function of OpenSSL 1.0.1e, (compiled on Windows) when encrypting data that is 1 block in length, but not an integral multiple of the block size. Specifically it appears that when encrypting the partial-block

Re: [openssl.org #2316] Build issue on Tru64 (Dl_info must specify a type)

I'm reluctant to open an old issue, but Tru64 v5.1 is a corner case unfortunately not covered by this fix. (Andy: I am seeing this error now that I am building OpenSSL with non-default build options.) /usr/include/dlfcn.h on this system #defines RTLD_NEXT, but neither Dl_info nor dladdr() are

Re: [openssl.org #3097] Incorrect revocation status with indirect CRL

Hi Craig, I'm trying to do the same - can you share either the openssl.cnf files or the cert/crl files the enabled you to get this working? The examples you provided in the thread were for Stephen Henson's, but I want to try the more official route... Thanks, Kent I also managed to get my

Re: [openssl.org #2316] Build issue on Tru64 (Dl_info must specify a type)

I'm reluctant to open an old issue, but Tru64 v5.1 is a corner case unfortunately not covered by this fix. (Andy: I am seeing this error now that I am building OpenSSL with non-default build options.) /usr/include/dlfcn.h on this system #defines RTLD_NEXT, but neither Dl_info nor dladdr() are

Re: [openssl.org #3165] tru64-alpha-cc compatibility fixes

I am now building OpenSSL with non-default arguments, and am thus seeing a new build error on Tru64 v5.1: cc -I.. -I../.. -I../modes -I../asn1 -I../evp -I../../include -DOPENSSL_THREADS -pthread -DDSO_DLFCN -DHAVE_DLFCN_H -std1 -tune host -fast -readonly_strings -DOPENSSL_BN_ASM_MONT -DSHA1_ASM