From: "Alberto Cortés" <alcortes@it.uc3m.es>
To: Russ Cox <rsc@swtch.com>
Cc: 9fans <9fans@cse.psu.edu>
Subject: Re: [9fans] snoopy thinks that the cpu command talks 9p
Date: Tue, 16 Jan 2007 15:05:55 +0100 [thread overview]
Message-ID: <20070116140555.GA12047@it.uc3m.es> (raw)
In-Reply-To: <ee9e417a0701160542l13eb0347mef461d1e07229b57@mail.gmail.com>
Russ Cox said:
> 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
Thanks you very much for the explanation, some things are much
more clear now.
Those few runes-as-hex sound reasonable, now that I understand a
little bit of the big picture.
--
Alberto Cortés
prev parent reply other threads:[~2007-01-16 14:05 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
2007-01-16 14:05 ` Alberto Cortés [this message]
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=20070116140555.GA12047@it.uc3m.es \
--to=alcortes@it.uc3m.es \
--cc=9fans@cse.psu.edu \
--cc=rsc@swtch.com \
/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).