Krishna, Following is the API documentation for "auth_cipher_text"
* @var odp_crypto_session_params_t::auth_cipher_text * * Controls ordering of authentication and cipher operations, * and is relative to the operation (encode vs decode). * When encoding, @c TRUE indicates the authentication operation * should be performed @b after the cipher operation else before. * When decoding, @c TRUE indicates the reverse order of operation. Logically speaking this seems correct as well. If in encode direction you did cipher first and then auth, then in decode direction you have to follow the reverse order. I hope this clarifies your doubt. Regards Nikhil -----Original Message----- From: lng-odp [mailto:lng-odp-boun...@lists.linaro.org] On Behalf Of Krishna Garapati Sent: Tuesday, September 06, 2016 6:34 PM To: LNG ODP Mailman List <lng-odp@lists.linaro.org> Subject: [lng-odp] issue with odp_crypto validation suite From odp crypto validation suite I see that the application is setting "auth_cipher_text" flag from odp_crypto_session_params to "false" all ways (Irrespective of ENCODE or DECODE). What this means from my understanding is application wants to do "cipher first and then authentication". And in the odp_crypto implementation during session_create if the crypto operation is ENCODE, this flag is set as is against the "odp_crypto_generic_session_t->do_cipher_first" which actually instead leads to do authentication then ciphering during crypto operation. This feels wrong in some way. Any idea about this implementation ?. /Krishna
