Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Stephan Mueller <smueller@chronox.de>
To: Nikolay Borisov <nborisov@suse.com>
Cc: Eric Biggers <ebiggers@kernel.org>,
	herbert@gondor.apana.org.au, davem@davemloft.net,
	linux-crypto@vger.kernel.org, terrelln@fb.com,
	jthumshirn@suse.de
Subject: Re: [PATCH] crypto: xxhash - Implement xxhash support
Date: Tue, 28 May 2019 07:59:17 +0200	[thread overview]
Message-ID: <2084703.uDJgg2HtUG@tauon.chronox.de> (raw)
In-Reply-To: <b9311cb4-3d59-1e97-4967-2f430c4918ad@suse.com>

Am Dienstag, 28. Mai 2019, 07:58:19 CEST schrieb Nikolay Borisov:

Hi Nikolay,

> On 28.05.19 г. 7:58 ч., Stephan Mueller wrote:
> > Please correct me if I am wrong, but as far as I see, however, xxhash
> > seems to be a cryptographic hash function.
> 
> No, xxhash is non-cryptographic. THe official description from
> xxhash.com states:
> 
> xxHash is an extremely fast non-cryptographic hash algorithm, working at
> speeds close to RAM limits. It is proposed in two flavors, 32 and 64 bits.

I see, then please disregard my comment on the FIPS flag then.

Ciao
Stephan



  reply	other threads:[~2019-05-28  5:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-27 14:28 [PATCH] crypto: xxhash - Implement xxhash support Nikolay Borisov
2019-05-27 15:06 ` Stephan Mueller
2019-05-27 19:15   ` Eric Biggers
2019-05-28  4:58     ` Stephan Mueller
2019-05-28  5:58       ` Nikolay Borisov
2019-05-28  5:59         ` Stephan Mueller [this message]
2019-05-27 19:40   ` Nikolay Borisov
2019-05-27 18:39 ` Eric Biggers
2019-05-27 19:06   ` Eric Biggers
2019-05-27 19:55   ` Nikolay Borisov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2084703.uDJgg2HtUG@tauon.chronox.de \
    --to=smueller@chronox.de \
    --cc=davem@davemloft.net \
    --cc=ebiggers@kernel.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=jthumshirn@suse.de \
    --cc=linux-crypto@vger.kernel.org \
    --cc=nborisov@suse.com \
    --cc=terrelln@fb.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox