From: Santiago Torres Arias <santiago@nyu.edu>
To: Kevin Daudt <me@ikke.info>, git <git@vger.kernel.org>
Subject: Re: SHA-1 chosen-prefix colission attack
Date: Tue, 7 Jan 2020 15:31:48 -0500 [thread overview]
Message-ID: <20200107203147.r33c5plp5g7pmxmj@LykOS.localdomain> (raw)
In-Reply-To: <20200107173111.GB923852@alpha>
[-- Attachment #1: Type: text/plain, Size: 425 bytes --]
> > As a side result, this shows that it now costs less than 100k USD to
> > break cryptography with a security level of 64 bits (i.e. to compute
> > 264 operations of symmetric cryptography).
Just to clarify:
As a stopgap measure, the collision-detection library of Stevens and Shumow [SS17]
can be used to detect attack attempts (it successfully detects our attack).
At the end of section 7.0,
Cheers
-Santiago
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-01-07 20:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-07 17:31 SHA-1 chosen-prefix colission attack Kevin Daudt
2020-01-07 20:31 ` Santiago Torres Arias [this message]
2020-01-08 7:30 ` Jeff King
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=20200107203147.r33c5plp5g7pmxmj@LykOS.localdomain \
--to=santiago@nyu.edu \
--cc=git@vger.kernel.org \
--cc=me@ikke.info \
/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;
as well as URLs for NNTP newsgroup(s).