lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Wed, 24 Dec 2014 16:57:53 +0000
From:	Ard Biesheuvel <>
To:	Jagannadha Teki <>
Cc:	Jagan Teki <>,
	Yazen Ghannam <>,
	Steve Capper <>,
	Herbert Xu <>,
	"" <>,
	Jagannadha Teki <>
Subject: Re: ARM64 Crypto validation

On 24 December 2014 at 11:47, Jagannadha Teki <> wrote:
> + Yazen Ghannam
> + Herbert Xu
> + Steve Capper
> On Tue, Dec 23, 2014 at 3:45 PM, Jagan Teki <> wrote:
>> Hi,
>> I need some information to validate arm64/crypto, do we have any
>> exact/defined way to validate this.
>> Here are my findings:
>> 1. I see a dirty test module tcrypto.c where we need to give the sec
>> and mode module params as inputs.
>> 2. Validate through open crypto [1]
>> Do we have any arm64 specific validations, Request for help.
>> [1]
> thanks!
> --
> Jagan.
> CONFIDENTIALITY NOTICE: This e-mail message, including any attachments,
> is for the sole use of the intended recipient(s) and contains information
> that is confidential and proprietary to Applied Micro Circuits Corporation or its subsidiaries.
> It is to be used solely for the purpose of furthering the parties' business relationship.
> All unauthorized review, use, disclosure or distribution is prohibited.
> If you are not the intended recipient, please contact the sender by reply e-mail
> and destroy all copies of the original message.

Let's forget you sent this email, so you can start over and:
- work on your tone; I find it hard to care about what *you* need if
you don't take the time to introduce yourself, explain what you are
trying to accomplish, for what purpose and how and to which extent
that purpose aligns with that of our community
- think carefully about what validation of a crypto algorithm
implementation means, and whether it makes sense to do it in an arm64
specific way
- familiarize yourself with the way crypto code is checked for
correctness before it gets merged by Herbert (hint: it is related to
the dirty test module)
- assuming that you are working on Xgene, find out which algorithms in
arm64/crypto can even run on that chip, as it does not have the Crypto
- get rid of the legalese footer, it has no place on an open source mailing list

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists