9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "sirjofri via 9fans" <9fans@9fans.net>
To: 9fans <9fans@9fans.net>
Subject: Re: [9fans] Solo factotum (was: Enterable namespaces: /proc/pid/$ns/srv)
Date: Mon, 29 Dec 2025 15:40:38 +0100	[thread overview]
Message-ID: <e70fea20-3ed8-4180-a974-629509e7243d@sirjofri.de> (raw)
In-Reply-To: <760adea1-7ed3-4c91-a320-8e54267cb01c@app.fastmail.com>

29.12.2025 14:03:55 David Arroyo <droyo@aqwari.net>:
> On Sun, Dec 14, 2025, at 07:43, sirjofri wrote:
>> More ideally, but also offtopic, I's like to have a factotum usb drive,
>> where the secrets never leave the usb device. It would talk 9p directly
>> over the serial bus.
>
> I think this is a great idea; an HSM-like device with an interface that
> doesn't suck. After some discussion about this idea on IRC, I want to
> try and implement it.

That sounds cool and I can't wait for the results.

> It has a capacitive button
> which would work nice with the `confirm` attribute of factotum to require
> human presence before using a key.

Somehow funny that factotum has this feature that's described in the fido standard years later.

> I'm trying to figure out how to serve 9P over USB, which I know very
> little about.  My initial plan is to make the device a USB serial
> device that expects 9P, then try to mount the /dev/eiaUN device.
> However, nusb(4) states that the nusb/serial driver only works for two
> chips, so I'd have to add support for this one.  That's not a problem,
> but am I going in the right direction?

I don't know much about USB, though maybe the nusb/serial restriction only applies for real rxtx serial converters or something? I mean, USB is serial by its nature so any communication is serial, I guess... But I also don't know. However, being able to mount 9p from a USB serial line would be interesting for many use cases.

For the factotum key, another complex issue could be that factotum needs access to the network interface for auth stuff. I was thinking about this, and plan 9 makes it possible to solve this. One could for example put the /net of the host into a /srv of the factotum key, or something like that. In any case, this is a challenge to find a good and clean solution.

sirjofri.

------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T969c381dcd9c760d-M0d2ff5a543c1c0839177815f
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

  reply	other threads:[~2025-12-29 15: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 [this message]
2025-12-30  6:28   ` David Arroyo
2025-12-30 17:56     ` [9fans] Solo factotum Dworkin Muller
2025-12-30 21:37       ` 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=e70fea20-3ed8-4180-a974-629509e7243d@sirjofri.de \
    --to=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).