From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] possible file server setup
Date: Wed, 2 Dec 2020 21:23:27 +0100 [thread overview]
Message-ID: <CAFSF3XMTKDD8NJi76yZ41q6U93542cmD3dzC0Hv5WGsG9REeCQ@mail.gmail.com> (raw)
In-Reply-To: <CAHjwAuwbv=1cveAX-4bcAqL+C600SwU2UZKn1ANwBu1NMgDKPw@mail.gmail.com>
yeah as sam-d says.
on boot you can enter the password into a keyboard. then there is no
need for nvram.
and dp9ik uses only passwords, no complicated certificate chains that
need special storage...
On 12/2/20, Silas McCroskey <inkswinc@gmail.com> wrote:
>> I was wondering wether it is possible to have a separate auth server that
>> TCP/PXE boots from the fileserver. It looks like the idiomatic way on one
>> end, a “chicken and egg” problem on the other!
>
> you can auth to another machine without using an auth server as long
> as you're authing as the server's hostowner.
>
> You can use this trick to bring the auth server up second via PXE
> (with nvram on a USB stick or something to make it automatic, if
> desired) and then use the auth server for everything else.
>
> I don't know how common this is... I'm pretty sure I did it with VMs a
> while back, but on hardware I've always run combined file + auth.
>
> - sam-d
>
next prev parent reply other threads:[~2020-12-02 20:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-17 16:24 Daniel Morandini
2020-11-17 16:33 ` [9front] " hiro
2020-11-18 13:21 ` Daniel Morandini
2020-12-02 19:33 ` Daniel Morandini
2020-12-02 20:13 ` Silas McCroskey
2020-12-02 20:23 ` hiro [this message]
2020-12-02 21:37 ` Daniel Morandini
2020-12-02 23:18 ` hiro
2020-12-03 7:33 ` Daniel Morandini
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=CAFSF3XMTKDD8NJi76yZ41q6U93542cmD3dzC0Hv5WGsG9REeCQ@mail.gmail.com \
--to=23hiro@gmail.com \
--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).