From: Paul Lalonde <plalonde@telus.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: [9fans] Venti security in view of SHA-1 exploit
Date: Sat, 19 Feb 2005 11:20:18 -0800 [thread overview]
Message-ID: <9e8b82886fac51f78a70e17b6ba26813@telus.net> (raw)
In-Reply-To: <ee9e417a0502191058484e4422@mail.gmail.com>
Has anyone given any thoughts on how Venti might be affected by the
recent weakening of the SHA-1 hash?
I can see one exploit in which a different block is returned from a
compromised venti server, that I accept because the fingerprint matches
the requested fingerprint. The issue of turnaround time isn't really
there as files live on Venti for a long time, and a compromised server
could at its leisure find a collision for some block I'm submitting.
The likelihood of such an exploit seems small, but should we be looking
for a better Venti hash?
Paul
next prev parent reply other threads:[~2005-02-19 19:20 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-19 18:37 [9fans] Drawterm and security Brian L. Stuart
2005-02-19 18:48 ` andrey mirtchovski
2005-02-19 21:00 ` Brian L. Stuart
2005-02-19 18:58 ` Russ Cox
2005-02-19 19:15 ` blstuart
2005-02-19 19:20 ` Russ Cox
2005-02-19 20:24 ` blstuart
2005-02-19 20:34 ` andrey mirtchovski
2005-02-19 19:20 ` Paul Lalonde [this message]
2005-02-19 19:26 ` [9fans] Venti security in view of SHA-1 exploit andrey mirtchovski
2005-02-19 19:35 ` Paul Lalonde
2005-02-19 20:14 ` Tim Newsham
2005-02-20 4:24 ` Karl Magdsick
2005-02-19 20:15 ` Russ Cox
2005-02-19 22:25 ` boyd, rounin
2005-02-19 22:44 ` [9fans] Venti security in view of SHA-1 exploity William Josephson
2005-02-19 22:48 ` boyd, rounin
2005-02-20 18:08 ` William Josephson
2005-02-19 23:21 ` [9fans] Venti security in view of SHA-1 exploit Bruce Ellis
2005-02-20 1:00 ` Tim Newsham
2005-02-20 3:53 ` Karl Magdsick
2005-02-19 19:52 ` [9fans] Drawterm and security Skip Tavakkolian
2005-02-19 19:11 ` blstuart
2005-02-21 11:30 ` Robert Raschke
2005-02-21 19:20 ` geoff
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=9e8b82886fac51f78a70e17b6ba26813@telus.net \
--to=plalonde@telus.net \
--cc=9fans@cse.psu.edu \
/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).