9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Kurt H Maier <khm@sciops.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] 9P or better file services for multiple platforms
Date: Sun,  2 Sep 2018 16:22:14 -0700	[thread overview]
Message-ID: <20180902232214.GA66313@wopr> (raw)
In-Reply-To: <CAJQ9t7jdAu7_yYmu+vJHHRZD5xgLsQHshmoW6ATi7qHjPM5+2A@mail.gmail.com>

On Sun, Sep 02, 2018 at 08:09:55PM +0200, Lucio De Re wrote:
> On 9/2/18, Skip Tavakkolian <skip.tavakkolian@gmail.com> wrote:
> >
> > Regarding authentication and access control, I think the only *standard*
> > option for a mixed OS environment (Plan 9, Linux/*BSD, Windows) is
> > Kerberos.
> >
> Is that still actively used (I mean, outside of Microsoft's attempted
> hi-jacking)? In my Linux-prone wider environment, the name is never
> uttered.

Yes, it's extremely common in many business and government
environments.  All of linux's weird-ass authentication systems are
poorly-reinvented kerberos implementations, with the primary limitations
and pain points directly stemming from unix tropes.  Generally someone
comes up with a bad idea, everyone adopts it, and then that bad idea
slowly evolves as closely as it can to being kerberos.

Most commonly, someone will mandate two-factor authentication, and
kerberos tickets (usually via GSSAPI) are the back-end, regardless of
which security tokens (RSA SecurID, smart cards, yubikeys, etc) are
chosen.

khm



  reply	other threads:[~2018-09-02 23:22 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-01  5:21 Lucio De Re
2018-09-01 10:29 ` Rui Carmo
2018-09-01 13:33   ` Lucio De Re
2018-09-01 14:03     ` Emery Hemingway
2018-09-01 14:33       ` Lucio De Re
2018-09-01 14:49         ` Lucio De Re
2018-09-01 18:00           ` Joseph Stewart
2018-09-02 11:14             ` Lucio De Re
2018-09-02 11:24               ` hiro
2018-09-02 11:30                 ` hiro
2018-09-02 12:01                   ` Lucio De Re
2018-09-02 12:16                     ` hiro
2018-09-02 12:22                       ` hiro
2018-09-02 17:51                         ` Lucio De Re
2018-09-02 18:00                           ` hiro
2018-09-02 18:07                           ` hiro
2018-09-02 11:43                 ` Lucio De Re
2018-09-02 11:48                 ` Lucio De Re
2018-09-02 12:07                   ` hiro
2018-09-03  4:03                     ` Lucio De Re
2018-09-01 18:32   ` Ethan Gardener
2018-09-01 20:33     ` hiro
2018-09-02 11:22       ` Lucio De Re
2018-09-02 11:25         ` Lucio De Re
2018-09-02 11:32           ` hiro
2018-09-02 17:44 ` Ethan Gardener
2018-09-02 18:02   ` Lucio De Re
2018-09-02 18:19     ` Ethan Gardener
2018-09-02 18:24       ` Lucio De Re
2018-09-02 18:55         ` Ethan Gardener
2018-09-02 17:47 ` Skip Tavakkolian
2018-09-02 17:55   ` Lucio De Re
2018-09-02 18:09   ` Lucio De Re
2018-09-02 23:22     ` Kurt H Maier [this message]
2018-09-03  3:22       ` Lucio De Re
     [not found] <600987589.2057147.1535842278571.ref@mail.yahoo.com>
2018-09-01 22:51 ` Brian L. Stuart
2018-09-02  9:25   ` Lucio De Re
2018-09-02 17:03     ` Bakul Shah
2018-09-02 13:33 cinap_lenrek

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=20180902232214.GA66313@wopr \
    --to=khm@sciops.net \
    --cc=9fans@9fans.net \
    /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).