Existing Ports of Whonix ™[edit]

Whonix ™ reported ^[archive] to be running on POWER9 (OpenPOWER ^[archive]), Raptor ^[archive] Talos II ^[archive] using distro-morphing.
Whonix for arm64 / Raspberry Pi ( RPi ) ^[archive] (wiki)
Whonix on Mac M1 (ARM based) ^[archive]

Existing Ports of Kicksecure ™[edit]

ppc64el Kicksecure ™ functional, created using distro-morphing on a test server for Whonix ™ developer Patrick.
Distro-morphing should generate viable images for KVM on arm64.

Packages[edit]

NOTE[edit]

amd64 might imply AMD only. This is wrong.

amd64 means Intel and AMD.

For technical reasons, in Debian (and in many other Linux / Freedom Software related places) both, Intel and AMD, is called amd64. This is common knowledge without controversy among technical people, in doubt see Wikipedia X86-64 ^[archive].

Porting Simplicity[edit]

To simplify ports to other architectures, all of the following packages are optional dependencies. These packages have very useful functionality however to simplify bootstrapping a port of Whonix ™ for a quick motivational milestone to reach of Whonix ™ building and booting, all architecture specific packages are optional dependencies by design in Whonix ™.

Therefore porters do not need to worry about any of the following packages during original porting work.

Most of Whonix ™ packages and all essential packages are architecture independent.

To simplify ports, Whonix ™ repository at time of writing supports the following architectures. ^[1]

amd64 arm64 armel armhf hurd-i386 hurd-amd64 i386 kfreebsd-amd64 kfreebsd-i386 mips mipsel powerpc ppc64 ppc64el s390x sparc source

This might be useful for distro-morphing.

Distro-morphing might be the easiest way to create a proof of concept port of Whonix ™. Following the spirit of Free Support Principle, first experimenting with Debian (which Whonix ™ is based on) first might be helpful.

A production quality, redistributable port of Whonix ™ however should be created using Whonix ™ build script instead of distro-morphing.

bindp[edit]

maintained by third party: yes
compiled: yes
no upstream version number
documentation: none
upstream: https://github.com/yongboy/bindp ^[archive]
package source code: https://github.com/Whonix/bindp ^[archive]
kernel module: no

lkrg[edit]

maintained by third party: yes
compiled: yes
version number by upstream: yes
upstream architecture support: amd64 only
documentation: Linux Kernel Runtime Guard (LKRG)
upstream: https://www.openwall.com/lkrg/ ^[archive]
Debian package source code: https://github.com/Whonix/lkrg ^[archive]
kernel module: yes
LKRG Development Discussion ^[archive]

kloak[edit]

maintained by third party: yes
compiled: yes
version number by upstream: yes
architecture support: ?
- https://github.com/vmonaco/kloak/issues/24 ^[archive]
- https://github.com/vmonaco/kloak/issues/25 ^[archive]
documentation: kloak
upstream: https://github.com/vmonaco/kloak ^[archive]
Debian package source code: https://github.com/Whonix/kloak ^[archive]
kernel module: no
Kloak Forum Discussion ^[archive]

corridor[edit]

maintained by third party: yes
compiled: no
version number by upstream: yes
upstream architecture support: any
- bash scripts
documentation: Corridor
upstream: https://github.com/rustybird/corridor ^[archive]
Debian pacakge source code: https://github.com/Whonix/corridor ^[archive]
kernel module: no
corridor Development Discussion ^[archive]

Hardened Malloc[edit]

Hardened Memory Allocator

maintained by third party: yes
compiled: yes
version number by upstream: yes
upstream architecture support: amd64 only
documentation: Hardened Malloc
upstream: https://github.com/GrapheneOS/hardened_malloc ^[archive]
Debian package source code: https://github.com/Whonix/hardened_malloc ^[archive]
kernel module: no
Hardened Malloc Development Discussion ^[archive]

tb-updater[edit]

maintained by third party: no
compiled: no
version number by upstream: no
architecture support: i386 and amd64
- For the Linux platform The Tor Project is only providing i386 and amd64 downloads. See https://dist.torproject.org/torbrowser/ ^[archive].
Debian package source code: https://github.com/Whonix/tb-updater ^[archive]
kernel module: no

tirdad[edit]

maintained by third party: yes
compiled: yes
version number by upstream: upstream does not (yet) provide version numbers
architecture support: amd64 only
documentation: TODO
upstream: https://github.com/0xsirus/tirdad ^[archive]
Debian package source code: https://github.com/Whonix/tirdad ^[archive]
kernel module: yes
tirdad Development Discussion ^[archive]

binaries-freedom[edit]

Currently not in use.

tor[edit]

Architectures amd64, i386 and arm64 are using the deb.torproject.org tor package ^[archive]. A newer version. The latest stable version provided by The Tor Project for the stable release of Debian. Why? See Dev/Tor and https://forums.whonix.org/t/tor-package-urgently-needs-update-to-v0-4-6-8-due-to-tor-browser-11-stable-fingerprintability/12762 ^[archive].
Architectures other than amd64, i386 and arm64 are using the packages.debian.org tor package ^[archive]. An older version. The frozen stable version provided by Debian for Debian stable. This has a disadvantage: https://forums.whonix.org/t/tor-package-urgently-needs-update-to-v0-4-6-8-due-to-tor-browser-11-stable-fingerprintability/12762 ^[archive]
package maintained by third party: yes
compiled during package build process: no
contains binaries: yes
version number by upstream: yes

Check Tor SocksPort Reachability[edit]

On Whonix-Workstation ™. Test.

{{Curl_Plain}} 10.152.152.10:9100 ; echo $?

Should show.

<html>
<head>
<title>Tor is not an HTTP Proxy</title>
</head>
<body>
<h1>Tor is not an HTTP Proxy</h1>
<p>
It appears you have configured your web browser to use Tor as an HTTP proxy.
This is not correct: Tor is a SOCKS proxy, not an HTTP proxy.
Please configure your client accordingly.
</p>
<p>
See <a href="https://www.torproject.org/documentation.html">https://www.torproject.org/documentation.html</a> for more information.
<!-- Plus this comment, to make the body response more than 512 bytes, so      IE will be willing to display it. Comment comment comment comment      comment comment comment comment comment comment comment comment.-→
</p>
</body>
</html>
0

Otherwise, it would be a grave error (Tor SocksPort not reachable).

Check CPFP Reachability[edit]

On Whonix-Workstation ™. Test.

{{Curl_Plain}} 10.152.152.10:9052

Should show.

510 Prohibited command "GET / HTTP/1.1"
510 Prohibited command "User-Agent: curl/7.26.0"
510 Prohibited command "Host: 10.152.152.10:9052"
510 Prohibited command "Accept: */*"
510 Unrecognized command ""

Otherwise, it would be a grave error (CPFP not reachable).