Aug 19 2015
Aug 14 2015
No longer using taksel. Building Whonix templates now with flavor minimal and no-recommends to get better control of the installed packages. Therefore also no more build error.
Aug 7 2015
Aug 6 2015
I think those are two totally unrelated issues:
- Build failure
- Usage of tasksel (and more generally - default package list for Qubes Debian template) in Whonix template build
Jul 7 2015
Jun 26 2015
For the record, slightly off-topic.
Qubes Q3 RC1, Whonix 10.
Jun 15 2015
Alright. That answers my question. Thanks!
Qubes VMs (currently) does not use grub at all - Xen loads kernel
directly from dom0 filesystem (yes, VM have no influence on kernel
binary and parameters).
So, those files will not be used at all.
Jun 11 2015
Jun 10 2015
Jun 7 2015
Jun 6 2015
Jun 5 2015
For the record, flushing all rules and defaulting to ACCEPT makes obfsproxy work.
Jun 4 2015
This seems to have gotten lost in the backlog.
Qubes fix - https://phabricator.whonix.org/T339:
I tried to use a systemd drop in snippet but it did not work for ifup@.service.
I currently have it tied into the GATEWAY_IPv4_DROP_INVALID_INCOMING_PACKAGES_POST_HOOK hook.
Jun 3 2015
Don't work around this. Try to view this from Whonix perspective where you're upstream yourself. Where upstream can make any changes required to make this work. No need to see qubes-whonix as a fork that needs to work around things. We modify the whonix-(gw|ws)-firewall packages so those are also well suited for Qubes-Whonix.
Jun 1 2015
Please review and merge:
May 31 2015
Joanna wants the disclaimer skipped in qubes-whonix. Always.
Currently Setup is run differently for the Template vs an AppVM.