From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <b6fc473d4db32518ee2c6fdd887fcbe4@coraid.com>
From: erik quanstrom <quanstro@coraid.com>
Date: Thu,  1 Feb 2007 14:00:44 -0500
To: 9fans@cse.psu.edu
Subject: Re: [9fans] security model
In-Reply-To: <4a591bc90702011033h5efeb78cs435843b913300a06@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Topicbox-Message-UUID: 0b816ccc-ead2-11e9-9d60-3106f5b1d025

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.

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

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 gene=
ral=20
terms.  in practice, the keys are generally user names.

- erik

>=20
> --=20
> =D0=94=D0=B0 =D0=B1=D1=83=D0=B4=D0=B5=D1=82 =D0=BE=D1=81=D0=B8=D1=8F=D0=
=BD =D0=B7=D0=B2=D0=B5=D0=B7=D0=B4=D0=BE=D0=B9 =D0=BC=D0=BE=D0=BC=D0=B5=D0=
=BD=D1=82 =D0=BD=D0=B0=D1=88=D0=B5=D0=B9 =D0=BF=D0=B5=D1=80=D0=B5=D0=BF=D0=
=B8=D1=81=D0=BA=D0=B8!
> Phil Kulin