From: Russ Cox <russcox@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Venti security in view of SHA-1 exploit
Date: Sat, 19 Feb 2005 15:15:38 -0500 [thread overview]
Message-ID: <ee9e417a05021912153b6c45ee@mail.gmail.com> (raw)
In-Reply-To: <9e8b82886fac51f78a70e17b6ba26813@telus.net>
Conversion is made quite easy (compared to other systems
I am familar with) because the blocks are tagged with their type
(data, SHA1 hashes of data, SHA1 hashes of hashes of data)
and the block tree is a standardized format used by all clients,
so conversion can happen independent of the program that wrote
the data. After converting the data, all the clients and the server
would have to be rebuilt with the new hash function.
It is not necessary to write a separate program to convert fossil
data, vac data, etc.
Some day it will be necessary to worry about this. It is not today.
Russ
next prev parent reply other threads:[~2005-02-19 20:15 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 ` [9fans] Venti security in view of SHA-1 exploit Paul Lalonde
2005-02-19 19:26 ` 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 [this message]
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=ee9e417a05021912153b6c45ee@mail.gmail.com \
--to=russcox@gmail.com \
--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).