From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <40E8D3CE.6000802@place.org> Date: Sun, 4 Jul 2004 21:06:38 -0700 From: Stephen Wynne User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040616 MIME-Version: 1.0 To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu> Subject: Re: [9fans] References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Topicbox-Message-UUID: b49891fa-eacd-11e9-9e20-41e7f4b1d025 andrey mirtchovski wrote: > you won't need a secstore for your installation to work. OK, I guess I don't need it for connecting with drawterm, either. But apparently I need it for SSH and pulling updates. I may also need it for other stuff. I'm running an app that makes a call to auth_getuserpasswd() and it fails now that I've tried to setup securestore; it used to get past that point before. > check the /sys/doc/auth.ps paper (also on Bell-Labs' > site) secstore/factotum pair Well, . Here's where I am now: On my terminal via a drawterm connection (I haven't recompiled for more GUI support yet), I'm following http://pages.cpsc.ucalgary.ca/~mirtchov/lanlp9/tips.html on setting up secstore. The mkdirs were done before. One small issue, factotum wanted /adm/secstore/store/bootes/factotum/ (I think it was). > on auth server: > > auth/secstored > mkdir /adm/secstore > mkdir /adm/secstore/store > mkdir /adm/secstore/who > auth/secuser dpx > > on terminal: > > touch /tmp/factotum > auth/secstore -p /tmp/factotum > ramfs -p; cd /tmp > auth/secstore -g factotum > secstore password: > echo 'key proto=apop dom=x.com user=dpx \ > !password=y~1' >> factotum > auth/secstore -p factotum > secstore password: > cat factotum > /mnt/factotum/ctl This is where I'm still stuck. > you'll need to have both auth/secstored and > auth/factotum started. I do, but there must be something else wrong. I found one thing: my lib/ndb/local file still had localhost and 127.0.0.1 as the sys'name from my initial fumbling around to get it online. Now I get to the ramfs stage! However, secstore -g complains about /tmp/factotum not existing. If I skip the ramfs step, I see this: cpu% auth/secstore -g factotum secstore password: secstore implausible filesize for factotum secstore cmd failed On the console of the PC, I see "implausible filesize -1 for factotum," but no information about which file is too small. This is what I have in /mnt/factotum: cpu% pwd /mnt/factotum cpu% cat ctl key proto=p9sk1 user=bootes dom=9net !hex? !password? cpu% ls -l -lrw------- M 48 bootes bootes 0 Jul 4 23:46 confirm --rw-r--r-- M 48 bootes bootes 0 Jul 4 23:46 ctl -lr-------- M 48 bootes bootes 0 Jul 4 23:46 log -lrw------- M 48 bootes bootes 0 Jul 4 23:46 needkey --r--r--r-- M 48 bootes bootes 0 Jul 4 23:46 proto --rw-rw-rw- M 48 bootes bootes 0 Jul 4 23:46 rpc > it's like riding a bycicle -- once you do it you'll > always know how it's done :) I'm still trying to bolt on my training wheels, I think. But thanks for your patience!