qusal/salt/mirage-builder
Ben Grande 422b01e0f6 feat: remove audiovm setting when unnecessary
Decrease audio attack surface to qubes that will never need to use it.
2024-01-20 19:34:39 +01:00
..
files/client refactor: import armored gpg keys instead of db 2024-01-03 21:40:05 +01:00
clone.sls refactor: initial commit 2023-11-13 14:33:28 +00:00
clone.top refactor: initial commit 2023-11-13 14:33:28 +00:00
configure.sls refactor: import armored gpg keys instead of db 2024-01-03 21:40:05 +01:00
configure.top refactor: initial commit 2023-11-13 14:33:28 +00:00
create.sls feat: remove audiovm setting when unnecessary 2024-01-20 19:34:39 +01:00
create.top refactor: initial commit 2023-11-13 14:33:28 +00:00
init.top refactor: initial commit 2023-11-13 14:33:28 +00:00
install.sls feat: remove extraneous passwordless root 2024-01-05 12:03:23 +01:00
install.top refactor: initial commit 2023-11-13 14:33:28 +00:00
README.md refactor: initial commit 2023-11-13 14:33:28 +00:00

mirage-builder

Mirage Builder environment in Qubes OS.

Table of Contents

Description

Setup a builder qube for Mirage Unikernel named "mirage-builder". The tool necessary to build Mirage with docker or directly with Opam will also be installed.

Installation

Mirage Firewall commits and tags are not signed by individuals, but as they are done through the web interface, they have GitHub Web-Flow signature. This is the best verification we can get for Mirage Firewall. If you don't trust the hosting provider however, don't install this package.

  • Top
qubesctl top.enable mirage-builder
qubesctl --targets=tpl-mirage-builder,mirage-builder state.apply
qubesctl top.disable mirage-builder
  • State
qubesctl state.apply mirage-builder.create
qubesctl --skip-dom0 --targets=tpl-mirage-builder state.apply mirage-builder.install
qubesctl --skip-dom0 --targets=mirage-builder state.apply mirage-builder.configure

Usage

The qube mirage-builder is intended to build Mirage Unikernel. Consult upstream documentation on how to build qubes-mirage-firewall from source.

If you plan to build without docker, the hooks and completion scripts are already being sourced by your shell profile. Because of this, when calling opam-init, use it together with the option --no-setup:

opam init --no-setup