From: Uriel <uriell@binarydream.org>
To: 9fans <9fans@cse.psu.edu>
Subject: [9fans] p9sk2
Date: Tue, 4 Oct 2005 22:04:25 +0100 [thread overview]
Message-ID: <20051004210425.GC19776@server4.lensbuddy.com> (raw)
I was trying to document -O in cpu(1) which is undocumented, it enables
'p9sk2', but what that does is rather confusing, my initial guess was that it
was a deprecated version of p9sk1, but lookman p9sk2 pointed me at
factotum(4) which says:
p9sk1 a Plan 9 shared key protocol described in
authsrv(6)'s ``File Service'' section.
p9sk2 a variant of p9sk1 described in authsrv(6)'s
``Remote Execution'' section.
(Oh, and it seems that factotum(4) in p9p and in Plan 9 are out of sync..
*sigh*)
Looking at authsrv(6) leaves me even more confused.
But auth/factotum/p9sk1.c seems to confirm the original theory:
% grep p9sk2 /sys/src/cmd/auth/factotum/p9sk1.c|sed 1q
* p9sk1, p9sk2 - Plan 9 secret (private) key authentication.
This all started because cpu -O is used in
http://plan9.bell-labs.com/wiki/plan9/Drawterm_to_your_terminal/
My guess is that it's needed for drawterm to be able to connect, will dt2k
fix that? what is up with dt2k anyway?
uriel
next reply other threads:[~2005-10-04 21:04 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-04 21:04 Uriel [this message]
2005-10-04 21:16 ` Axel Belinfante
2005-10-04 21:30 ` Axel Belinfante
2005-10-04 21:38 ` Uriel
2005-10-04 21:48 ` Skip Tavakkolian
2005-10-04 21:44 ` Russ Cox
2005-10-04 21:52 ` andrey mirtchovski
2005-10-04 22:05 ` geoff
2005-10-04 22:28 ` andrey mirtchovski
2005-10-04 22:38 ` Skip Tavakkolian
2005-10-04 22:41 ` Russ Cox
2005-10-04 22:42 ` andrey mirtchovski
2005-10-04 22:10 ` Uriel
2005-10-04 23:21 ` Skip Tavakkolian
2005-10-04 23:26 ` Russ Cox
2005-10-04 23:35 ` Russ Cox
2005-10-05 0:11 ` Uriel
2005-10-05 0:19 ` Russ Cox
2005-10-05 0:22 ` Skip Tavakkolian
2005-10-05 1:27 ` Uriel
2005-10-05 1:50 ` Russ Cox
2005-10-05 2:13 ` jmk
2005-10-05 4:56 ` LiteStar numnums
2005-10-24 13:52 ` Uriel
2005-10-24 14:17 ` jmk
[not found] ` <000001c5c94e$82d49890$14aaa8c0@utelsystems.local>
2005-10-05 5:36 ` Nils O. Selåsdal
2005-10-04 23:36 ` David Leimbach
2005-10-05 7:20 ` Richard Miller
2005-10-05 7:44 ` Skip Tavakkolian
[not found] ` <67a09890a59797f569b0456bb3edcc86@hamnavoe.com>
2005-10-05 10:46 ` Russ Cox
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=20051004210425.GC19776@server4.lensbuddy.com \
--to=uriell@binarydream.org \
--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).