9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: arisawa@ar.aichi-u.ac.jp
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] factotum & invalid entries
Date: Mon,  7 Feb 2005 17:09:27 +0900	[thread overview]
Message-ID: <65ce4516c890a7cc231be49f75689b0e@ar.aichi-u.ac.jp> (raw)
In-Reply-To: <1ae7aeda5561f403475aea19a6f0b493@proxima.alt.za>

some miscommunication probably because of my sketchy explanation.

My image is
term% cat /mnt/factotum/ctl
key proto=p9sk1 dom=aichi-u.ac.jp user=arisawa !password?
key proto=p9sk1 dom=aichi-u.ac.jp user=bootes !password?
disabled key proto=p9sk1 dom=inside.plan9.bell-labs.com user=arisawa
!password?
key proto=p9sk1 dom=grid.bell-labs.com user=arisawa !password?
term%

Factotum knows attribute value list is useless or not.
If the list is confirmed useless in authentication process,
I would like disabled is put at the beginning.
Next time I will fix the problem and put
key proto=p9sk1 dom=outside.plan9.bell-labs.com user=arisawa !password?
then I will get
term% cat /mnt/factotum/ctl
key proto=p9sk1 dom=aichi-u.ac.jp user=arisawa !password?
key proto=p9sk1 dom=aichi-u.ac.jp user=bootes !password?
key proto=p9sk1 dom=outside.plan9.bell-labs.com user=arisawa !password?
key proto=p9sk1 dom=grid.bell-labs.com user=arisawa !password?
term%

If I put wrong user name, say alice instead of arisawa, then factotum
is not
authenticated. therefore we will get:
term% cat /mnt/factotum/ctl
key proto=p9sk1 dom=aichi-u.ac.jp user=arisawa !password?
key proto=p9sk1 dom=aichi-u.ac.jp user=bootes !password?
key proto=p9sk1 dom=outside.plan9.bell-labs.com user=arisawa !password?
key proto=p9sk1 dom=grid.bell-labs.com user=arisawa !password?
disabled key proto=p9sk1 dom=outside.plan9.bell-labs.com user=alice
!password?
term%
Wrong user name does no harm

The current problem is in that factotum put every data even if the data
is confirmed
invalid.

The above is rough sketch. we should examine more.

Kenji Arisawa



  reply	other threads:[~2005-02-07  8:09 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-06  2:45 YAMANASHI Takeshi
2005-02-06 16:12 ` Russ Cox
2005-02-06 20:00   ` Tiit Lankots
2005-02-07  5:25   ` Lucio De Re
2005-02-07  5:42     ` arisawa
2005-02-07  6:03       ` Lucio De Re
2005-02-07  6:47         ` arisawa
2005-02-07  7:26           ` Lucio De Re
2005-02-07  8:09             ` arisawa [this message]
2005-02-07  8:55               ` Lucio De Re
2005-02-07  9:15                 ` arisawa
2005-02-07 10:05                   ` Lucio De Re
2005-02-08  5:12                     ` Russ Cox
2005-02-08 16:36                       ` rog
2005-02-08 16:42                         ` Russ Cox
2005-02-08 16:55                           ` Lucio De Re
2005-02-08 16:51                             ` rog
2005-02-08 16:52                             ` Devon H. O'Dell
2005-02-08 17:08                               ` Lucio De Re
2005-02-08 17:10                                 ` rog
2005-02-13 20:03 ` Russ Cox
  -- strict thread matches above, loose matches on Subject: below --
2005-02-14  2:35 YAMANASHI Takeshi
2005-02-14  3:42 ` Russ Cox
2005-02-04  9:31 [9fans] netpbm C H Forsyth
2005-02-05 18:26 ` [9fans] factotum & invalid entries Tiit Lankots
2005-02-05 20:12   ` Russ Cox

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=65ce4516c890a7cc231be49f75689b0e@ar.aichi-u.ac.jp \
    --to=arisawa@ar.aichi-u.ac.jp \
    --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).