9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: lucio@proxima.alt.za
To: 9fans@cse.psu.edu
Subject: Re: [9fans] factotum/802.1x catch 22?
Date: Thu, 22 Mar 2007 06:38:11 +0200	[thread overview]
Message-ID: <9321241f7154cd4cd7fab6579c8916b0@proxima.alt.za> (raw)
In-Reply-To: <200703212303.l2LN3Vl25960@zamenhof.cs.utwente.nl>

> I've extended my factotum with an 'authaddr' ctl verb.
> (don't know wat can of worms it opens...)

Sure, anything in security has its risks.  It may be safer if this
could occur exactly once and that if "-a authaddr" was previously
given, the command was rejected.  But that may be overkill.  Still,
I'd do it.  And -A would override for those who like living
dangerously.

> reseiving it it will also trigger an attempt to access
> secstore if it wanted to do that on startup but couldn't
> (like because there was no network configured yet.)

That is also a useful function in itself and I see no risks in it.  If
you add it in as a separate function, make sure we can add the
location of the secstore.  Mind you, that might be necessary in the
"authaddr" command, too, possibly as an option.

I second such changes, can you submit them here if "patch" does not
like them?  :-) :-)

*** Off Topic ***

I had a brief chat with "patch" and it strikes me now that the delay
in accepting complex patches might be alleviated if such patches could
be reviewed by 9fans, that is to say, publicly, by request.  Say, for
example, that we are asked to comment on Axel's patch and we return a
verdict, as part of the "patch" process.  No need to publish the
request, those interested can look on sources and post the result
there.

Two factors would seem important: usefulness as well as correctness.
Maybe on a scale of 1 to 5.  I don't know if I'm skilled enough to
alter patch/* accordingly, but I could try.

++L



  reply	other threads:[~2007-03-22  4:38 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-19 13:47 Axel Belinfante
2007-03-20 13:44 ` erik quanstrom
2007-03-21 23:03 ` Axel Belinfante
2007-03-22  4:38   ` lucio [this message]
2007-03-22  5:19     ` Uriel
2007-03-22  6:13       ` Noah Evans
2007-03-22  9:11     ` erik quanstrom
2007-03-22 15:31       ` Joel C. Salomon
2007-03-25 11:56     ` Axel Belinfante
2007-03-25 12:12       ` Uriel
2007-03-25 14:48         ` lucio
2007-03-25 20:38           ` Charles Forsyth
2007-03-26  6:51             ` lucio
2007-03-27  9:24               ` Charles Forsyth
2007-03-27 17:29                 ` lucio
2007-03-25 15:40         ` erik quanstrom
2007-03-25 16:44           ` lucio
2007-03-25 20:15           ` Axel Belinfante
2007-03-25 14:46       ` lucio

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=9321241f7154cd4cd7fab6579c8916b0@proxima.alt.za \
    --to=lucio@proxima.alt.za \
    --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).