Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
| From | Dan Purgert <dan@djph.net> |
|---|---|
| Newsgroups | comp.misc |
| Subject | Re: [Link Posting] [Cfrg] Notice on chosen-prefix collisions for SHA-1 |
| Date | 2019-05-13 17:42 +0000 |
| Organization | A noiseless patient Spider |
| Message-ID | <slrnqdjb3i.ds3.dan@djph.net> (permalink) |
| References | <m342G3d+yWNiFpR1l58s6ToQ@dont-email.me> <slrnqdil86.n0k.dan@djph.net> <gjtch5F7v0uU3@mid.individual.net> |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Huge wrote:
> On 2019-05-13, Dan Purgert <dan@djph.net> wrote:
>>
>> Rich wrote:
>>> [...]
>>> The text below is a quotation from the URL above:
>>>>
>>>> We, Gaetan Leurent and myself, would like to emphasize some results we
>>>> will present in a few days at Eurocrypt 2019 [LP19]. ePrint version
>>>> available here: https://eprint.iacr.org/2019/459.pdf
>>>>
>>>> [TL;DR] Chosen-prefix collisions for SHA-1 hash function are now
>>>> practical (cost lower than 100K $), all hope is lost.
>>
>> Finally, something I can use to back up "this is bad, and you should
>> feel bad" when people want to keep from upgrading their ancient setups.
>
> I banned SHA1 at ${MEGABANK} as soon as the theoretical breaks
> became known, with full support of management.
Can I work for you?
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCAAdFiEEBcqaUD8uEzVNxUrujhHd8xJ5ooEFAlzZrHIACgkQjhHd8xJ5
ooG+lggAp39uCWubG6SoZxjaLf5JYhWMHhTZOV4gm3q4FVD8vxMmB17cNWrLi+Y/
JbammMx8EgIXODbvj8awGYCuYrTyD+pS5gVZBEqYsI5VX9Oymaw3jEW3D3xFDg9X
L81ZrQYm9E1Wvf99S20+CPQuLV84x6ZPSTUfGXHtssrQIXK4Lm5SUf4UOPC6Y8Wd
lbsVDeREpHJV5I0BIlAiQNBR/NAOJU1sq7ILUvVTzHcWLKqe8AvkqvfGue+EV4XP
A4o7Mdtl7A+b3nVtcGDXZL7AbxBIFmtdiXrGE587wiNgKP5+ELa842YErEJCtNwA
M2qr6/YLyjMwzr4zk08MqX96+Z7JGg==
=LwLz
-----END PGP SIGNATURE-----
--
|_|O|_|
|_|_|O| Github: https://github.com/dpurgert
|O|O|O| PGP: 05CA 9A50 3F2E 1335 4DC5 4AEE 8E11 DDF3 1279 A281
Back to comp.misc | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[Link Posting] [Cfrg] Notice on chosen-prefix collisions for SHA-1 Rich <rich@example.invalid> - 2019-05-12 03:11 +0000
Re: [Link Posting] [Cfrg] Notice on chosen-prefix collisions for SHA-1 Dan Purgert <dan@djph.net> - 2019-05-13 11:29 +0000
Re: [Link Posting] [Cfrg] Notice on chosen-prefix collisions for SHA-1 Huge <Huge@nowhere.much.invalid> - 2019-05-13 14:16 +0000
Re: [Link Posting] [Cfrg] Notice on chosen-prefix collisions for SHA-1 Dan Purgert <dan@djph.net> - 2019-05-13 17:42 +0000
Re: [Link Posting] [Cfrg] Notice on chosen-prefix collisions for SHA-1 Bob Eager <news0073@eager.cx> - 2019-05-13 21:05 +0000
Re: [Link Posting] [Cfrg] Notice on chosen-prefix collisions for SHA-1 Dan Purgert <dan@djph.net> - 2019-05-13 22:40 +0000
Re: [Link Posting] [Cfrg] Notice on chosen-prefix collisions for SHA-1 Huge <Huge@nowhere.much.invalid> - 2019-05-14 00:18 +0000
csiph-web