FIPS, continuous tests, and error reporting

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




-----Original Message----- 
> From: "Salz, Rich" <rsalz at akamai.com> 
> To: openssl-users at openssl.org 
> Date: 02/19/15 07:43 
> Subject: Re: [openssl-users] FIPS, continuous tests, and error reporting 
> 
> > For that matter and in a general sense, so far I've seen that many encryption
> > methods do not return any error code. ?How does error reporting generally
> > works ?
> 
> Really? ?Which ones?

For instance, any of the void DES_*_encrypt().? This cursory observation is also supported by a vendor application code such as:

?static void des_encrypt(char key1[8], char key2[8], char key3[8], char ivec[8],
???????????????? char *input, char *output, int len,
???????????????? int encrypt)
?{

?? [snip]

??? DES_set_key(&des_key1, &schedule1);
??? DES_set_key(&des_key2, &schedule2);
??? DES_set_key(&des_key3, &schedule3);
??? DES_ede3_cbc_encrypt((unsigned char *)input, (unsigned char *)output, len,
???????????????????????? &schedule1, &schedule2, &schedule3, &des_ivec,
???????????????????????? encrypt);
?}


This is basically why I'm wondering about how errors propagate in the OpenSSL library.






[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux