On 04-01-2019 14:04, Steffen Klassert wrote:
> On Thu, Jan 03, 2019 at 04:16:56PM +0530, Harsh Jain wrote:
>> On 02-01-2019 18:21, Herbert Xu wrote:
>>> Does this occur if you use software crypto on the receiving end
>>> while keeping the sending end unchanged?
>> I tried with "authencesn(hmac(sh
On Thu, Jan 03, 2019 at 04:16:56PM +0530, Harsh Jain wrote:
>
> On 02-01-2019 18:21, Herbert Xu wrote:
> > Does this occur if you use software crypto on the receiving end
> > while keeping the sending end unchanged?
>
> I tried with "authencesn(hmac(sha1-ssse3),cbc(aes-asm))" on both sides.
>
>
On 02-01-2019 18:21, Herbert Xu wrote:
> On Wed, Dec 26, 2018 at 03:16:29PM +0530, Harsh Jain wrote:
>> +linux-crypto
>>
>> On 26-12-2018 14:54, Harsh Jain wrote:
>>> Hi All,
>>>
>>> Kernel version on both machines: 4.19.7.
>>>
>>> Packet drops with EBADMSG is observed on receive end of connectio
On Wed, Dec 26, 2018 at 03:16:29PM +0530, Harsh Jain wrote:
> +linux-crypto
>
> On 26-12-2018 14:54, Harsh Jain wrote:
> > Hi All,
> >
> > Kernel version on both machines: 4.19.7.
> >
> > Packet drops with EBADMSG is observed on receive end of connection. It
> > seems that sometimes crypto driver
+linux-crypto
On 26-12-2018 14:54, Harsh Jain wrote:
> Hi All,
>
> Kernel version on both machines: 4.19.7.
>
> Packet drops with EBADMSG is observed on receive end of connection. It seems
> that sometimes crypto driver receives packet with wrong "seq_hi" value in
> AAD. See below the dump of as
Hi All,
Kernel version on both machines: 4.19.7.
Packet drops with EBADMSG is observed on receive end of connection. It seems
that sometimes crypto driver receives packet with wrong "seq_hi" value in AAD.
See below the dump of assoc data for 1 such instance.
[ 380.823454] assoclen 8th byte 1
