From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Thu, 18 Jan 2007 19:11:43 +0100
From: Alberto =?iso-8859-1?Q?Cort=E9s?= <alcortes@it.uc3m.es>
To: 9fans <9fans@cse.psu.edu>
Message-ID: <20070118181143.GA9084@it.uc3m.es>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
User-Agent: Mutt/1.5.9i
Subject: [9fans] Is the "cpu" command using version 1 of p9any?
Content-Transfer-Encoding: quoted-printable
Topicbox-Message-UUID: 05b83ac8-ead2-11e9-9d60-3106f5b1d025


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=3Dp9any role=3Dclient".

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%

--=20
Alberto Cort=E9s