I didn’t want to make a new thread but could you please create the Whonix ™ for macOS: Download and Installation page? I am happy to assist macOS users to the best of my ability and will start updating the macOS wiki as issues arise.
I’ve been working on Qubes/Reinstall manual method
The advantage of this method is, that it also works with non-Fedora based Qubes dom0 UpdateVMs, i.e. also with Debian based Qubes dom0 UpdateVMs.
Since automated method can use a torified UpdateVM should we have a manual method? Everything is covered in automated method section - Salt, DVM template, uninstall templates etc. Its a lot simpler IMO. Less chance of mistakes.
Maybe I’m missing something. Maybe more advanced users with prefer manual?
If legally possible, I guess so…
Could you remove please Copyright: and License?
I don’t think Apple or Oracle have any copyright on that page just for mentioning them. Claiming they have copyright where they didn’t invent anything may even be illegal.
For most pages Whonix copyright / licensing is already sorted in the page footer.
Unless otherwise noted, the content of this page is copyrighted and licensed under the same Libre Software license as Whonix itself. (Why?)
The format of the macOS wiki was based on the Whonix Computer Security Introduction wiki page
I am not sure headlines are enough creativity copyright wise to be protected by copyright. The Computer Security Education - Whonix says Whonix Computer Security Education wiki page Copyright (C) Amnesia <amnesia at boum dot org> but that page was rewritten / remixed so many times it’s hard to see what contents there still are by (C) Amnesia.
There’s a saying. Who writes, sticks. Meaning the once who starts writing something will always have a huge influence in the end result even if everyone else is invited to make edits. Sometimes not good.
When we write documentation based on upstream such as Redirecting… we should have that in mind and not necessarily copy non-ideal descriptions such as Automated Reinstallation Method and Manual Reinstallation Method. We don’t necessarily need both.
have sworn --action=reinstall works only with Fedora based UpdateVM.
(But even if that was the case, that UpdateVM could use sys-whonix as its NetVM.)
Even if they did, as I grow older I stop trying make everyone happy. Someone, somewhere, will always find a reason to complain. To turn it around, having these extra instructions would actually blow up the page size and make it look more complicated, therefore offend laymen users. So either way not everyone will be happy. So let’s rather do one thing and do it well.
There is my mistake. I was thinking reinstall because template is broken, misconfigured, compromised. Not upgrade to the latest template (point release etc.) At the beginning I was having a lot of trouble writing the page because I was trying to copy, use same format, terminology as Qubes reinstall page. For the most part we write Whonix documentation a little differently. It made for a lot of confusion.
--action=reinstall works with torified UpdateVM
But it looks like:
--action=upgradeonly works with a Fedora base UpdateVM.
Including upgrade-to and downgrade
This is why Qubes has manual reinstall, which is really, uninstall the target template, then install newest template. We already have an Qubes Uninstall and Qubes Install wiki page. I should have realized that.
About --action=upgrade. You want short instruction to set a fedora based UpdateVM and use sys-whonix as NetVM for UpdateVM? Wouldn’t see why there would be an issue.
I’d also like to test --action=upgrade using torified UpdateVM to see if it works. Maybe? All my templates are latest point release. Might have to wait until next point release to test or try debian-8 upgrade-to debian-9.