I reopened this because KVM page (https://www.whonix.org/wiki/KVM#Arch_Linux) explicitly mentions Arch as a host OS.
If someone here is using Arch as well, maybe you guys can reproduce this after all. Also see my previous comment.

Many code enhancements were recently added by its author.

Alright. If you know how to automate / implement that... Using mediawiki or else... Would speed up implementation a ton.

it seems a rather odd reason to me since debian has literally done it this way for years. i understand that it would be a problem if the downloaded file name was always the same (for example, "tor-current.exe"). but, since the filenames always include the version number, there are multiple means of documenting for a user how to determine their version number before making support requests.

I requested such a feature myself once from Tor Project. They refused this because they said, when you ask users what version they are using, they will reply latest.

I'm using Arch.
All the software versions (libvirt, QEMU, virt-viewer, kernel) are deemed stable upstream (by their respective developers, not by Debian folks).

What distro are you using?

Yes.

Other imporvements in this thread such as functioning SMTP gateways are also part of this ticket:

God for the time being, if anyone wants to add more there is an outline of what procedures can be done, to add to.

Looks like nothing more to do here.

Since grsecurity is not a thing anymore, closing this as invalid.

I also noticed the file "~/.tb/first-boot-home-population.done" which suggests that whonix does something on first boot

To build a package with qubes-builder, you need to add Makefile.builder file with just one line: DEBIAN_BUILD_DIRS := debian. This will tell qubes-builder that given repository contains Debian package.
Alternatively, if that would be too much of a problem, it should be easy to add an option that do auto detection (probably just looks for debian directory).

I am slow to review this. Finally got to it. More feedback here:

I created a user documentation page explaining this feature and when to use it for users to understand.

Not only relevant for retroshare.

Sounds good!

Moved to xfce so past comment is irrelevant. Will test Zulu after moving to Buster and add if it works.

@Patrick Was this only relevant for Retroshare?

The concept was documented for operational use. Auto Guard de-duplication considered too complex to deploy and manual checking is enough.

Mixmaster is not present in Buster BTW

Looks like someone beat us to it:

Ready to close if happy.

Middle of the range solution. How does this sound? Confirmed it falls within the private address CIDR: