unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: jbranso@dismail.de
To: "Csepp" <raingloom@riseup.net>, "Vagrant Cascadian" <vagrant@debian.org>
Cc: "zimoun" <zimon.toutoune@gmail.com>,
	"Tobias Geerinckx-Rice" <me@tobias.gr>,
	guix-devel@gnu.org
Subject: Re: Could Guix System eventually run on top of HyperbolaBSD ? slightly off topic
Date: Tue, 19 Jul 2022 21:46:56 +0000	[thread overview]
Message-ID: <9b226426269f805a4d72384c0e285354@dismail.de> (raw)
In-Reply-To: <877d4eaad1.fsf@riseup.net>

July 15, 2022 7:23 AM, "Csepp" <raingloom@riseup.net> wrote:

> Vagrant Cascadian <vagrant@debian.org> writes:
> 
> 
> If the goal is to produce highly secure servers than I'd like to suggest
> unikernels once again. No Guix running on the deployed server, but the
> server image is built by and possibly deployed by Guix.
> Of course the downside is that they do a whole lot less than OpenBSD or
> Linux. But if your use case is already covered, that's actually a
> positive, since no extra features means smaller attack surface.
> MirageOS could be a good starting point, since we already have a good
> chunk of Ocaml tooling integrated into Guix.
> http://unikernel.org/projects
> There was a Nix project with similar aims that sadly fizzled out, so
> it's probably not exactly an easy task to tackle, but it's much easier
> than porting Guix to a new kernel and packaging a userland for that
> kernel.

Thanks for the suggestion!  That would be a really secure server!


  parent reply	other threads:[~2022-07-19 21:47 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-11 22:44 Could Guix System eventually run on top of HyperbolaBSD ? slightly off topic Joshua Branson
2022-07-12  0:16 ` indieterminacy
2022-07-12  2:18   ` Joshua Branson
2022-07-12  3:56     ` Akib Azmain Turja
2022-07-12 13:39       ` Joshua Branson
2022-07-12  8:25     ` Josselin Poiret
2022-07-12 13:36       ` Joshua Branson
2022-07-12 20:12       ` Csepp
2022-07-14 10:23 ` zimoun
2022-07-14 10:40   ` Tobias Geerinckx-Rice
2022-07-14 13:06     ` zimoun
2022-07-14 15:38       ` Vagrant Cascadian
2022-07-15 11:09         ` Csepp
2022-07-19 21:46         ` jbranso [this message]
2022-07-19 21:44       ` jbranso
2022-07-19 21:43     ` jbranso
2022-07-19 21:41 ` jbranso
  -- strict thread matches above, loose matches on Subject: below --
2022-07-20 16:03 Raghav Gururajan
2022-07-20 16:49 ` Maxime Devos
2022-07-21 16:27 ` zimoun

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9b226426269f805a4d72384c0e285354@dismail.de \
    --to=jbranso@dismail.de \
    --cc=guix-devel@gnu.org \
    --cc=me@tobias.gr \
    --cc=raingloom@riseup.net \
    --cc=vagrant@debian.org \
    --cc=zimon.toutoune@gmail.com \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).