From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: help-guix <help-guix@gnu.org>
Subject: Re: Putting a file into system image ~user/ but not on reconfigure
Date: Thu, 10 Aug 2023 14:38:24 +0200 [thread overview]
Message-ID: <bbd3326f-2057-3495-7598-17aead98bf13@crazy-compilers.com> (raw)
In-Reply-To: <ZNTUQ1IWRb29KqrQ@ws>
Am 10.08.23 um 14:12 schrieb wolf:
>
> I guess you could have a script that would use the existence of the key itself
> as a marker. In that case you would likely want to recreate it if the marker
> (key) got deleted,
No! The key must not be recreated. The key is expected to be replaced by
a new one when the box will become a machine. Thus, using the key as a
marker is not possible, as the would recreate the insecure key on next
reboot. The key must never ever be put into back into place.
> I do not have much experience with Vagrant, but I assumed the general idea for
> these kind of systems declarative systems is to just recreate the when updates
> are required. Is it expected to actually run guix reconfigure inside the VM?
This depends on how one uses the virtual machines :-)
And even if it is not expected to run guix reconfigure on it: If one
does, this but open a front door to the system - which is not what one
wants.
Anyhow, thanks for sharing thoughts,
--
Regards
Hartmut Goebel
| Hartmut Goebel | h.goebel@crazy-compilers.com |
| www.crazy-compilers.com | compilers which you thought are impossible |
next prev parent reply other threads:[~2023-08-10 12:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 22:11 Putting a file into system image ~user/ but not on reconfigure Hartmut Goebel
2023-08-10 12:12 ` wolf
2023-08-10 12:38 ` Hartmut Goebel [this message]
2023-08-13 14:58 ` Efraim Flashner
2023-08-17 19:30 ` Hartmut Goebel
2023-08-18 12:53 ` Efraim Flashner
2023-08-24 18:57 ` Hartmut Goebel
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=bbd3326f-2057-3495-7598-17aead98bf13@crazy-compilers.com \
--to=h.goebel@crazy-compilers.com \
--cc=help-guix@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.