From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org
X-Spam-Level: 
X-Spam-Status: No, score=1.0 required=5.0 tests=DATE_IN_PAST_12_24,
	DKIM_INVALID,DKIM_SIGNED,T_SCC_BODY_TEXT_LINE autolearn=no
	autolearn_force=no version=3.4.4
Received: (qmail 12158 invoked from network); 15 Feb 2022 08:47:52 -0000
Received: from 4ess.inri.net (216.126.196.42)
  by inbox.vuxu.org with ESMTPUTF8; 15 Feb 2022 08:47:52 -0000
Received: from a10-18.smtp-out.amazonses.com ([54.240.10.18]) by 4ess; Mon Feb 14 09:48:19 -0500 2022
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
	s=a4tryept6ew4kp6pdupzhtikhmwphypy; d=mapinternet.com;
	t=1644850093;
	h=From:Content-Type:Content-Transfer-Encoding:Mime-Version:Subject:Message-Id:Date:To;
	bh=ZBsL33sIjUmmP8nccxfHZfPGtL9LSt11hBnEFsbxOjc=;
	b=2ltZZv1IowidKhPAgCe70kQBjSlINTfsQo7x2RLXIAcsqwyBSyUDUM/lYFtoCXdG
	QZGIUUixV45+jpD1Bfbn3dmpX1alyWLqHbJ7nsTWBufRGz27VqZc68qVi2zEAB8I28i
	4Z+ziFVVcEYp/xK4F3/AXCUmCprvIwa1roDJuGCo=
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
	s=ug7nbtf4gccmlpwj322ax3p6ow6yfsug; d=amazonses.com; t=1644850093;
	h=From:Content-Type:Content-Transfer-Encoding:Mime-Version:Subject:Message-Id:Date:To:Feedback-ID;
	bh=ZBsL33sIjUmmP8nccxfHZfPGtL9LSt11hBnEFsbxOjc=;
	b=JcqqktVvwtw5avuRVcz/mzbtSitYvnML42FTcaRXueIa/DlDfG9ArPsLZiokyqTc
	nJfMVdFYXsMNF+13FZMxdqmBvTtZSwU/IrdL/nBADPVv2fneNXQiEhHdfwJS8hy5Max
	DKcn8rrv0aCHhhj0/xQekwr2qjRVQnN/Jf0v0zFE=
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=50.202.122.66; envelope-from=<mackbw@mapinternet.com>;
From: Mack Wallace <mackbw@mapinternet.com>
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\))
Message-ID: <0100017ef8b49b77-efd8ac91-87b4-4754-96ff-4842b10dcb2a-000000@email.amazonses.com>
Date: Mon, 14 Feb 2022 14:48:13 +0000
To: 9front@9front.org
X-Mailer: Apple Mail (2.3608.120.23.2.1)
X-Qnum: 1327845528
X-Authenticated-User: mackbw@mapinternet.com 
Feedback-ID: 1.us-east-1.X+xhoL9JiEQ8K0gzGjV36WZnSewOzOs8YCWuakKsLBY=:AmazonSES
X-SES-Outgoing: 2022.02.14-54.240.10.18
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: object-oriented distributed strategy-scale deep-learning generator 
Subject: [9front] Can additional keys be added to nvram?
Reply-To: 9front@9front.org
Precedence: bulk

I have some CPU servers that connect to some other devices via SSH. =
Being a CPU server, factotum doesn=E2=80=99t ask for passwords, and this =
CPU server is remote anyway and will running scripts to access the other =
hardware.=20

While we could add the key (username, password, ssh thumb) to factotum =
through a script, it would be a lot nicer to have the other one or two =
keys loaded from nvram. I know the nvram partition is typically small =
(only 512 bytes), but I also know that a larger nvram partition could be =
made. So is there a way to add keys to the nvram?

I did try to use auth/factotum -k (with -S) to 'write=E2=80=99 factotum =
to nvram as stated in the man page. We also checked the secstore man =
page and tried the procedure outlined there (though lacked confidence =
that would work because it is specific for a secstore server) - that did =
not work either.=20

Look forward to the response.

Thanks,

Mack