From: "roger peppe" <rogpeppe@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] Factotum
Date: Tue, 6 May 2008 10:51:51 +0100 [thread overview]
Message-ID: <df49a7370805060251o410fa372o292f464e3bea9ffc@mail.gmail.com> (raw)
In-Reply-To: <47678717a143d31883deb21d731c8a7d@quanstro.net>
On Sun, May 4, 2008 at 2:57 AM, erik quanstrom <quanstro@quanstro.net> wrote:
> it is not factotum's job to provide persistant storage. that would
> infringe upon secstore's franchise.
that said, i sometimes wish the interface between factotum and secstore
was a bit more slick, particularly when dealing with protocols (such as
inferno's auth(6)) that don't use a password directly, but instead use another
protocol (e.g. login(6)) to generate a long-term key which is the info that you
want factotum to store.
the stuff with ipso, etc, is fine when all the entries are manually generated,
but seems unnecessarily awkward when automatically generated keys are
involved.
i'd like to see a way of asking factotum "please save your keys to secstore",
although there's some difficulty getting it right, as there are
potentially many factotums
to one secstore, or even worse, several secstores.
next prev parent reply other threads:[~2008-05-06 9:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-03 18:57 Rodolfo kix Garcia
2008-05-03 22:54 ` erik quanstrom
2008-05-03 23:01 ` Pietro Gagliardi
2008-05-04 1:37 ` Russ Cox
2008-05-04 1:45 ` Pietro Gagliardi
2008-05-04 1:57 ` erik quanstrom
2008-05-04 5:39 ` Bruce Ellis
2008-05-06 9:51 ` roger peppe [this message]
2008-05-06 13:57 ` Eric Van Hensbergen
2008-05-06 14:08 ` erik quanstrom
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=df49a7370805060251o410fa372o292f464e3bea9ffc@mail.gmail.com \
--to=rogpeppe@gmail.com \
--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).