9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Alexander Povolotsky <ap80@lucent.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Drawterm vs Autentication Server
Date: Tue, 24 Apr 2001 09:00:31 +0000	[thread overview]
Message-ID: <9c2030$38n@nntpb.cb.lucent.com> (raw)
In-Reply-To: <200104231539.LAA20789@smtp1.fas.harvard.edu>

I did not mean that the enhancement I am requesting for Plan 9 owners to
implement only relates to the "drawterm" (Solaris code) side
(though implementation of the "noauth" modifier and passing it to Plan 9 cpu
server during connection  belongs to that part
of the code).
Obviously the Plan 9 listener should also be modified as a part of
fulfilling my request.

>You could consider removing
> the authentication protocol from both drawterm and
> the cpu listener, but that's more work than just setting
> up a proper auth server.

If what I am asking above is too much ..., then
instead of me removing the authentication protocol  in my copy of the code,
I would like to ask Plan 9 code owners to implement in the next standard
distribution.

If even the latter request is too hard to honor,
then at least I would like to ask Plan 9 code owners to provide for ability
to start "authentication server"
manually, thus allowing to fully upgrade from Plan 9 terminal to Plan 9 CPU
server "on the fly",
i.e. without reconfiguring and rebuilding the kernel.

Best Regards,
Alex Povolotsky
----------------------------------------------------------------------------
---------------------------------
<rsc@plan9.bell-labs.com> wrote in message
news:200104231539.LAA20789@smtp1.fas.harvard.edu...
> > Is it possible to consider implementation  of "noauth" option for the
> > drawterm (running on Solaris )
> >  to allow to connect to the Plan 9 machine without authentication ?
>
> It's not drawterm that is insisting on authentication,
> but the cpu server itself.  You could consider removing
> the authentication protocol from both drawterm and
> the cpu listener, but that's more work than just setting
> up a proper auth server.
>
> Russ


  reply	other threads:[~2001-04-24  9:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-23 15:39 rsc
2001-04-24  9:00 ` Alexander Povolotsky [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-04-24 12:32 presotto
2001-04-24 10:15 forsyth
2001-04-23  9:54 Alexander Povolotsky

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='9c2030$38n@nntpb.cb.lucent.com' \
    --to=ap80@lucent.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).