From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <8ccc8ba40707270933t32e0ec8pa675c354a1c1fc70@mail.gmail.com>
Date: Fri, 27 Jul 2007 18:33:14 +0200
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
In-Reply-To: <fc984be2075394ad7be5bb350a3785d2@coraid.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <14ec7b180707270734v316923c2h710fe98af498d149@mail.gmail.com>
	<fc984be2075394ad7be5bb350a3785d2@coraid.com>
Topicbox-Message-UUID: 97d8e20e-ead2-11e9-9d60-3106f5b1d025

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
>