On 3/12/2013 10:57 PM, Chaoxing Lin wrote:
Seems that somehow I got confused, considering the one/single-pass over data
description the same as combined mode algorithm.
I will post a fix or revert the patch if HW does not allow the correct
behaviour.
Horia,
Do you plan to fix talitos
On Thu, 14 Mar 2013 12:21:20 +0200
Horia Geantă horia.gea...@freescale.com wrote:
On 3/12/2013 10:57 PM, Chaoxing Lin wrote:
The freescale crypto engine is still capable of doing AES-CBC + HMAC-SHAxxx
in one shot.
DESC_HDR_TYPE_IPSEC_ESP may not able to achieve authencesn.
Correct. And
On 3/11/2013 9:15 AM, Steffen Klassert wrote:
Ccing Horia Geanta, he did the esn implementation for talitos.
On Fri, Mar 08, 2013 at 03:27:48PM +, Chaoxing Lin wrote:
1. Can any one point me which RFC describe how exactly authencesn should work?
The ESN algorithm is described in RFC
Seems that somehow I got confused, considering the one/single-pass over
data description the same as combined mode algorithm.
I will post a fix or revert the patch if HW does not allow the correct
behaviour.
Horia,
Do you plan to fix talitos driver to make it ESN capable in the near
Ccing Horia Geanta, he did the esn implementation for talitos.
On Fri, Mar 08, 2013 at 03:27:48PM +, Chaoxing Lin wrote:
1. Can any one point me which RFC describe how exactly authencesn should work?
The ESN algorithm is described in RFC 4303 IP Encapsulating Security
Payload (ESP).
2.
1. Can any one point me which RFC describe how exactly authencesn should work?
2. I test Ipsec with esp=aes256-sha512-esn! options and found compatibility
issue between kernel software crypto and talitos driver.
Talitos talitos Good
Soft cryptosoft crypto
