From: C H Forsyth <forsyth@vitanuova.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] security model
Date: Thu, 1 Feb 2007 22:57:12 +0000 [thread overview]
Message-ID: <70c348c9a9f24a2bb44903f886defd64@vitanuova.com> (raw)
In-Reply-To: <878xfh4ibl.fsf@jorgito.magma.intern>
[-- Attachment #1: Type: text/plain, Size: 117 bytes --]
it times out, reasonably quickly on the systems i've used.
it then falls back to talking directly to an auth server.
[-- Attachment #2: Type: message/rfc822, Size: 3278 bytes --]
From: Georg Lehner <jorge-plan9@magma.com.ni>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] security model
Date: Thu, 01 Feb 2007 23:35:42 +0100
Message-ID: <878xfh4ibl.fsf@jorgito.magma.intern>
erik quanstrom <quanstro@coraid.com> writes:
> i'll take a stab at this.
>
> On Thu Feb 1 08:34:58 EST 2007, schors@gmail.com wrote:
...
>> First I don't undestand why I must run auth/secstored on my auth
>> server.
>
> it is not required. secstore provides secure storage for users. also you
> don't need to run secstore on the auth server, but for most people
> that's where it makes sense.
...
drawterm (on linux, at least) always tries to contact secstore on the
authserver during startup. So it may not be *required* to run
secstore there, but I guess doing otherwise is not feasible.
Regards,
Jorge-León
next prev parent reply other threads:[~2007-02-01 22:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
2007-02-01 15:31 erik quanstrom
[not found] <0c5a6d53f01894258fb37e168ee08628@coraid.com>
2007-02-01 18:33 ` Phil Kulin
2007-02-01 19:00 ` 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=70c348c9a9f24a2bb44903f886defd64@vitanuova.com \
--to=forsyth@vitanuova.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).