Existing Ports of and Porting Whonix ™ to other Architectures

From Whonix

< Dev

Existing Ports of Whonix ™[edit]

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.



amd64 might imply AMD only. This is wrong.

amd64 means Intel and AMD.

For technical reasons, Debian both, Intel and AMD, is called amd64.

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.





Hardened Malloc[edit]

Hardened Memory Allocator




Check Tor SocksPort Reachability[edit]

On Whonix-Workstation ™. Test.

{{Curl_Plain}} ; echo $?

Should show.

<title>Tor is not an HTTP Proxy</title>
<h1>Tor is not an HTTP Proxy</h1>
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.
See <a href=""></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.-→

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

Check CPFP Reachability[edit]

On Whonix-Workstation ™. Test.


Should show.

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

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

Forum Discussion[edit] [archive]


Fosshost is sponsors Kicksecure ™ stage server Whonix old logo.png
Fosshost About Advertisements

Search engines: YaCy | Qwant | ecosia | MetaGer | peekier | Whonix ™ Wiki

Follow: 1024px-Telegram 2019 Logo.svg.png Iconfinder Apple Mail 2697658.png Twitter.png Facebook.png Rss.png Reddit.jpg 200px-Mastodon Logotype (Simple).svg.png

Support: 1024px-Telegram 2019 Logo.svg.png Discourse logo.png Matrix logo.svg.png

Donate: Donate Bank Wire Paypal Bitcoin accepted here Monero accepted here Contriute

Whonix donate bitcoin.png Monero donate Whonix.png United Federation of Planets 1000px.png

Twitter-share-button.png Facebook-share-button.png Telegram-share.png Iconfinder Apple Mail 2697658.png Reddit.jpg 200px-Mastodon Logotype (Simple).svg.png

Please help in testing new features and bug fixes in Whonix ™.

https link onion link Priority Support | Investors | Professional Support

Whonix | © ENCRYPTED SUPPORT LP | Heckert gnu.big.png Freedom Software / Osi standard logo 0.png Open Source (Why?)

The personal opinions of moderators or contributors to the Whonix ™ project do not represent the project as a whole.

By using our website, you acknowledge that you have read, understood and agreed to our Privacy Policy, Cookie Policy, Terms of Service, and E-Sign Consent.