9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Skip Tavakkolian <skip.tavakkolian@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Factotum vs SASL
Date: Tue, 18 Nov 2014 00:22:26 -0800	[thread overview]
Message-ID: <CAJSxfmJhoSmzOYVP=w7bN9nf7CJ2u+hMUMZdkNVfYON3VUKU-w@mail.gmail.com> (raw)
In-Reply-To: <546981BE.90704@gr13.net>

[-- Attachment #1: Type: text/plain, Size: 1282 bytes --]

to do a comparative analysis of the functions it makes sense to know one
side very well. i found it easier to understand factotum and compare the
others to factotum. to me SASL is more like the functions of factotum's rpc
and proto files.  Window's Local Security Authority (LSA) combined with
Security Support Provider Interface (SSPI) and the corresponding protocol
DDL's, is more comparable to factotum's credentials caching,
rpc/proto/needkey, etc fs interface and how it negotiates change of
identity of a verified process using cap(3).  on Linux, for a server,
SASL+setuid program+PAM is sort-of like factotum and SASL+app is sort of
like factotum for a client.


On Sun, Nov 16, 2014 at 9:03 PM, Enrico Weigelt, metux IT consult <
enrico.weigelt@gr13.net> wrote:

> Hi folks,
>
> I've got the impression that there're some similarities between SASL
> (saslauthd) and Factotum - at least at the point that both are
> offloading actual authentication handshakes to a separate service.
> But I have to admit that I didn't have done a deeper analysis of
> these two.
>
> Could anybody with deeper insight perhaps give some detailed
> comparison between them ?
>
>
> greetings,
> --
> Enrico Weigelt,
> metux IT consulting
> +49-151-27565287
>
>

[-- Attachment #2: Type: text/html, Size: 1706 bytes --]

  parent reply	other threads:[~2014-11-18  8:22 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-17  5:03 Enrico Weigelt, metux IT consult
2014-11-17  5:57 ` Lyndon Nerenberg
2014-11-17  6:29 ` lucio
2014-11-17 13:58   ` erik quanstrom
2014-11-17 14:14     ` lucio
2014-11-18  8:22 ` Skip Tavakkolian [this message]
2014-11-29 19:46   ` Enrico Weigelt, metux IT consult
2014-11-29 19:46     ` erik quanstrom
2014-11-29 21:20       ` Enrico Weigelt, metux IT consult
2014-11-29 21:23         ` erik quanstrom
2014-12-01  6:28           ` Enrico Weigelt, metux IT consult
2014-12-01  7:00             ` lucio
2014-12-01 10:38               ` tlaronde
2014-12-01 10:45                 ` lucio
2014-12-02  4:00                 ` Enrico Weigelt, metux IT consult
2014-12-02  4:08                   ` erik quanstrom
2014-12-02 15:40                     ` plannine
2014-12-02 16:33                       ` Wes Kussmaul
2014-12-02 20:32                       ` Skip Tavakkolian
2014-12-02 22:20                       ` Enrico Weigelt, metux IT consult
2014-12-02  9:50                   ` Richard Miller
2014-12-02 22:15                     ` Enrico Weigelt, metux IT consult
2014-12-01 12:14             ` Stuart Morrow
2014-12-02 20:32     ` Skip Tavakkolian
2015-01-01 14:55     ` Teodoro Santoni

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='CAJSxfmJhoSmzOYVP=w7bN9nf7CJ2u+hMUMZdkNVfYON3VUKU-w@mail.gmail.com' \
    --to=skip.tavakkolian@gmail.com \
    --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).