From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Tue, 1 May 2007 14:56:58 +0200 From: Christian Kellermann To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu> Message-ID: <20070501125658.GK2624@hermes.my.domain> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="va4/JQ6j8/8uipEp" Content-Disposition: inline User-Agent: Mutt/1.5.12-2006-07-14 Subject: [9fans] keyfs warnings Topicbox-Message-UUID: 546c2a12-ead2-11e9-9d60-3106f5b1d025 --va4/JQ6j8/8uipEp Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Dear list, I have done some more reading through documentations after my last post to this list about the strange loss if user login data on my auth server. I am now able to pin down the problem to keyfs. I have started over by - overwriting my nvram with bla - truncating the /adm/keys file with echo '' > /adm/keys - rebooting, filling in password and secstore phrase - killing keyfs - starting auth/keyfs on the server console - creating new keys with auth/changeuser for bootes and another user - rebooting After that I am able to log in as bootes but not the other user (the user is present on the fossil filesystem) When I now kill/restart keyfs on the server keyfs prints the following warnings: % auth/keyfs keyfs: warning: bad status in key file keyfs: warning: bad status in key file keyfs: warning: bad status in key file 4 keys read 1. Shouldn't there be only 2 keys as I have added 2 users? 2. When trying to auth/debug the user login still fails 3. lc /mnt/keys displays garbage Any hints? Yours, Christian --=20 You may use my gpg key for replies: pub 1024D/47F79788 2005/02/02 Christian Kellermann (C-Keen) --va4/JQ6j8/8uipEp Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (OpenBSD) iD8DBQFGNzkaXYob3Uf3l4gRAvbaAKCLa/zrQhCPWk2O69L6VYXs53Sy4ACggvSl wiGWDkuN55YmeRxewEZ/UpA= =i49r -----END PGP SIGNATURE----- --va4/JQ6j8/8uipEp--