From: "Alberto Cortés" <alcortes@it.uc3m.es>
To: 9fans <9fans@cse.psu.edu>
Subject: [9fans] Is the "cpu" command using version 1 of p9any?
Date: Thu, 18 Jan 2007 19:11:43 +0100 [thread overview]
Message-ID: <20070118181143.GA9084@it.uc3m.es> (raw)
Authsrv(6) sais cpu(1) uses "p9any" and also sais that "p9any
version 1" is no longer used.
I had snooped on a cpu connection, here is the payload of the
first 4 (data) tcp packets:
(1) C->S p9 rc4_256 sha1
(2) S->C (null char here)
(3) S->C p9sk1@my.auth.domain
(4) C->S p9sk1 my.auth.domain
(1) and (2) are part of an specific negotiation of cpu clients
and servers.
(3) and (4) look like a "p9any version 1" negotiation. I presume
these packets are due to /sys/src/cmd/cpu.c:524, a call to
auth_proxy(2).
I believe the above samples comes from calling auth_proxy with
"proto=p9any role=client".
Maybe cpu is using "p9any version 1" or there is an errata in
authsrv(6).
PS: The samples are from a tcp connection to 17010 port; on my server:
cpu% cat /rc/bin/serice/tcp17010
#!/bin/cpu -R
cpu%
--
Alberto Cortés
next reply other threads:[~2007-01-18 18:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-18 18:11 Alberto Cortés [this message]
2007-01-18 18:27 ` Alberto Cortés
2007-01-18 18:50 ` 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=20070118181143.GA9084@it.uc3m.es \
--to=alcortes@it.uc3m.es \
--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).