9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Charles Forsyth <forsyth@terzarima.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] plain passwords and keyfs
Date: Sat, 24 Jul 2004 09:45:11 +0100	[thread overview]
Message-ID: <e21633a34edc5534aae622ce1dcf6e2b@terzarima.net> (raw)
In-Reply-To: <4AC740C7-DCD0-11D8-89AF-0003931DE5D4@lsub.org>

[-- Attachment #1: Type: text/plain, Size: 670 bytes --]

if you don't set a pop3 password in keyfs there won't be one in the clear (in `secret').
plan 9 itself doesn't need that password except to support pop3 clients
(and similar).  if you don't use pop3 you don't need it.
the administrator of the auth server can still shuffle the contents of the plan 9 `key'
files to masquerade for instance but cannot see the original plain text key.
thus your secret is safe unless it's in `secret',
because `key' doesn't contain the original key.

in any case, the casual snooping possible with Unix/Linux's `root' is a little
more tedious to do on Plan 9, and immutable logs in changeuser/keyfs
might discourage it further.

[-- Attachment #2: Type: message/rfc822, Size: 2899 bytes --]

From: Enrique Soriano <esoriano@lsub.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] plain passwords and keyfs
Date: Fri, 23 Jul 2004 19:46:57 +0200
Message-ID: <4AC740C7-DCD0-11D8-89AF-0003931DE5D4@lsub.org>


El 23/07/2004, a las 18:10, Charles Forsyth escribió:

> the Plan 9 password is scrambled, into key not secret.
> secret is used for access to other systems.
> i don't think you must set it.

I used auth/changeuser to add the users (I didn't use directly the
keyfs filesystem).

> it is in plain text because it's hard to say which
> particular scrambling algorithm, if any,
> will be used to talk to those other systems.

Thanks.

Q.

  reply	other threads:[~2004-07-24  8:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5d791b8fa2a574fb6cc322e97696054c@terzarima.net>
2004-07-23 17:46 ` Enrique Soriano
2004-07-24  8:45   ` Charles Forsyth [this message]
2004-07-24 13:48     ` Steve Simon
2004-07-25 19:19       ` Charles Forsyth
2004-07-25 20:00         ` Steve Simon
2004-07-23 13:14 Enrique Soriano Salvador
2004-07-23 16:10 ` Charles Forsyth
2004-07-23 16:34   ` Wes Kussmaul
2004-07-23 16:47     ` andrey mirtchovski
2004-07-23 17:38       ` Wes Kussmaul
2004-07-23 17:06     ` Skip Tavakkolian
2004-07-24  7:32       ` Sam
2004-07-23 17:29         ` andrey mirtchovski
2004-07-23 23:24         ` Bruce Ellis

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=e21633a34edc5534aae622ce1dcf6e2b@terzarima.net \
    --to=forsyth@terzarima.net \
    --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).