From: erik quanstrom <quanstro@coraid.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] ssh host key
Date: Fri, 27 Jul 2007 12:57:55 -0400 [thread overview]
Message-ID: <20b8249a95a46ec94a1aed95aeb1f766@coraid.com> (raw)
In-Reply-To: <8ccc8ba40707270940m707b70e5w4f976fbe9b10cce7@mail.gmail.com>
> I don't know about len limits, but mine has really weird characters and
> works fine in nvram. This may seem silly, but, have you checked out that
> your password is nvram is indeed ok? [that was a mistake I made]
> You could try after rewriting it.
well, the password does authenticate with the fs and
i did use auth/wrkey to rewrite it, just in case.
- erik
next prev parent reply other threads:[~2007-07-27 16:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-27 13:07 erik quanstrom
2007-07-27 14:29 ` andrey mirtchovski
2007-07-27 14:34 ` andrey mirtchovski
2007-07-27 15:41 ` erik quanstrom
2007-07-27 16:27 ` erik quanstrom
2007-07-27 16:33 ` Francisco J Ballesteros
2007-07-27 16:37 ` andrey mirtchovski
2007-07-27 16:40 ` Francisco J Ballesteros
2007-07-27 16:57 ` erik quanstrom [this message]
2007-07-27 17:03 ` Francisco J Ballesteros
2007-07-27 17:22 ` erik quanstrom
2007-07-27 17:08 ` geoff
2007-07-27 17:21 ` erik quanstrom
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=20b8249a95a46ec94a1aed95aeb1f766@coraid.com \
--to=quanstro@coraid.com \
--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).