9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "andrey mirtchovski" <mirtchovski@gmail.com>
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 10:37:17 -0600	[thread overview]
Message-ID: <14ec7b180707270937s2a97abe3l22d38d2e3f5af84f@mail.gmail.com> (raw)
In-Reply-To: <fc984be2075394ad7be5bb350a3785d2@coraid.com>

invalidate the nvram first and make sure you set the secstore password
correctly to the one that you have set for hostowner's user in
secstored when it asks you on the next reboot. if you have done
already then simply cat the nvram partition: you should be able to see
it in full and in plain text and see if it's truncated.

if the system and secstore passwords are different for hostowner
perhaps there may be a bug in parsing the nvram. they are the same
around here so i've never tested that condition.

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
>


  parent reply	other threads:[~2007-07-27 16:37 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 [this message]
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=14ec7b180707270937s2a97abe3l22d38d2e3f5af84f@mail.gmail.com \
    --to=mirtchovski@gmail.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).