rocodes

We have sadly known about this for a while and even tried to suppress those warnings: https://github.com/freedomofpress/securedrop-client/commit/9bcd76a6561889da66b10d999fb0c47329ae8c91 Another good reason to move away from this approach and towards the modern...

Hey @deeplow, thanks for preparing this. My opinion (recapping from standup for the rest of the team) is a couple things: * I prefer to keep the dvm template free...

Yeah I'm with you, I would say A or B, (and if A, that we make a plan to do B and drop all the ppd driver stuff in a...

@deeplow: re printer detection via lpinfo: can you post the exact steps you are doing to configure the printer, either in a draft PR or a gist somewhere? I did...

> How would the yum-test and apt-test configs get applied to override the prod versions though? For the non repo related files (eg systemd presets, conf overrides) it's straightforward: if...

In advance of a conversation about this, another related issue about managing dev/staging/prod config: #1053 (relevant because for example we could have a pillar of (apt) repo config data, which...

Discussed today in meeting: * None of this (except the prod keyring package as already agreed upon) is a blocker or requirement for 1.1.0. * There will be slight changes...

Just reposting here a suggestion for looking ahead past the keyring work to continuing a clean/simple strategy. - [ ] (publish keyrings). Don't try to enforce any kind of requirements/constraints...

I looked into this. The correct thing to do is adjust the (empty, whonix-provided) file `/usr/local/etc/torrc.d/50_user.conf` so that it contains the line ```DisableNetwork 0```. That bypasses the anon connection wizard...

> Or maybe a systemd unit to create the file, to make it easy to connect w/ qubesdb/qubes services. So the file is already created by whonix, which is why...