Re: [9fans] factotum nits

[r@google.com]

[-- Attachment #1: Type: text/plain, Size: 377 bytes --]

ipso was written in part to deal with this issue.  i know it's not quite
the same thing as what you're saying, but i use it exclusively to deal
with keys now. if i need to add a key, i put it in with ipso whenever
fgui yells at me.  Although you have to do it twice, the fgui display
shows you all the info you need to put in the key line when editing
with ipso.

-rob

[-- Attachment #2: Type: message/rfc822, Size: 2050 bytes --]

From: rog@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] factotum nits
Date: Mon, 11 Nov 2002 18:16:45 0000
Message-ID: <95f3ebae36d626c660bd745e0a1929c0@vitanuova.com>

> If you have other nits, say something.

i wondered if it could be useful to have factotum know about writing
to the secstore, so once you've entered a load of keys (with auth/fgui
or whatever) you could ask factotum to write them to the secstore from
which it obtained them, thus obviating the need to remember and
re-enter them (in the open, with an acme that might swap them out) at
a later date.

of course, you'd have to remember to sync that instance of secstore
with any other copies you're maintaining, but you do anyway.

maybe it's too dodgy to have factotum retain the secstore key?