├── version ├── .gitignore ├── .qubesbuilder ├── etc └── salt │ └── minion.d │ └── qubes-infrastructure.conf ├── pillar └── build-infra │ ├── logs-kernel-repo.sls │ ├── logs.sls │ ├── logs-kernel.sls │ ├── init.top │ ├── build-vms.sls │ └── init.sls ├── .gitlab-ci.yml ├── Makefile.builder ├── .gitmodules ├── FORMULA ├── Makefile ├── rpm_spec └── qubes-infrastructure-dom0.spec.in ├── README.md └── LICENSE /version: -------------------------------------------------------------------------------- 1 | 4.2.4 2 | -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | pkgs/ 2 | -------------------------------------------------------------------------------- /.qubesbuilder: -------------------------------------------------------------------------------- 1 | host: 2 | rpm: 3 | build: 4 | - rpm_spec/qubes-infrastructure-dom0.spec 5 | -------------------------------------------------------------------------------- /etc/salt/minion.d/qubes-infrastructure.conf: -------------------------------------------------------------------------------- 1 | file_roots: 2 | base: 3 | - /srv/formulas/base/qubes-infrastructure 4 | -------------------------------------------------------------------------------- /pillar/build-infra/logs-kernel-repo.sls: -------------------------------------------------------------------------------- 1 | build-infra: 2 | build_report_repo: fepitre-bot/update-status-kernel 3 | build_issues_repo: fepitre-bot/build-issues-kernel 4 | logs_repo: fepitre-bot/logs-kernel -------------------------------------------------------------------------------- /.gitlab-ci.yml: -------------------------------------------------------------------------------- 1 | include: 2 | - project: 'QubesOS/qubes-continuous-integration' 3 | file: '/r4.2/gitlab-base.yml' 4 | - project: 'QubesOS/qubes-continuous-integration' 5 | file: '/r4.2/gitlab-host.yml' 6 | - project: 'QubesOS/qubes-continuous-integration' 7 | file: '/r4.3/gitlab-base.yml' 8 | - project: 'QubesOS/qubes-continuous-integration' 9 | file: '/r4.3/gitlab-host.yml' 10 | -------------------------------------------------------------------------------- /pillar/build-infra/logs.sls: -------------------------------------------------------------------------------- 1 | 2 | build-infra: 3 | # public gpg key associated to the one used to sign log commits 4 | # it allows to not rely on gpg key servers 5 | logs_repo_public_key: | 6 | -----BEGIN PGP PUBLIC KEY BLOCK----- 7 | ... 8 | -----END PGP PUBLIC KEY BLOCK----- 9 | # ssh key used to access github - needs to have write access to logs repository 10 | github_ssh_key: | 11 | -----BEGIN RSA PRIVATE KEY----- 12 | ... 13 | -----END RSA PRIVATE KEY----- 14 | -------------------------------------------------------------------------------- /pillar/build-infra/logs-kernel.sls: -------------------------------------------------------------------------------- 1 | 2 | build-infra: 3 | # public gpg key associated to the one used to sign log commits 4 | # it allows to not rely on gpg key servers 5 | logs_repo_public_key: | 6 | -----BEGIN PGP PUBLIC KEY BLOCK----- 7 | ... 8 | -----END PGP PUBLIC KEY BLOCK----- 9 | # ssh key used to access github - needs to have write access to logs repository 10 | github_ssh_key: | 11 | -----BEGIN RSA PRIVATE KEY----- 12 | ... 13 | -----END RSA PRIVATE KEY----- 14 | -------------------------------------------------------------------------------- /pillar/build-infra/init.top: -------------------------------------------------------------------------------- 1 | base: 2 | '*': 3 | - build-infra 4 | logs: 5 | - build-infra.logs 6 | build-fedora1: 7 | - build-infra.build-vms 8 | build-fedora2: 9 | - build-infra.build-vms 10 | build-centos1: 11 | - build-infra.build-vms 12 | build-debian1: 13 | - build-infra.build-vms 14 | logs-kernel: 15 | - build-infra.logs-kernel-repo 16 | - build-infra.logs-kernel 17 | build-kernel: 18 | - build-infra.logs-kernel-repo 19 | - build-infra.build-vms 20 | -------------------------------------------------------------------------------- /pillar/build-infra/build-vms.sls: -------------------------------------------------------------------------------- 1 | build-infra: 2 | github_api_key: place API key here for qubesos-bot account 3 | openqa_server: openqa.qubes-os.org 4 | openqa_key: 123456789 5 | openqa_secret: 123456789 6 | mirror_ssh_key: | 7 | -----BEGIN OPENSSH PRIVATE KEY----- 8 | ... 9 | -----END OPENSSH PRIVATE KEY----- 10 | # public GPG keys for allowing Qubes members to build packages/templates 11 | commands_public_keys: | 12 | -----BEGIN PGP PUBLIC KEY BLOCK----- 13 | ... 14 | -----END PGP PUBLIC KEY BLOCK----- 15 | -----BEGIN PGP PUBLIC KEY BLOCK----- 16 | ... 17 | -----END PGP PUBLIC KEY BLOCK----- 18 | -------------------------------------------------------------------------------- /Makefile.builder: -------------------------------------------------------------------------------- 1 | # vim: filetype=make 2 | 3 | ifndef LOADING_PLUGINS 4 | SOURCE_COPY_IN := mgmt-salt-copy-in 5 | ifeq ($(PACKAGE_SET),dom0) 6 | ifneq ($(filter $(DISTRIBUTION), debian qubuntu),) 7 | DEBIAN_BUILD_DIRS := $(call get-mgmt-debian-dir) 8 | else 9 | RPM_SPEC_FILES := $(call get-mgmt-rpm-spec) 10 | endif 11 | else ifeq ($(PACKAGE_SET),vm) 12 | ifneq ($(filter $(DISTRIBUTION), debian qubuntu),) 13 | DEBIAN_BUILD_DIRS := $(call get-mgmt-debian-dir) 14 | else 15 | RPM_SPEC_FILES := $(call get-mgmt-rpm-spec) 16 | endif 17 | endif 18 | endif 19 | 20 | -------------------------------------------------------------------------------- /.gitmodules: -------------------------------------------------------------------------------- 1 | [submodule "build-infra/qubes-builder"] 2 | path = build-infra/qubes-builder 3 | url = https://github.com/qubesos/qubes-builder 4 | [submodule "build-infra/qubes-builder-github"] 5 | path = build-infra/qubes-builder-github 6 | url = https://github.com/qubesos/qubes-builder-github 7 | [submodule "build-infra/qubes-builderv2"] 8 | path = build-infra/qubes-builderv2 9 | url = https://github.com/QubesOS/qubes-builderv2 10 | [submodule "build-infra/qubes-infrastructure-mirrors"] 11 | path = build-infra/qubes-infrastructure-mirrors 12 | url = https://github.com/qubesos/qubes-infrastructure-mirrors.git 13 | [submodule "build-infra/builderv2-github"] 14 | path = build-infra/qubes-builderv2-github 15 | url = https://github.com/QubesOS/qubes-builderv2-github 16 | -------------------------------------------------------------------------------- /FORMULA: -------------------------------------------------------------------------------- 1 | # vim: set syntax=yaml ts=2 sw=2 sts=2 et : 2 | 3 | package-name: qubes-mgmt-salt-dom0-qubes-infrastructure 4 | saltenv: base 5 | version: 4.2.4 6 | release: 1 7 | name: qubes-infrastructure 8 | top_level_dir: build-infra 9 | formula-files: build-infra LICENSE README.md 10 | pillar-files: pillar/build-infra 11 | formula_dir: $(MGMT_DEFAULT_FORMULA_DIR)/$(MGMT_SALTENV)/$(MGMT_NAME) 12 | pillar_dir: $(MGMT_DEFAULT_PILLAR_DIR)/$(MGMT_SALTENV)/$(MGMT_TOP_LEVEL_DIR) 13 | os: Qubes 14 | os_family: RedHat 15 | summary: Manage Qubes OS infrastructure VMs 16 | description: | 17 | Create VMs used to build and distribute Qubes OS packages 18 | 19 | pillar-tops: 20 | base: 21 | enable: 22 | - build-infra 23 | -------------------------------------------------------------------------------- /Makefile: -------------------------------------------------------------------------------- 1 | # The Qubes OS Project, http://www.qubes-os.org 2 | # 3 | # Copyright (C) 2017 Marek Marczykowski-Górecki 4 | # 5 | # 6 | # This program is free software; you can redistribute it and/or 7 | # modify it under the terms of the GNU General Public License 8 | # as published by the Free Software Foundation; either version 2 9 | # of the License, or (at your option) any later version. 10 | # 11 | # This program is distributed in the hope that it will be useful, 12 | # but WITHOUT ANY WARRANTY; without even the implied warranty of 13 | # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the 14 | # GNU General Public License for more details. 15 | # 16 | # You should have received a copy of the GNU General Public License 17 | # along with this program; if not, write to the Free Software 18 | # Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA. 19 | 20 | # This file is generated from FORMULA* by yaml-dumper in mgmt-salt builder plugin 21 | -include Makefile.vars 22 | 23 | # This file is copied in from mgmt-salt 24 | -include Makefile.install 25 | 26 | .PHONY: install-custom 27 | install-custom:: 28 | # Install /etc/salt/* and /srv/* 29 | cp -Tr etc $(DESTDIR)/etc 30 | 31 | get-sources: 32 | git submodule update --init --recursive 33 | 34 | # nothing to be done, because git submodules are referenced by exact commit id (hash) 35 | verify-sources: 36 | @true 37 | -------------------------------------------------------------------------------- /rpm_spec/qubes-infrastructure-dom0.spec.in: -------------------------------------------------------------------------------- 1 | Name: qubes-mgmt-salt-dom0-qubes-infrastructure 2 | Version: @VERSION@ 3 | Release: 1%{?dist} 4 | Summary: Manage Qubes OS infrastructure VMs 5 | 6 | Group: System administration tools 7 | License: GPL 2.0 8 | BuildArch: noarch 9 | URL: https://www.qubes-os.org/ 10 | Source: %{name}-%{version}.tar.gz 11 | BuildRequires: make 12 | Requires: qubes-mgmt-salt 13 | Requires: qubes-mgmt-salt-dom0 14 | 15 | # Turn off automatic python bytecompilation 16 | %undefine py_auto_byte_compile 17 | 18 | %description 19 | 20 | 21 | %prep 22 | %setup -q 23 | 24 | %build 25 | 26 | %install 27 | make install DESTDIR=%{buildroot} LIBDIR=%{_libdir} BINDIR=%{_bindir} SBINDIR=%{_sbindir} SYSCONFDIR=%{_sysconfdir} 28 | 29 | 30 | %files 31 | %defattr(-,root,root) 32 | %doc LICENSE README.md 33 | %attr(750, root, root) %dir /srv/formulas/base/qubes-infrastructure 34 | /srv/formulas/base/qubes-infrastructure/README.md 35 | /srv/formulas/base/qubes-infrastructure/LICENSE 36 | /srv/formulas/base/qubes-infrastructure/build-infra 37 | 38 | %attr(750, root, root) %dir /srv/pillar/base/build-infra 39 | %config(noreplace) /srv/pillar/base/build-infra/init.sls 40 | %config(noreplace) /srv/pillar/base/build-infra/logs.sls 41 | %config(noreplace) /srv/pillar/base/build-infra/logs-kernel.sls 42 | %config(noreplace) /srv/pillar/base/build-infra/logs-kernel-repo.sls 43 | %config(noreplace) /srv/pillar/base/build-infra/build-vms.sls 44 | %config(noreplace) /srv/pillar/base/build-infra/init.top 45 | 46 | %config(noreplace) /etc/salt/minion.d/qubes-infrastructure.conf 47 | 48 | %changelog 49 | @CHANGELOG@ 50 | -------------------------------------------------------------------------------- /pillar/build-infra/init.sls: -------------------------------------------------------------------------------- 1 | 2 | 3 | build-infra: 4 | # Default NetVMs and templates: 5 | # netvm: sys-net 6 | # logs-template: fedora-42-xfce 7 | # logs-netvm: sys-firewall 8 | # build-template: fedora-42-xfce 9 | # build-netvm: sys-whonix 10 | # keys-template: fedora-42-minimal 11 | 12 | # example list of build environments: 13 | build-envs: 14 | fedora1: 15 | builders-list: 16 | /home/user/builder-r4.2: 17 | release: 4.2 18 | config: 19 | - file: R4.2/qubes-os-r4.2-host.conf 20 | - repository: 21 | - baseurl: https://github.com/QubesOS-contrib/qubes- 22 | - component: contrib-configs 23 | - maintainers: 24 | - 9FA64B92F95E706BF28E2CA6484010B5CDC576E2 25 | /home/user/builder-r4.1: 26 | release: 4.1 27 | config: 28 | - file: R4.1/qubes-os-r4.1-dom0.conf 29 | - repository: 30 | - baseurl: https://github.com/QubesOS/qubes- 31 | - component: release-configs 32 | volume-size: 20GiB 33 | logs: logs 34 | fedora2: 35 | builderv2: True 36 | builders-list: 37 | /home/user/builder-r4.2: 38 | release: 4.2 39 | config: 40 | - file: R4.2/qubes-os-r4.2-dom0.yml 41 | - repository: 42 | - baseurl: https://github.com/QubesOS/qubes- 43 | - component: release-configs 44 | volume-size: 20GiB 45 | logs: logs 46 | # setup for building windows tools too 47 | windows: true 48 | kernel: 49 | builders-list: 50 | /home/user/builder-r4.1-kernel: 51 | keys: 52 | - 9FA64B92F95E706BF28E2CA6484010B5CDC576E2 53 | release: 4.1 54 | config: 55 | - file: qubes-kernel.conf 56 | - repository: 57 | - baseurl: https://github.com/fepitre/qubes- 58 | - component: linux-kernel-updater 59 | volume-size: 20GiB 60 | logs: logs-kernel 61 | 62 | # Above definitions of environments can be put in 63 | # separate pillar files. Just ensure to keep at least 64 | # the env names for init.top 65 | # build-envs: 66 | # fedora1: {} 67 | # fedora2: {} 68 | 69 | # list of remote hosts used to push packages 70 | remote-hosts: 71 | yum.qubes-os.org: 72 | ssh_user: user 73 | ssh_host_enc: ssh-rsa 74 | ssh_host_key: AAAAB3NzaC1yc2EAAAADAQABAAABAQCs7JxW6S2eWv44tS9aXKrk2roSk8FclU7vtdz/hnsThtc3A7VofkGHCaG0xzFjreUvI300/dYQ3P6vehx08S+gpyWC6ILB6S4P4sY+VVl8d9OFenRDFXd+spv9DKEufsZ8x0E7DpopHYWir+NCx5ohw0BDwoeH/VOjQfAEzWy1kRyX2hy9dtO8rM8ykEUrL6bB0SAUF09HuVFhPVnveaLZD13baZcd5uBuqg5+s+atCFVRyr+f9ffBQKW+rE9FEckMV7/RfHF8FHeVZ/wHy+HIUF35I9IiXOr76TbRUttgTXpPU19aAsP91f4ISL8w49cBUiSCd4vYO9wqOV9rmCZ/ 75 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | Qubes OS build infrastructure configuration 2 | =========================================== 3 | 4 | This repository contains part of Qubes OS infrastructure configuration. 5 | 6 | `build-infra` formula 7 | ---------------------- 8 | 9 | This formula provides setup for Qubes OS build machine. It can consists of 10 | multiple build environments, each of them have at least two VMs: 11 | 12 | - build-`ENV_NAME` 13 | - keys-`ENV_NAME` 14 | 15 | In addition to those, `logs` VM is created. Configuration allows: 16 | 17 | - build VM to upload build logs to `logs` VM 18 | - `logs` VM to unlock signing keys usage for appropriate keys VM 19 | - build VM access the keys VM 20 | 21 | Each build VM have access to the network through Whonix Gateway, so all 22 | 3rd-party sources are downloaded through Tor. 23 | 24 | Build environments list can be specified with `build-infra:build-envs` pillar. 25 | Example pillar is provided in `/srv/pillar/base/qubesos-infra/build-infra.sls`. 26 | 27 | ### Usage: 28 | 29 | 1. Enable this formula with: 30 | 31 | qubesctl top.enable build-infra 32 | qubesctl top.enable build-infra pillar=True 33 | 34 | 2. Apply the configuration: 35 | 36 | qubesctl --all state.highstate 37 | 38 | 3. Provision gpg signing keys into appropriate `keys-` VMs, setup qubes-builder 39 | in appropriate `build-` VMs. See below for detailed list. 40 | 41 | 42 | `build-infra.ssh-proxy` formula 43 | -------------------------------- 44 | 45 | Configure ssh in build VMs to bypass Whonix Gateway. The main reason here is 46 | performance. This shouldn't affect main goal of using Tor - making targeted 47 | attacks harder, for attacker controlling 3rd-party signing key. Ssh is used only to: 48 | - download our code from github (where it's authenticated using gpg) 49 | - upload binary packages to appropriate repositories 50 | 51 | Technically it's done by configuring ssh (`ProxyCommand` in 52 | `~/.ssh/config`) to use `local.ConnectSSH` service to `sys-net` (and pass 53 | destination hostname in service argument), instead of establishing TCP 54 | connection directly. `local.ConnectSSH` service is implemented as simple netcat. 55 | 56 | ### Usage: 57 | 58 | 1. Enable this formula: 59 | 60 | qubesctl top.enable build-infra.ssh-proxy 61 | 62 | 2. Apply the configuration: 63 | 64 | qubesctl --all state.highstate 65 | 66 | 67 | `build-infra.webhooks` formula 68 | -------------------------------- 69 | 70 | Configure a web server (Nginx) in `sys-net` to receive github webhooks. The web 71 | server receives `push event` at the location `/github-hooks/` with content 72 | type `application/json`. For triggering build from github, configure 73 | the payload URL to be `http://IPADDRESS/github-hooks/trigger-build` and for processing 74 | github comments, configure payload URL to be `http://IPADDRESS/github-hooks/process-comment`. 75 | 76 | ### Usage: 77 | 78 | 1. Enable this formula: 79 | 80 | qubesctl top.enable build-infra.webhooks 81 | 82 | 2. Apply the configuration: 83 | 84 | qubesctl --all state.highstate 85 | 86 | 87 | Detailed description of the infrastructure 88 | ========================================== 89 | 90 | Build infrastructure consists of several build environments. Each of them use 3 VMs: 91 | 92 | 1. Build VM (`build-*`), responsible for: 93 | - building the package with logging to `logs` VM in real time 94 | - sending build artifacts to Keys VM for signing (using split gpg) 95 | - uploading signed packages to repository 96 | - sending notifications to github (issue comments etc) 97 | 98 | 2. Keys VM (`keys-*`), responsible for: 99 | - keeping signing keys 100 | - signing packages, but only if `logs` VM acknowledged build log reception 101 | 102 | 3. Build VM (`logs-*`) VM (default `logs`), common for all their associated build environments, responsible for: 103 | - receiving build logs 104 | - sending them (in form of signed commits) to logs repositories 105 | - signaling appropriate Keys VM of successful logs reception and sending 106 | 107 | The above workflow and used qrexec services can be illustrated with the diagram below: 108 | 109 | 110 | .-----------. .----------. 111 | | build VM | | keys VM | 112 | | | 4. qubes.Gpg | | 113 | | |-------------------->| | 114 | | | | | 115 | | | | | 116 | | | '----------' 117 | '-----------' ^ 118 | | | 119 | |1. qubesbuilder.BuildLog | 120 | | | 121 | v | 122 | .---------------. 3. qubesbuilder.LogReceived| 123 | | logs VM |----------------------------' 124 | | | .-,( ),-. 125 | | | 2. push signed logs .-( )-. 126 | | |********************>( github ) 127 | | | '-( ).-' 128 | | | '-.( ).-' 129 | '---------------' 130 | 131 | The build process may be triggered manually (be calling appropriate `make` 132 | command in some of build VM), or in response to github notification. The later 133 | is achieved using 134 | [builder-github](https://github.com/QubesOS/qubes-builder-github), which 135 | provide webhooks and qrexec services to handle this process. It boils down to: 136 | 137 | 1. HTTP server in `sys-net` (nginx) receive HTTP POST request from github with 138 | information about an event in repository. It is handed to appropriate 139 | handler script from `github-webhooks` directory of `builder-github`. 140 | 2. Webhook handler extract essential data (for example repository name) and 141 | send it to all build VMs using `qubesbuilder.TriggerBuild` qrexec service. 142 | 3. Qrexec service in a build VM check if the named component exists in any of 143 | `qubes-builder` instance and call `scripts/auto-build` build script. This 144 | script check if anything new needs to be built - and if so, build it and 145 | upload to current-testing repository. This, among other things, report 146 | successful (or failed) build as an issue in appropriate repository. 147 | 148 | Very similar approach is used to move packages from `current-testing` to 149 | `current` repository: 150 | 151 | 1. HTTP server in `sys-net` (nginx) receive HTTP POST request from github with 152 | information about an comment on issue. It is handed to appropriate 153 | handler script from `github-webhooks` directory of `builder-github`. 154 | 2. Webhook handler extract commend body, check if it have any PGP-signed data 155 | (but do not verify it yet) and 156 | send it to all build VMs using `qubesbuilder.ProcessGithubCommand` qrexec service. 157 | 3. Qrexec service in a build VM check signature on the commend and if it's made 158 | by a trusted key, process the command. See documentation in 159 | [builder-github](https://github.com/QubesOS/qubes-builder-github) for 160 | details. 161 | 162 | 163 | 164 | .-,( ),-. .------------. 165 | .-( )-. HTTP POST | sys-net | 166 | ( github )****************>| | 167 | '-( ).-' | | 168 | '-.( ).-' '------------' 169 | ^ | 170 | * qubesbuilder.TriggerBuild 171 | github issue/comment qubesbuilder.ProcessGithubCommand 172 | * | 173 | * .----------. | 174 | ***********| build VM |<---------| 175 | * '----------' | 176 | * | 177 | * .----------. | 178 | ***********| build VM |<---------' 179 | * '----------' 180 | * 181 | packages 182 | * 183 | v 184 | .-,( ),-. 185 | .-( )-. 186 | ( repository ) 187 | '-( ).-' 188 | '-.( ).-' 189 | 190 | 191 | In addition to the above, build VM use Tor to download 3rd-party software 192 | (including build dependencies etc). This is to make _targeted_ attack as hard as 193 | possible even for someone having write access to 3rd-party source/binary 194 | repository (including access to a signing key). 195 | 196 | The above architecture is designed to make the build process as transparent as 197 | possible, while limiting damages of a compromised single build environment. 198 | Especially: 199 | 200 | - Build VM doesn't have direct access to a signing key, so it's impossible to leak 201 | it from there. 202 | - Packages signed with different keys are built in separate build environments. 203 | This means separate build environments for: 204 | - Fedora packages, 205 | - Debian packages, 206 | - Community-supported templates, 207 | - Contributed packages (TBD), 208 | - Build VM send build logs in real time - so even if the build environment 209 | would be compromised in the build process, it won't be able to erase the 210 | evidences from the build log. Note that after build VM is compromised, one 211 | can no longer trust further build logs, as those can be easily falsified. But 212 | those produced in the past (including the exact compromise incident) should 213 | remain immutable. 214 | - Build VM can request package signing only when sent a build log first. It's 215 | important to stress out here that Keys VM have no way to verify if the build 216 | log really corresponds to the binary received for signing. But since every 217 | build is logged in real time and it's a requirement for having package 218 | signed, logs will be available (publicly) and can be audited. 219 | 220 | 221 | Post installation steps 222 | ------------------------ 223 | 224 | Configuration tasks not included in this formula: 225 | 226 | 1. In each keys VM: 227 | 228 | - [ ] generate/import appropriate signing key 229 | 230 | 2. In each build VM: 231 | 232 | - [ ] generate/import ssh key used to upload packages 233 | 234 | - For any config `builder.conf` used, make sure to: 235 | 236 | - drop `NO_SIGN ?= 1` line 237 | - adjust `DISTS_VM` and `DIST_DOM0` if needed (must be set using `?=` operator) 238 | - adjust COMPONENTS, add builder-github there (must be set using `?=` operator, cannot use `+=`) 239 | - set `SIGN_KEY` to appropriate key id (the one in matching keys VM) 240 | - set `LINUX_REPO_BASEDIR` to a appropriate directory (pointing exact release version, like `$(SRC_DIR)/linux-yum/r4.0`) 241 | - include `$(HOME)/builder-github.conf` 242 | 243 | 3. In each logs VM: 244 | 245 | - [ ] generate/import ssh key, add it to each logs repositories (default QubesOS/build-logs) as deploy key with write access 246 | - [ ] import logs signing key 247 | 248 | 4. Make sure build VMs are large enough if not specified in `pillar` data. 249 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | GNU GENERAL PUBLIC LICENSE 2 | Version 2, June 1991 3 | 4 | Copyright (C) 1989, 1991 Free Software Foundation, Inc., 5 | 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA 6 | Everyone is permitted to copy and distribute verbatim copies 7 | of this license document, but changing it is not allowed. 8 | 9 | Preamble 10 | 11 | The licenses for most software are designed to take away your 12 | freedom to share and change it. By contrast, the GNU General Public 13 | License is intended to guarantee your freedom to share and change free 14 | software--to make sure the software is free for all its users. This 15 | General Public License applies to most of the Free Software 16 | Foundation's software and to any other program whose authors commit to 17 | using it. (Some other Free Software Foundation software is covered by 18 | the GNU Lesser General Public License instead.) You can apply it to 19 | your programs, too. 20 | 21 | When we speak of free software, we are referring to freedom, not 22 | price. Our General Public Licenses are designed to make sure that you 23 | have the freedom to distribute copies of free software (and charge for 24 | this service if you wish), that you receive source code or can get it 25 | if you want it, that you can change the software or use pieces of it 26 | in new free programs; and that you know you can do these things. 27 | 28 | To protect your rights, we need to make restrictions that forbid 29 | anyone to deny you these rights or to ask you to surrender the rights. 30 | These restrictions translate to certain responsibilities for you if you 31 | distribute copies of the software, or if you modify it. 32 | 33 | For example, if you distribute copies of such a program, whether 34 | gratis or for a fee, you must give the recipients all the rights that 35 | you have. You must make sure that they, too, receive or can get the 36 | source code. And you must show them these terms so they know their 37 | rights. 38 | 39 | We protect your rights with two steps: (1) copyright the software, and 40 | (2) offer you this license which gives you legal permission to copy, 41 | distribute and/or modify the software. 42 | 43 | Also, for each author's protection and ours, we want to make certain 44 | that everyone understands that there is no warranty for this free 45 | software. If the software is modified by someone else and passed on, we 46 | want its recipients to know that what they have is not the original, so 47 | that any problems introduced by others will not reflect on the original 48 | authors' reputations. 49 | 50 | Finally, any free program is threatened constantly by software 51 | patents. We wish to avoid the danger that redistributors of a free 52 | program will individually obtain patent licenses, in effect making the 53 | program proprietary. To prevent this, we have made it clear that any 54 | patent must be licensed for everyone's free use or not licensed at all. 55 | 56 | The precise terms and conditions for copying, distribution and 57 | modification follow. 58 | 59 | GNU GENERAL PUBLIC LICENSE 60 | TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 61 | 62 | 0. This License applies to any program or other work which contains 63 | a notice placed by the copyright holder saying it may be distributed 64 | under the terms of this General Public License. The "Program", below, 65 | refers to any such program or work, and a "work based on the Program" 66 | means either the Program or any derivative work under copyright law: 67 | that is to say, a work containing the Program or a portion of it, 68 | either verbatim or with modifications and/or translated into another 69 | language. (Hereinafter, translation is included without limitation in 70 | the term "modification".) Each licensee is addressed as "you". 71 | 72 | Activities other than copying, distribution and modification are not 73 | covered by this License; they are outside its scope. The act of 74 | running the Program is not restricted, and the output from the Program 75 | is covered only if its contents constitute a work based on the 76 | Program (independent of having been made by running the Program). 77 | Whether that is true depends on what the Program does. 78 | 79 | 1. You may copy and distribute verbatim copies of the Program's 80 | source code as you receive it, in any medium, provided that you 81 | conspicuously and appropriately publish on each copy an appropriate 82 | copyright notice and disclaimer of warranty; keep intact all the 83 | notices that refer to this License and to the absence of any warranty; 84 | and give any other recipients of the Program a copy of this License 85 | along with the Program. 86 | 87 | You may charge a fee for the physical act of transferring a copy, and 88 | you may at your option offer warranty protection in exchange for a fee. 89 | 90 | 2. You may modify your copy or copies of the Program or any portion 91 | of it, thus forming a work based on the Program, and copy and 92 | distribute such modifications or work under the terms of Section 1 93 | above, provided that you also meet all of these conditions: 94 | 95 | a) You must cause the modified files to carry prominent notices 96 | stating that you changed the files and the date of any change. 97 | 98 | b) You must cause any work that you distribute or publish, that in 99 | whole or in part contains or is derived from the Program or any 100 | part thereof, to be licensed as a whole at no charge to all third 101 | parties under the terms of this License. 102 | 103 | c) If the modified program normally reads commands interactively 104 | when run, you must cause it, when started running for such 105 | interactive use in the most ordinary way, to print or display an 106 | announcement including an appropriate copyright notice and a 107 | notice that there is no warranty (or else, saying that you provide 108 | a warranty) and that users may redistribute the program under 109 | these conditions, and telling the user how to view a copy of this 110 | License. (Exception: if the Program itself is interactive but 111 | does not normally print such an announcement, your work based on 112 | the Program is not required to print an announcement.) 113 | 114 | These requirements apply to the modified work as a whole. If 115 | identifiable sections of that work are not derived from the Program, 116 | and can be reasonably considered independent and separate works in 117 | themselves, then this License, and its terms, do not apply to those 118 | sections when you distribute them as separate works. But when you 119 | distribute the same sections as part of a whole which is a work based 120 | on the Program, the distribution of the whole must be on the terms of 121 | this License, whose permissions for other licensees extend to the 122 | entire whole, and thus to each and every part regardless of who wrote it. 123 | 124 | Thus, it is not the intent of this section to claim rights or contest 125 | your rights to work written entirely by you; rather, the intent is to 126 | exercise the right to control the distribution of derivative or 127 | collective works based on the Program. 128 | 129 | In addition, mere aggregation of another work not based on the Program 130 | with the Program (or with a work based on the Program) on a volume of 131 | a storage or distribution medium does not bring the other work under 132 | the scope of this License. 133 | 134 | 3. You may copy and distribute the Program (or a work based on it, 135 | under Section 2) in object code or executable form under the terms of 136 | Sections 1 and 2 above provided that you also do one of the following: 137 | 138 | a) Accompany it with the complete corresponding machine-readable 139 | source code, which must be distributed under the terms of Sections 140 | 1 and 2 above on a medium customarily used for software interchange; or, 141 | 142 | b) Accompany it with a written offer, valid for at least three 143 | years, to give any third party, for a charge no more than your 144 | cost of physically performing source distribution, a complete 145 | machine-readable copy of the corresponding source code, to be 146 | distributed under the terms of Sections 1 and 2 above on a medium 147 | customarily used for software interchange; or, 148 | 149 | c) Accompany it with the information you received as to the offer 150 | to distribute corresponding source code. (This alternative is 151 | allowed only for noncommercial distribution and only if you 152 | received the program in object code or executable form with such 153 | an offer, in accord with Subsection b above.) 154 | 155 | The source code for a work means the preferred form of the work for 156 | making modifications to it. For an executable work, complete source 157 | code means all the source code for all modules it contains, plus any 158 | associated interface definition files, plus the scripts used to 159 | control compilation and installation of the executable. However, as a 160 | special exception, the source code distributed need not include 161 | anything that is normally distributed (in either source or binary 162 | form) with the major components (compiler, kernel, and so on) of the 163 | operating system on which the executable runs, unless that component 164 | itself accompanies the executable. 165 | 166 | If distribution of executable or object code is made by offering 167 | access to copy from a designated place, then offering equivalent 168 | access to copy the source code from the same place counts as 169 | distribution of the source code, even though third parties are not 170 | compelled to copy the source along with the object code. 171 | 172 | 4. You may not copy, modify, sublicense, or distribute the Program 173 | except as expressly provided under this License. Any attempt 174 | otherwise to copy, modify, sublicense or distribute the Program is 175 | void, and will automatically terminate your rights under this License. 176 | However, parties who have received copies, or rights, from you under 177 | this License will not have their licenses terminated so long as such 178 | parties remain in full compliance. 179 | 180 | 5. You are not required to accept this License, since you have not 181 | signed it. However, nothing else grants you permission to modify or 182 | distribute the Program or its derivative works. These actions are 183 | prohibited by law if you do not accept this License. Therefore, by 184 | modifying or distributing the Program (or any work based on the 185 | Program), you indicate your acceptance of this License to do so, and 186 | all its terms and conditions for copying, distributing or modifying 187 | the Program or works based on it. 188 | 189 | 6. Each time you redistribute the Program (or any work based on the 190 | Program), the recipient automatically receives a license from the 191 | original licensor to copy, distribute or modify the Program subject to 192 | these terms and conditions. You may not impose any further 193 | restrictions on the recipients' exercise of the rights granted herein. 194 | You are not responsible for enforcing compliance by third parties to 195 | this License. 196 | 197 | 7. If, as a consequence of a court judgment or allegation of patent 198 | infringement or for any other reason (not limited to patent issues), 199 | conditions are imposed on you (whether by court order, agreement or 200 | otherwise) that contradict the conditions of this License, they do not 201 | excuse you from the conditions of this License. If you cannot 202 | distribute so as to satisfy simultaneously your obligations under this 203 | License and any other pertinent obligations, then as a consequence you 204 | may not distribute the Program at all. For example, if a patent 205 | license would not permit royalty-free redistribution of the Program by 206 | all those who receive copies directly or indirectly through you, then 207 | the only way you could satisfy both it and this License would be to 208 | refrain entirely from distribution of the Program. 209 | 210 | If any portion of this section is held invalid or unenforceable under 211 | any particular circumstance, the balance of the section is intended to 212 | apply and the section as a whole is intended to apply in other 213 | circumstances. 214 | 215 | It is not the purpose of this section to induce you to infringe any 216 | patents or other property right claims or to contest validity of any 217 | such claims; this section has the sole purpose of protecting the 218 | integrity of the free software distribution system, which is 219 | implemented by public license practices. Many people have made 220 | generous contributions to the wide range of software distributed 221 | through that system in reliance on consistent application of that 222 | system; it is up to the author/donor to decide if he or she is willing 223 | to distribute software through any other system and a licensee cannot 224 | impose that choice. 225 | 226 | This section is intended to make thoroughly clear what is believed to 227 | be a consequence of the rest of this License. 228 | 229 | 8. If the distribution and/or use of the Program is restricted in 230 | certain countries either by patents or by copyrighted interfaces, the 231 | original copyright holder who places the Program under this License 232 | may add an explicit geographical distribution limitation excluding 233 | those countries, so that distribution is permitted only in or among 234 | countries not thus excluded. In such case, this License incorporates 235 | the limitation as if written in the body of this License. 236 | 237 | 9. The Free Software Foundation may publish revised and/or new versions 238 | of the General Public License from time to time. Such new versions will 239 | be similar in spirit to the present version, but may differ in detail to 240 | address new problems or concerns. 241 | 242 | Each version is given a distinguishing version number. If the Program 243 | specifies a version number of this License which applies to it and "any 244 | later version", you have the option of following the terms and conditions 245 | either of that version or of any later version published by the Free 246 | Software Foundation. If the Program does not specify a version number of 247 | this License, you may choose any version ever published by the Free Software 248 | Foundation. 249 | 250 | 10. If you wish to incorporate parts of the Program into other free 251 | programs whose distribution conditions are different, write to the author 252 | to ask for permission. For software which is copyrighted by the Free 253 | Software Foundation, write to the Free Software Foundation; we sometimes 254 | make exceptions for this. Our decision will be guided by the two goals 255 | of preserving the free status of all derivatives of our free software and 256 | of promoting the sharing and reuse of software generally. 257 | 258 | NO WARRANTY 259 | 260 | 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY 261 | FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN 262 | OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES 263 | PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED 264 | OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF 265 | MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS 266 | TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE 267 | PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, 268 | REPAIR OR CORRECTION. 269 | 270 | 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING 271 | WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR 272 | REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, 273 | INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING 274 | OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED 275 | TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY 276 | YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER 277 | PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE 278 | POSSIBILITY OF SUCH DAMAGES. 279 | 280 | END OF TERMS AND CONDITIONS 281 | 282 | How to Apply These Terms to Your New Programs 283 | 284 | If you develop a new program, and you want it to be of the greatest 285 | possible use to the public, the best way to achieve this is to make it 286 | free software which everyone can redistribute and change under these terms. 287 | 288 | To do so, attach the following notices to the program. It is safest 289 | to attach them to the start of each source file to most effectively 290 | convey the exclusion of warranty; and each file should have at least 291 | the "copyright" line and a pointer to where the full notice is found. 292 | 293 | 294 | Copyright (C) 295 | 296 | This program is free software; you can redistribute it and/or modify 297 | it under the terms of the GNU General Public License as published by 298 | the Free Software Foundation; either version 2 of the License, or 299 | (at your option) any later version. 300 | 301 | This program is distributed in the hope that it will be useful, 302 | but WITHOUT ANY WARRANTY; without even the implied warranty of 303 | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the 304 | GNU General Public License for more details. 305 | 306 | You should have received a copy of the GNU General Public License along 307 | with this program; if not, write to the Free Software Foundation, Inc., 308 | 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA. 309 | 310 | Also add information on how to contact you by electronic and paper mail. 311 | 312 | If the program is interactive, make it output a short notice like this 313 | when it starts in an interactive mode: 314 | 315 | Gnomovision version 69, Copyright (C) year name of author 316 | Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. 317 | This is free software, and you are welcome to redistribute it 318 | under certain conditions; type `show c' for details. 319 | 320 | The hypothetical commands `show w' and `show c' should show the appropriate 321 | parts of the General Public License. Of course, the commands you use may 322 | be called something other than `show w' and `show c'; they could even be 323 | mouse-clicks or menu items--whatever suits your program. 324 | 325 | You should also get your employer (if you work as a programmer) or your 326 | school, if any, to sign a "copyright disclaimer" for the program, if 327 | necessary. Here is a sample; alter the names: 328 | 329 | Yoyodyne, Inc., hereby disclaims all copyright interest in the program 330 | `Gnomovision' (which makes passes at compilers) written by James Hacker. 331 | 332 | , 1 April 1989 333 | Ty Coon, President of Vice 334 | 335 | This General Public License does not permit incorporating your program into 336 | proprietary programs. If your program is a subroutine library, you may 337 | consider it more useful to permit linking proprietary applications with the 338 | library. If this is what you want to do, use the GNU Lesser General 339 | Public License instead of this License. 340 | --------------------------------------------------------------------------------