From: Akshat Kumar <akumar@mail.nanosouffle.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] In case anyone worries about block hash collision in
Date: Sun, 7 Feb 2010 15:25:35 -0800 [thread overview]
Message-ID: <fe41879c1002071525t29103057hd693e33f9c6269@mail.gmail.com> (raw)
In-Reply-To: <3be2ae880613957957e63b3de4805c40@yyc.orthanc.ca>
The case of intentional collisions is stronger
than that of accidental collisions. If one were
to worry about the former with regards to
ROT-13, then the idea would be discarded
before the latter ever became an issue.
On Sun, Feb 7, 2010 at 12:57 PM, Lyndon Nerenberg (VE6BBM/VE7TFX)
<lyndon@orthanc.ca> wrote:
>>> Seems to me you should be worried about both.
>>
>> let's not get carried away. the odds of accidental
>> collision are 1 2^80.
>
> And being worried about both leads to the choice of SHA-1 as a suitable
> algorithm. If we weren't worried about it I'm sure some bright light would
> have picked ROT-13 for performance reasons.
>
>
>
next prev parent reply other threads:[~2010-02-07 23:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-06 18:47 [9fans] In case anyone worries about block hash collision in venti maht
2010-02-06 23:42 ` Tim Newsham
2010-02-07 4:47 ` erik quanstrom
2010-02-07 16:54 ` Tim Newsham
2010-02-07 17:44 ` erik quanstrom
2010-02-07 19:12 ` Don Bailey
2010-02-07 19:24 ` Nathaniel W Filardo
2010-02-07 22:08 ` matt
2010-02-08 23:37 ` Nathaniel W Filardo
2010-02-09 13:13 ` hiro
2010-02-09 13:50 ` ron minnich
2010-02-09 14:54 ` erik quanstrom
2010-02-07 20:03 ` Tim Newsham
2010-02-08 21:58 ` Georg Lehner
2010-02-07 20:21 ` [9fans] In case anyone worries about block hash collision in Lyndon Nerenberg (VE6BBM/VE7TFX)
2010-02-07 20:31 ` erik quanstrom
2010-02-07 20:57 ` Lyndon Nerenberg (VE6BBM/VE7TFX)
2010-02-07 23:25 ` Akshat Kumar [this message]
2010-02-08 0:37 ` Russ Cox
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=fe41879c1002071525t29103057hd693e33f9c6269@mail.gmail.com \
--to=akumar@mail.nanosouffle.net \
--cc=9fans@9fans.net \
/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).