9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu, Russ Cox <rsc@swtch.com>
Subject: Re: [9fans] 9fs sources
Date: Fri, 28 Oct 2005 15:07:07 -0500	[thread overview]
Message-ID: <20051028200707.640D210F54@dexter-peak.quanstro.net> (raw)
In-Reply-To: <20051028194707.BBEB210F54@dexter-peak.quanstro.net>

asked and answered i guess... spaces are encoded as + when the web browser
submits them from http://plan9.bell-labs.com/plan9dist/newaccount.html
maybe the password should be run de-urlencoded? 

erik

quanstro@quanstro.net (erik quanstrom) writes

| 
| ya, been there, done that:
| 
| ; 9p read factotum/ctl 
| key dom=outside.plan9.bell-labs.com proto=p9sk1 role=client user=quanstro !password?
| 
| but since i cut-and-paste the password, i'm pretty sure that it's correct. is space an
| legit password character?
| 
| erik
| 
| Russ Cox <rsc@swtch.com> writes
| 
| | 
| | 9p read factotum/ctl might tell you something
| | interesting.
| | 
| | On 10/28/05, erik quanstrom <quanstro@quanstro.net> wrote:
| | > i'm sure this is a stupid question, but ...
| | >
| | > does an update account give access to "9fs sources"?
| | > on p9p i get into this loop:
| | >
| | > ; 9fs sources
| | >
| | > !adding key: proto=p9sk1 role=client dom=outside.plan9.bell-labs.com user=quanstro
| | > password:
| | > !
| | >
| | > !adding key: proto=p9sk1 role=client dom=outside.plan9.bell-labs.com user=quanstro
| | > password:
| | >
| | > [ad infinitum]
| | >


  reply	other threads:[~2005-10-28 20:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-28 19:05 erik quanstrom
2005-10-28 19:17 ` Federico G. Benavento
2005-10-28 19:46 ` Russ Cox
2005-10-28 19:47   ` erik quanstrom
2005-10-28 20:07     ` erik quanstrom [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-07-25 11:04 boyd, rounin

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=20051028200707.640D210F54@dexter-peak.quanstro.net \
    --to=quanstro@quanstro.net \
    --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).