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 08:34:38 -0600	[thread overview]
Message-ID: <14ec7b180707270734v316923c2h710fe98af498d149@mail.gmail.com> (raw)
In-Reply-To: <14ec7b180707270729l19362cf8pb30938e46019cf7b@mail.gmail.com>

sorry, i wasn't clear. factotum won't pick up the file from secstore
by itself because secstored isn't started by the time the hostowner's
factotum starts, so you'll have to do it by yourself. this is a
typical cpurc for a cpu server running ssh:

	auth/secstored
	auth/secstore -n -G factotum > /mnt/factotum/ctl

with the host key in the factotum file, of course.

andrey

On 7/27/07, andrey mirtchovski <mirtchovski@gmail.com> wrote:
> put it in the hostowner's secstore where factotum will pick it up
> every time the machine boots. let me know if you need an example.
>
> On 7/27/07, erik quanstrom <quanstro@coraid.com> wrote:
> > the sshserve(1) (sic.) man page mentions how to generate a host
> > key on-the-fly, but doesn't mention where to store the key.
> >
> > where is the recommend place to stash that key?
> >
> > - erik
> >
>


  reply	other threads:[~2007-07-27 14:34 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 [this message]
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
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=14ec7b180707270734v316923c2h710fe98af498d149@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).