From: rog@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] fossil/flfmt -v problem
Date: Fri, 4 Jul 2003 18:21:44 +0100 [thread overview]
Message-ID: <63090fce9e1be3b8bc05488eefe1e15f@vitanuova.com> (raw)
In-Reply-To: <cc60cbcd83a8e73e318697e8eb2707db@plan9.bell-labs.com>
> a console with real paper in it makes an excellent log.
but... watch out, as a venti score is a dangerous thing.
given a venti archive score and access to a venti server, you've got
access to all data in the filesystem, regardless of permissions or
ownership.
i wonder whether it might be sensible to print venti scores blinded
with some private key, or something along that sort of line?
next prev parent reply other threads:[~2003-07-04 17:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-03 22:50 andrey mirtchovski
2003-07-04 3:23 ` jmk
2003-07-04 3:35 ` andrey mirtchovski
2003-07-04 3:57 ` jmk
2003-07-04 4:37 ` andrey mirtchovski
2003-07-04 13:37 ` Fco.J.Ballesteros, nemo
2003-07-04 13:51 ` andrey mirtchovski
2003-07-04 16:42 ` jmk
2003-07-04 17:17 ` Fco.J.Ballesteros, nemo
2003-07-04 17:21 ` rog [this message]
2003-07-04 17:20 ` Fco.J.Ballesteros, nemo
2003-07-04 17:25 ` Fco.J.Ballesteros, nemo
2003-07-04 17:46 ` rog
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=63090fce9e1be3b8bc05488eefe1e15f@vitanuova.com \
--to=rog@vitanuova.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).