9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Russ Cox" <rsc@swtch.com>
To: "Alberto Cortés" <alcortes@it.uc3m.es>,
	"Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] snoopy thinks that the cpu command talks 9p
Date: Tue, 16 Jan 2007 08:42:06 -0500	[thread overview]
Message-ID: <ee9e417a0701160542l13eb0347mef461d1e07229b57@mail.gmail.com> (raw)
In-Reply-To: <20070116130839.GA20455@it.uc3m.es>

> > There's not really any good option here, since the interesting
> > bits are encrypted, and saying ninep is not a lie, so I'm
> > inclined just to leave it alone.  There's certainly no point in
> > printing unknown("hello 9fans!"), since as I mentioned above,
> > it's either 9P or encrypted 9P, never plain text.
>
> It certainly have plain text on the first packet:
>
>     p9 rc4_256 sha1
>
> I am not sure if this is 9P.

No, it's not.  There is a negotiation that happens first, specific to cpu,
and then there is a generic factotum authentication protocol that happens
afterward (if p9 is what is chosen by the cpu negotiation),
and then the bulk of the connection is in fact encrypted 9P.
Printing the hex is still the best choice: only the first little bit has
text, and even that has some NULs and the like for framing.
The auth protocol has some text strings embedded but it's mostly
binary.

Russ


  reply	other threads:[~2007-01-16 13:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-16 11:59 Alberto Cortés
2007-01-16 12:18 ` Russ Cox
2007-01-16 13:08   ` Alberto Cortés
2007-01-16 13:42     ` Russ Cox [this message]
2007-01-16 14:05       ` Alberto Cortés

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=ee9e417a0701160542l13eb0347mef461d1e07229b57@mail.gmail.com \
    --to=rsc@swtch.com \
    --cc=9fans@cse.psu.edu \
    --cc=alcortes@it.uc3m.es \
    /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).