From: unobe@cpan.org
To: 9front@9front.org
Subject: Re: [9front] dp9ik plugins for pam and bsd auth.
Date: Wed, 08 Sep 2021 10:49:43 -0700 [thread overview]
Message-ID: <413DD0E37E3D9724879653B3B5F8E467@smtp.pobox.com> (raw)
In-Reply-To: <35FD7A952D0CFEC0075D185A3594FCD5@eigenstate.org>
Quoth ori@eigenstate.org:
> Quoth Jacob Moody <moody@mail.posixcafe.org>:
> > Hello all,
> >
> > I sent some mail previously regarding some work on a standalone tlsclient ripped out of drawterm.
> > The repo[0] now contains a pam module and bsd auth executable for use in making UNIX system
> > authentication defer to a 9front authentication server. The ssl library has been changed
> > to use openssl rather then gnutls as well. I personally have been using the pam module for a
> > couple months now and haven't had much issue with it. I figure this might be interesting
> > to those running a hybrid network.
> >
> > Thanks,
> > moody
> >
> > [0] http://shithub.us/moody/tlsclient/HEAD/info.html
> >
This is great! Thanks moody.
> Thanks, this actually looks like something I should try out.
>
> ...So, who's going to do the factotum based chrome password
> manager extension?
An extension would be nice. I began working on a factotum extension
but decided to just write a JS snippet that communicates via a
websocket to a Perl process that was a pass-through to (p9p's)
factotum. IIRC, 'twas non-trivial to write an extension, so I took
the path of least resistance. The JS snippet was rudimentary--I had
stored it as a bookmark so I could "fill in" whichever site I was
using. I haven't used it for more than a year (tempus volat), but I
can post it somewhere if anyone is interested in looking at the JS and
Perl. I never did get the 'confirm' functionality implemented within
the browser, but maybe that was a benefit since the browser didn't
have full control of the secstore and the confirmation had to occur
outside the browser.
prev parent reply other threads:[~2021-09-08 17:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-05 16:02 Jacob Moody
2021-09-07 22:03 ` ori
2021-09-08 15:17 ` hiro
2021-09-08 17:49 ` unobe [this message]
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=413DD0E37E3D9724879653B3B5F8E467@smtp.pobox.com \
--to=unobe@cpan.org \
--cc=9front@9front.org \
/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).