Qubes-Whonix 14 TemplateVMs (4.0.1-20181101) for Qubes R4 -- Testers Wanted!

[nurmagoz]

Other issues:

• whonix-gw-appvm which are based on the old whonix 14, will not be able to be connect to the internet due to the same issue that i mentioned above. (so you need to delete every old gw-14 appvms and create new one based on the current testing whonix-14-gw appvms)

• previous whonixes , when you create new whonix-apppvm there was a service in the settings of the appvm called “meminfo-writer”. this one seems to be disappeared with the current testing builds.(i need to write it manually then it will pop-up then i press on sign to add it back)

• Old based vms on whonix-14 , will not save their data.true the whonix-ws-xxx.appvm which is based on the stable/old whonix will still in the qubes manager, but it will not keep containing the same data (emails,chat , texts …etc all will be erased).

Edit: only emails/mails + plugins (torbirdy+enigmail) with Thunderbird will be lost.

• Qubes Manager/Whonix Bug:

pressing on “Refresh application” inside whonix-ws-appvm which is taking its connection from whonix-gw-appvm NOT sys-whonix, it will ignore that and open sys-whonix EVEN though whonix-ws network isnt based on sys-whonix appvm.

Related:

cloned Whonix TemplateVM connects / upgrades through sys-whonix even if NetVM is set to a different Whonix-Gateway ProxyVM

if we clone whonix-ws/gw 14 template and we change the connection of appvm from sys-whonix to xxx-gw-appvm. the template will always open sys-whonix even if change the “Networking” to anther gw-appvm name. this is i think a problem of salt? but anyway its not good to connect all templates to one point by force. as sometimes u like to modify the appvm-gw to be with vpn or with i2p or …etc. this is cant be achieved atm.