@Patrick Let’s choose a name for the project which will determine what the disk images are called in the Template XML.
I plan on letting it use the “default” NAT network unless you have a strong reason for it to use Whonix-External
@Patrick Let’s choose a name for the project which will determine what the disk images are called in the Template XML.
I plan on letting it use the “default” NAT network unless you have a strong reason for it to use Whonix-External
HulaHoop via Whonix Forum:
@Patrick Let’s choose a name for the project which will determine what the disk images are called in the Template XML.
For now hardened debian. Matching file name to fix that build bug.
Renaming can’t be accelerated. Still undecided.
I plan on letting it use the “default” NAT network unless you have a strong reason for it to use Whonix-External
Sounds ok. Hardened debian is supposed to be totally independent from
Whonix (except being developed here which is unavoidable).
Build script for creating Kicksecure KVM images is almost ready.
https://github.com/Whonix/whonix-libvirt/blob/master/usr/share/whonix-libvirt/xml/Kicksecure.xml looks good as is?
Does Kicksecure require a network XML file similar to
?
If it is required, could you please add it to https://github.com/Whonix/whonix-libvirt/tree/master/usr/share/whonix-libvirt/xml?
Yes
Nope we are not using an anon GW.
Not needed here anyhow, but my github account access is completely broken because of verification email issues.