From: Christian Kellermann <Christian.Kellermann@nefkom.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: [9fans] keyfs warnings
Date: Tue, 1 May 2007 14:56:58 +0200 [thread overview]
Message-ID: <20070501125658.GK2624@hermes.my.domain> (raw)
[-- Attachment #1: Type: text/plain, Size: 1173 bytes --]
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
--
You may use my gpg key for replies:
pub 1024D/47F79788 2005/02/02 Christian Kellermann (C-Keen)
[-- Attachment #2: Type: application/pgp-signature, Size: 194 bytes --]
next reply other threads:[~2007-05-01 12:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-01 12:56 Christian Kellermann [this message]
2007-05-01 13:13 ` erik quanstrom
2007-05-01 15:17 ` Christian Kellermann
2007-05-01 15:19 ` C H Forsyth
2007-05-01 15:39 ` Christian Kellermann
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=20070501125658.GK2624@hermes.my.domain \
--to=christian.kellermann@nefkom.net \
--cc=9fans@cse.psu.edu \
/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).