9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Enrique Soriano Salvador <esoriano@lsub.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: [9fans] plain passwords and keyfs
Date: Fri, 23 Jul 2004 15:14:56 +0200	[thread overview]
Message-ID: <1090588496.13043.40.camel@ronin.dat.escet.urjc.es> (raw)

Why does keyfs serve the users password in plain text on the file
/mnt/keys/user/secret ?

I know that the man in front of the
cpu/auth server is the only one that can see the users passwords...  but
it can be dangerous for users that have the same
password for different systems (unix,
win, plan9 ...)

{ I am changing my Unix passwords
in this very moment, so nemo and gorka can now see my password-for-all
in plain text!!! :) }

As far as I know, in other systems (i.e. unix) the admin cannot  see the
users passwords (of course, he can try to crack the /etc/shadow file or
to make other malicious acts)

I am sure that there is a design related
explanation for that...

Thanks!

Q.





             reply	other threads:[~2004-07-23 13:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-23 13:14 Enrique Soriano Salvador [this message]
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
     [not found] <5d791b8fa2a574fb6cc322e97696054c@terzarima.net>
2004-07-23 17:46 ` Enrique Soriano
2004-07-24  8:45   ` Charles Forsyth
2004-07-24 13:48     ` Steve Simon
2004-07-25 19:19       ` Charles Forsyth
2004-07-25 20:00         ` Steve Simon

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=1090588496.13043.40.camel@ronin.dat.escet.urjc.es \
    --to=esoriano@lsub.org \
    --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).