From: "Özgür Kesim" <oec-9front@kesim.org>
To: 9front@9front.org
Subject: [9front] Problem with authentication on file server
Date: Sun, 10 Nov 2024 14:37:44 +0100 [thread overview]
Message-ID: <z4tnp5k6zxtcln2pwhrubrfz4ukh5ofgspcackc44egm5msuqd@4mm3yoihlfgm> (raw)
Hi,
I have a 9front file+cpu+auth server on my desk that I occasionally use
for some experiments. About a week ago I did a sysupdate on the machine
and some changes to ndb/local (IIRC, only adding an authdom to the
ipnet). Now connection to it via drawterm (the 9front version) fails,
with the following complaint:
drawterm: can't authenticate: auth_proxy rpc: p9any client ask for keys: unable to find common key
Altering ndb/local didn't help. Before I dig deeper and try to extract
more information from the cpu server -- does anybody have an idea and a
hint where I should look?
Cheers,
oec
next reply other threads:[~2024-11-10 13:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-10 13:37 Özgür Kesim [this message]
2024-11-10 13:56 ` theinicke
2024-11-10 17:08 ` Özgür Kesim
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=z4tnp5k6zxtcln2pwhrubrfz4ukh5ofgspcackc44egm5msuqd@4mm3yoihlfgm \
--to=oec-9front@kesim.org \
--cc=9front@9front.org \
/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).