From: Dworkin Muller <dworkin@weaselfish.com>
To: 9fans@9fans.net, david@arroyo.cc
Subject: Re: [9fans] Solo factotum
Date: Tue, 30 Dec 2025 10:56:43 -0700 (MST) [thread overview]
Message-ID: <20251230.105643.1185666151293172501.dworkin@weaselfish.com> (raw)
In-Reply-To: <1076b151-30f7-42e9-ba16-be8ddefc64c6@app.fastmail.com>
On Tue, 30 Dec 2025 01:28:51 -0500, "David Arroyo" <david@arroyo.cc> wrote:
david> On Mon, Dec 29, 2025, at 09:40, sirjofri via 9fans wrote:
david> > For the factotum key, another complex issue could be that factotum
david> > needs access to the network interface for auth stuff. I was thinking
david>
david> I had not thought about that. I will probably start with the protocols
david> which can be completed offline, such as ssh. For protocols which need
david> the auth server to validate the peer's key, I'm not sure. Perhaps the
Alternatively, just set it up as a secret store, like is done with
terminals. Not quite as elegant/cool, but perhaps more practical.
Dworkin
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Ta60752663ff08448-M37f48b8734998f5a42ba5afc
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2025-12-30 18:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-29 10:57 [9fans] Solo factotum (was: Enterable namespaces: /proc/pid/$ns/srv) David Arroyo
2025-12-29 14:40 ` sirjofri via 9fans
2025-12-30 6:28 ` David Arroyo
2025-12-30 17:56 ` Dworkin Muller [this message]
2025-12-30 21:37 ` [9fans] Solo factotum sirjofri via 9fans
2025-12-30 23:29 ` ori
2025-12-31 4:24 ` Steve Simon
2025-12-31 5:21 ` David Arroyo
2025-12-31 17:31 ` ori
2025-12-31 21:47 ` Steve Simon
2025-12-31 9:40 ` sirjofri via 9fans
2025-12-31 16:26 ` ori
2025-12-31 8:51 ` Skip Tavakkolian
2025-12-29 15:32 ` [9fans] Solo factotum (was: Enterable namespaces: /proc/pid/$ns/srv) Shawn Rutledge
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=20251230.105643.1185666151293172501.dworkin@weaselfish.com \
--to=dworkin@weaselfish.com \
--cc=9fans@9fans.net \
--cc=david@arroyo.cc \
/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).