9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Francisco J Ballesteros" <nemo@lsub.org>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] ssh host key
Date: Fri, 27 Jul 2007 18:33:14 +0200	[thread overview]
Message-ID: <8ccc8ba40707270933t32e0ec8pa675c354a1c1fc70@mail.gmail.com> (raw)
In-Reply-To: <fc984be2075394ad7be5bb350a3785d2@coraid.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.

On 7/27/07, erik quanstrom <quanstro@coraid.com> wrote:
> i get this error
>
>         ladd# auth/secstore -nG factotum
>         ladd# echo $status
>         secstore 1517: invalid password in nvram
>
> however if i do it this way, it works:
>
>         ladd# auth/secstore -G factotum
>         secstore password: <same password entered>
>         secstore
>         <keys printed here>
>
> i have a longish password, but it doesn't exceed ANAMELEN.
> does nvram truncate the password?  are there any magic characters
> which must be avoided?
>
> - erik
>


  reply	other threads:[~2007-07-27 16:33 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 [this message]
2007-07-27 16:37       ` andrey mirtchovski
2007-07-27 16:40         ` Francisco J Ballesteros
2007-07-27 16:57           ` erik quanstrom
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=8ccc8ba40707270933t32e0ec8pa675c354a1c1fc70@mail.gmail.com \
    --to=nemo@lsub.org \
    --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).