Re: [9front] Introduction and regarding guidance

["Noam Preil" <noam@pixelhero.dev>]

Hey,

I looked into this a few months ago for much the same reason.

First, drawterm has to auth *to* the remote, to start the session. To do
so via secstore, it loads the auth key from secstore, discards the 
secstore file, and uses the key to auth in (then forgetting the key as
with any other).

Factotum loaded *from the remote end* then gets started, and wants the
keys from secstore. So, it logs into secstore as with any other time
you run auth/factotum in userspace.

In theory, there's a couple solutions:

* Accept the status quo. This isn't a great answer, but really there's
two things doing authentication, so why *shouldn't* it ask for the
password twice?

* Well, maybe there shouldn't be two things during authentication. If
factotum is run *by drawterm*, and that normal factotum is used for
initial auth, then there's no need to run factotum after connecting, and
the password only gets asked for once.

* Or, maybe drawterm should hold on to the factotum keys from secstore,
seed them to the factotum, and *then* forget them.

There's probably a couple options I haven't thought of. The hardest part
is to figure out *desired* behavior. Once that's known, the actual code
should be relatively straightforward.

- Noam Preil