9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Brian L. Stuart" <blstuart@bellsouth.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Drawterm and security
Date: Sat, 19 Feb 2005 15:00:46 -0600	[thread overview]
Message-ID: <20050219210107.DSND730.imf22aec.mail.bellsouth.net@p1.stuart.org> (raw)
In-Reply-To: Your message of Sat, 19 Feb 2005 11:48:00 -0700 . <0857c7e34289332af716f9b0ef5a55c2@plan9.ucalgary.ca>

Let's try this again.  It didn't seem to get out before.

In message <0857c7e34289332af716f9b0ef5a55c2@plan9.ucalgary.ca>, andrey mirtcho
vski writes:
>> Even a recipe would be welcome at this point.
>
>Ingredients:
>
>    * 1 part Vodka
>    * 1 part Tequila
>    * 1 part Rum
>    * 1 part Gin
>    * 1 part Triple sec
>    * 1 1/2 part Sour mix
>    * 1 splash Coca-Cola

Truely tempting.

Well, I was going to repeat all the stuff I had tried to send before,
but suddenly things are working for drawterm.  The last step was
to invalidate the nvram, reboot and reset all the passwords.  I'm
not sure how things got mangled, but drawterm is now working.
replica/pull still isn't however.  I definitely have the auth=sources
line in /lib/ndb/local now.  But even before factotum asks for
a user and password, I'm getting:

srv tcp!sources.cs.bell-labs.com: mount failed: authentication failed

I get the same thing if I manually try to 9fs soruces.  Any ideas on
that one?

Thanks to everyone for your help.  The really frustrating part of
all of the authentication stuff is that I don't seem to yet see
the connections between fault symptoms and causes.  I still don't
know why wiping the nvram and resetting everything has made drawterm
happy.

Brian L. Stuart


  reply	other threads:[~2005-02-19 21:00 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-19 18:37 Brian L. Stuart
2005-02-19 18:48 ` andrey mirtchovski
2005-02-19 21:00   ` Brian L. Stuart [this message]
2005-02-19 18:58 ` Russ Cox
2005-02-19 19:15   ` blstuart
2005-02-19 19:20     ` Russ Cox
2005-02-19 20:24       ` blstuart
2005-02-19 20:34         ` andrey mirtchovski
2005-02-19 19:20   ` [9fans] Venti security in view of SHA-1 exploit Paul Lalonde
2005-02-19 19:26     ` andrey mirtchovski
2005-02-19 19:35       ` Paul Lalonde
2005-02-19 20:14         ` Tim Newsham
2005-02-20  4:24           ` Karl Magdsick
2005-02-19 20:15     ` Russ Cox
2005-02-19 22:25       ` boyd, rounin
2005-02-19 22:44         ` [9fans] Venti security in view of SHA-1 exploity William Josephson
2005-02-19 22:48           ` boyd, rounin
2005-02-20 18:08             ` William Josephson
2005-02-19 23:21         ` [9fans] Venti security in view of SHA-1 exploit Bruce Ellis
2005-02-20  1:00           ` Tim Newsham
2005-02-20  3:53           ` Karl Magdsick
2005-02-19 19:52 ` [9fans] Drawterm and security Skip Tavakkolian
2005-02-19 19:11   ` blstuart
2005-02-21 11:30   ` Robert Raschke
2005-02-21 19:20     ` geoff
     [not found] <Pine.BSI.4.61.0502191055110.3971@malasada.lava.net>
2005-02-19 21:09 ` Brian L. Stuart
2005-02-19 22:42   ` Russ Cox
2005-02-19 23:37     ` Brian L. Stuart

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=20050219210107.DSND730.imf22aec.mail.bellsouth.net@p1.stuart.org \
    --to=blstuart@bellsouth.net \
    --cc=9fans@cse.psu.edu \
    /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).