> On 17 Feb 2017, at 10:06, Dennis Chen wrote:
>
>> On Fri, Feb 17, 2017 at 09:23:00AM +, Ard Biesheuvel wrote:
>>
>>> On 17 Feb 2017, at 09:17, Dennis Chen wrote:
>>>
>>> Hello Ard,
>>> Morning!
On Fri, Feb 17, 2017 at 07:12:46AM +, Ard Biesheuvel wrote:
Hello Libo,
>
On Fri, Feb 17, 2017 at 09:23:00AM +, Ard Biesheuvel wrote:
>
> > On 17 Feb 2017, at 09:17, Dennis Chen wrote:
> >
> > Hello Ard,
> > Morning!
> >> On Fri, Feb 17, 2017 at 07:12:46AM +, Ard Biesheuvel wrote:
> >> Hello Libo,
> >>
> >>> On 17 February 2017 at 03:47, wrote:
> >>> From:
> On 17 Feb 2017, at 09:17, Dennis Chen wrote:
>
> Hello Ard,
> Morning!
>> On Fri, Feb 17, 2017 at 07:12:46AM +, Ard Biesheuvel wrote:
>> Hello Libo,
>>
>>> On 17 February 2017 at 03:47, wrote:
>>> From: Libo Wang
>>>
>>> CTS template assumes underlying CBC algorithm will carry out nex
Hello Ard,
Morning!
On Fri, Feb 17, 2017 at 07:12:46AM +, Ard Biesheuvel wrote:
> Hello Libo,
>
> On 17 February 2017 at 03:47, wrote:
> > From: Libo Wang
> >
> > CTS template assumes underlying CBC algorithm will carry out next IV for
> > further process.But some implementations of CBC alg
Hello Libo,
On 17 February 2017 at 03:47, wrote:
> From: Libo Wang
>
> CTS template assumes underlying CBC algorithm will carry out next IV for
> further process.But some implementations of CBC algorithm in kernel break
> this assumption, for example, some hardware crypto drivers ignore next IV
From: Libo Wang
CTS template assumes underlying CBC algorithm will carry out next IV for
further process.But some implementations of CBC algorithm in kernel break
this assumption, for example, some hardware crypto drivers ignore next IV
for performance consider, inthis case, tcry cts(cbc(aes)) te