9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@coraid.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] security model
Date: Thu,  1 Feb 2007 14:00:44 -0500	[thread overview]
Message-ID: <b6fc473d4db32518ee2c6fdd887fcbe4@coraid.com> (raw)
In-Reply-To: <4a591bc90702011033h5efeb78cs435843b913300a06@mail.gmail.com>

On Thu Feb  1 13:39:00 EST 2007, schors@gmail.com wrote:
> 2007/2/1, erik quanstrom <quanstro@coraid.com>:
> All has appeared simply. When I have read through precise answers, I
> have methodically looked all dependent files. /adm/keys* have
> permissions owned by user admin (installation process?). I removes and
> recreates that files as I find at file-server instruction.

these files need to be owned by the hostowner of the auth server.

> 
> All works right now.  And I at last have understood as it works.
> 

great.


> All equally has not understood. Whether it is possible to describe
> more in detail these two passwords (secstore key and password) and
> their value? Who for whom and when follows in the subsequent
> situations.

this confuses me a bit, too.  the key is the user name and the key
is the password.  the reason for this is secstore is written in very general 
terms.  in practice, the keys are generally user names.

- erik

> 
> -- 
> Да будет осиян звездой момент нашей переписки!
> Phil Kulin



  reply	other threads:[~2007-02-01 19:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <0c5a6d53f01894258fb37e168ee08628@coraid.com>
2007-02-01 18:33 ` Phil Kulin
2007-02-01 19:00   ` erik quanstrom [this message]
2007-02-01 15:31 erik quanstrom
  -- strict thread matches above, loose matches on Subject: below --
2007-02-01 10:44 Phil Kulin
2007-02-01 13:52 ` erik quanstrom
2007-02-01 22:35   ` Georg Lehner
2007-02-01 22:57     ` C H Forsyth
2007-02-01 22:58     ` Steve Simon
2007-02-01 23:30       ` C H Forsyth
2007-02-01 15:44 ` C H Forsyth
2007-02-01 15:54 ` Alberto Cortés

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=b6fc473d4db32518ee2c6fdd887fcbe4@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).