All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean-Luc Cooke <jlcooke@certainkey.com>
To: linux-kernel@vger.kernel.org
Subject: [jlcooke@certainkey.com: Re: SHA-0]
Date: Fri, 13 Aug 2004 09:15:33 -0400	[thread overview]
Message-ID: <20040813131533.GI2192@certainkey.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1 bytes --]



[-- Attachment #2: Type: message/rfc822, Size: 1822 bytes --]

From: Jean-Luc Cooke <jlcooke@certainkey.com>
To: James Morris <jmorris@redhat.com>
Cc: lkml@vger.kernel.org
Subject: Re: SHA-0
Date: Fri, 13 Aug 2004 09:13:50 -0400
Message-ID: <20040813131350.GH2192@certainkey.com>

No it does not...we think...

SHA-0 is the nick-name for the first draft of SHA put forward by NIST/NSA of
the US Gov't.  Cryptographers got up in arms about how it had a "lazy bit" (a
bit that does not effect the output of the hash) and how it did not have
enough rounds.

So, they named the "first" SHA SHA-0 because it wasn't good enough.  And
SHA-1 the "first released" SHA.  SHA-1 was designed to be stronger than
SHA-0 in at least one of the ways SHA-0 was recently exploited.

Still, this is a very interesting development in the field of hash function
cryptanalysis.  Biham should be co-presenting a paper explain how they did
it soon.  They give allusion to a possible attack on SHA-1...but I hear it's
still theoretical.

SHA-256 is looking better.  Though SHA-1 is still strong enough, it may not
last to its 2012 "expiry date" for vulnerabilities to collision attacks set
by Lenstra/Verheul in (1).

Cheers,

JLC

(1) Selecting Cryptographic Key Sizes</a> by Arjen K. Lenstra, Eric R. Verheul
    <http://www.cacr.math.uwaterloo.ca/conferences/1999/ecc99/lenstra.doc>

On Thu, Aug 12, 2004 at 11:12:03PM -0400, James Morris wrote:
> Hi Jean-Luc,
> 
> I read on sci.crypt about the SHA-0 collision, do you know if this casts 
> doubt on SHA-1?
> 
> - James
> -- 
> James Morris
> <jmorris@redhat.com>
> 

                 reply	other threads:[~2004-08-13 13:21 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20040813131533.GI2192@certainkey.com \
    --to=jlcooke@certainkey.com \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.