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 07:18:34 -0500 [thread overview]
Message-ID: <ee9e417a0701160418vc62148em72e4369b882ad8f8@mail.gmail.com> (raw)
In-Reply-To: <20070116115900.GA16784@it.uc3m.es>
> Trying to understand how authentication works, I ended up using
> snoopy on a cpu connection, something like:
>
> % snoopy -f 'tcp(sd=17010)'
>
> and, on another window:
>
> % cpu
>
>
> This will give you lots of lines that looks like:
>
> ninep(68656c6c6f203966616e7321)
Cpu *does* talk 9P, but it is usually encrypted 9P, and the
chance of 9P encrypting to an ASCII string is pretty low.
If you ran cpu -e none (not an option unless you compile
your own special copy of cpu) you would be able to see
the raw 9P traffic.
> I believe it should say something like:
>
> unknown(68656c6c6f203966616e7321)
>
> or
>
> unknown"helo 9fans"
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.
Russ
next prev parent reply other threads:[~2007-01-16 12:18 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 [this message]
2007-01-16 13:08 ` Alberto Cortés
2007-01-16 13:42 ` Russ Cox
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=ee9e417a0701160418vc62148em72e4369b882ad8f8@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).