From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <1f816f8e7d96036f176dec16250e8b63@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] factotum-secstore
From: Eric Grosse <ehg@research.bell-labs.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Date: Mon, 23 Sep 2002 22:32:39 -0400
Topicbox-Message-UUID: f401b112-eaca-11e9-9e20-41e7f4b1d025

The correct sequence is:

ramfs -p; cd /tmp
ed factotum
   ...
auth/secstore -s tcp!plan9!5356 -p factotum -u william
mv factotum factotum.original
auth/secstore -s tcp!plan9!5356 -g factotum -u william


It is possible to have a subdirectory /adm/secstore/store/william/tmp/
and that might be useful in some special circumstances, but start with
just a flat layout.  Secstore is intended to bootstrap security,
not to be a general purpose file system.

The daemon secstored writes verbose error messages to stderr;  those
should probably go to /sys/log/auth instead and would have given you
a better clue to what was wrong.  I'll fix the source.

Eric