9front - general discussion about 9front
 help / color / mirror / Atom feed
From: alex <alex9-ml@proton.me>
To: "9front@9front.org" <9front@9front.org>
Subject: [9front] local auth without cpu service
Date: Thu, 27 Jun 2024 07:16:46 +0000	[thread overview]
Message-ID: <Y6cgoXjnVbDUKhyw2mufiyYff2_3lkP5ITOXtowC8xGYcDscy-gf2Zc72UgYKv09-tUx-UFiKZxedQJyWruOroR5CrLDLNhL0pK4BTGHlig=@proton.me> (raw)

Hello, 

I would like to use factotum on my notebook, without running a cpu service on it (since it is the only 9front device in my network at the moment).

At the moment I don't understand all the dependencies, but when I understand the fqa correctly, I think it is something like this:

- edit /lib/ndb/local, so the local system will be used as auth (setting "auth" and "authdom" matching to "sys", "ipnet" and "dom")
- setting nvram in plan9.ini (in the fqa it states: "nvram=#S/YOURDRIVE/nvram", so I've added "nvram=#S/sdE1/nvram", but I'm not sure whether it should read "nvram=local!/dev/sdE1/nvram", since "ls #S" is showing glenda's home dir and nobootprompt in plan9.ini has the value "local!/dev/sdE1/fscache")
- running auth/wrkey (for making use of the nvram?)
- adding user to the auth server ("auth/keyfs" and "auth/changeuser glenda")
- set up secstored ("mkdir /adm/secstore" and "chmod 770 /adm/secstore")
- start secstored at boot time ("echo auth/secstored > /cfg/$sysname/termrc")
- adding glenda to secstore (auth/secstore glenda")
- using secstore with ipso

I can't use ipso ("secstore read failed - bad password?"), but I think, I know why that is.. I've set no secstore password in auth/wrkey, but I've added glenda to secstore setting a password). Are these steps correct in principle? Can I redo my first auth/wrkey prompts?

Thank you very much in advance!

Best regards, 
Alex

             reply	other threads:[~2024-06-27  7:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-27  7:16 alex [this message]
2024-06-27  9:17 ` sirjofri

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='Y6cgoXjnVbDUKhyw2mufiyYff2_3lkP5ITOXtowC8xGYcDscy-gf2Zc72UgYKv09-tUx-UFiKZxedQJyWruOroR5CrLDLNhL0pK4BTGHlig=@proton.me' \
    --to=alex9-ml@proton.me \
    --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).