From: Thomas Riemer triemer@babbitt.bernstein.com
Subject: Continuing on CPU/Auth
Date: Sun, 7 Apr 1996 14:32:14 -0400 [thread overview]
Message-ID: <19960407183214.vAviIR72T-iUdmSdaFq-xJilWczour9Bo74CSYxg34I@z> (raw)
Curiouser and Curiouser...
The reason findkey in /sys/cmd/auth/lib/readwrite.c is failing is because
it can't find the file /mnt/keys/triemer/key.
It is calling open on /mnt/keys/triemer/key - and failing to find
the file.
This is extremely odd since a standard ls on /mnt/keys/triemer/key says
that it exists. This should be served by keyfs - if I'm correct.
keyfs is started in /bin/cpurc - it prints out that it has read 3 keys
when it starts.
Let me point out that as user bootes (the authid), I see
/mnt/keys/triemer/key - however as user none, I do not. It makes sense
that I should be able to see the keys as user none - I just don't know if
this is the way its "supposed" to be.
As bootes, I can "cat" the file - it has 7 characters in it.
Let me point out that I see the same behavior under the 9pccpudisk
that came on the CD - as well as the 9pccpudisk that I built yesterday with
all the patches to /sys/src/9 (boot, pc, port) applied.
Of course, all of this logic is so simple to explain... I was running
/bin/auth/auth.srv as user none - not as user bootes, because I was
foolish enough to put il566 in /bin/services instead of
/bin/service.auth/services. Right about now, I feel like I have a few
bullet holes in my boots. BTW - the authentication seems to work quite
nicely once I changed this.
-Tom
---- Where theory and reality meet.
---- Thomas Riemer, tom@rockvax.rockefeller.edu
reply other threads:[~1996-04-07 18:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=19960407183214.vAviIR72T-iUdmSdaFq-xJilWczour9Bo74CSYxg34I@z \
--to=9fans@9fans.net \
/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).