Voice over IP (VoIP)

Whonix ®

Download

Windows Linux Mac VirtualBox KVM Qubes USB ISO (coming soon) More options Source Code

About

Overview Features Whonix vs VPNs Why Open Source? Project Activities Contributors Mission & Vision

Docs

Documentation FAQ Troubleshooting

Community

Forums Contribute

Support

Self Support First Policy Search Engines, Docs and AI Support (Limited) Reporting Bugs Contact (Restricted)

Tools Upload file Special pages Recent changes Print Version Page meta What links here Related changes Page information

Page Read Edit History Move Protection Unwatch Watch Delete Purge

User Preferences Watchlist Contributions Logout Create account Login

Donate

Anonymous Voice over IP (VoIP). Encrypted, anonymous phone calls using the Tor Anonymity Network.

Introduction

Voice over IP (VoIP) is:

...a technology that allows you to make voice calls using a broadband Internet connection instead of a regular (or analog) phone line. ... VoIP services convert your voice into a digital signal that travels over the Internet. If you are calling a regular phone number, the signal is converted to a regular telephone signal before it reaches the destination. VoIP can allow you to make a call directly from a computer, a special VoIP phone, or a traditional phone connected to a special adapter.

VoIP software is complex and has a large attack surface. Several threat classes have been identified in the literature: social threats; eavesdropping, interception and modification of session contents; denial of service attacks; unauthorized access to VoIP equipment; and a sudden interruption of services.

Anonymizing VoIP is somewhat difficult, but still possible. It is easy to hide the IP address with Whonix, but the voice recognition component and slow Tor network speed (latency) are definite obstacles. Depending on your threat model, pseudonymous use of VoIP might be appropriate; this involves hidden voice communications that take place with known contacts. Consider the factors in the table below before deciding to use VoIP in Whonix.

Anonymity Factors

Table: Factors affecting VoIP Anonymity

VoIP Domain	Description	IP Anonymity	Full Anonymity
Tor + VoIP + Known Participants	If two or more people use a VoIP application in combination with Tor, it is possible to hide the act of communication from the ISP, government, Tor exit relays, man-in-the-middle attackers and so on. While the communication and IP addresses of each party remain hidden, this arrangement is not anonymous because the participants know each other.	Yes	No
Tor + VoIP + Unknown Participants	It is discouraged to use VoIP with anonymous parties in forums or other environments. The anonymous recipient of communications is a 'known unknown' -- it is impossible to confirm who you are talking to. The voiceprint might be correlated with your real identity later on, unless a voice scrambler or artificial voice is utilized (which is impractical in most circumstances).	Yes	No
Tor + VoIP + Artificial Voice	It is possible to type and let an artificial voice speak instead of using natural speech. This technique could work (similar to anonymous videos), but there are limited benefits compared to encrypted email, other than the real-time nature of the communication.	Yes	Maybe
Whistleblowing: Tor + VoIP	Whistleblowers cannot safely use their own voice if utilizing VoIP. Voice data is recorded and voice recognition works extremely well; see footnote. Almost everybody has had multiple non-anonymous phone calls in their lifetime, which provides a solid baseline for later correlation of 'anonymous' and non-anonymous identities. While commercial digital voice scramblers are available on the market, their effectiveness is a whole new field of research which is outside of the scope of Whonix.	Yes	With scrambler: Maybe

Voice Recognition

It is safe to assume that everyone has had an unencrypted phone call during their lifetime and that one of them has been recorded. Voiceprints allow a person to be identified from the specific characteristics (acoustics) of their voice and it is a useful biometric marker. This means personal and unique voiceprints can be used to link non-anonymous and "anonymous" voice samples; a process called voice recognition.

Software and Configuration

Some fully-functioned and reliable Libre VoIP software is already available, such as Linphone and Jitsi. Unfortunately it is not possible to communicate directly over Tor using a VoIP server, because all session initiation protocol (SIP)-based clients use UDP and Tor developers closed the related support ticket years ago.

The best workaround for SIP clients at present is to Tunnel UDP over Tor. The main downside of this method is that phone calls over Tor are slower and less convenient compared to ordinary networks. The reason is even when UDP packets are tunneled over Tor, the restrictions of the underlying TCP protocol still apply. To account for delays, push-to-talk is a reliable communication method in this configuration -- it has similarities to using a walkie-talkie. The Guardian Project recommends that 'prowords' (procedure words) such as "Roger" are used to acknowledge the end of transmission (speech, sentence).

When configuring the chosen software, it is safer to delegate encryption to Tor by utilizing onion services for both the caller and receiver. If that is not possible, then only use VoIP clients which support end-to-end encryption protocols like SRTP or ZRTP. This recommendation comes with warnings:

• Never use a Variable Bit Rate (VBR) codec because ZRTP cannot protect it.
  • If this advice is ignored, pauses in conversation will produce fingerprints in the encrypted stream that allow adversaries to infer what words are being said.
• Authentication strings must be compared with the other party during the initial call. If the strings do not match then this signals an active man-in-the-middle attack is underway and the call should be terminated.

Servers and Privacy

Even with end-to-end encryption, VoIP servers servers can log call signalling metadata. This is not a major threat if:

1. VoIP IDs are anonymously registered (no personal data is required for signing up).
2. All parties only and always connect over Tor and have never used (or will use) accounts over clearnet.
3. All calls are encrypted end-to-end.
4. No communications occur with anonymous strangers.

In this case it is unlikely a malicious server could cause much harm from logging or other actions.

Other than the factors outlined in this introduction section, no additional anonymity or security problems have been identified for VoIP. That said, this configuration is less tested in Whonix so the performance and voice quality could be quite variable. If this activity is necessary, then it is recommended to test the performance of VoIP software for yourself and to provide feedback about the experience.

Tox

Tox looks like a promising solution for secure, encrypted communications. The official client implementation is based on the TokTok protocol library, which is very feature-rich and has a variety of functions besides VoIP. By default, Tox does not attempt to cloak your IP address from authorized contacts. However, Tox is the only Tor compatible VoIP solution we know of, allowing communication with others even if they are not anonymous. Desktop versions are available for every major OS, however mobile support is lacking.

To learn more, refer to this entry.

Signal

Signal Logo

There is a user report of Signal working between one instance running over Tor and the other in the clear.

Notes:

• Signal is not in packages.debian.org. Only third party (signal APT repository).
• Signal Desktop requires a Phone Number Validation. "There are plans to give users more freedom by letting them use emails. Workarounds to register a phone no. anonymously may be possible, but not straight forward." - Source?

See also: Signal

Mumble

Mumble Logo

Introduction

Mumble is:

... a low-latency, high quality voice chat program for gaming. It features noise suppression, encrypted connections for both voice and instant messaging, automatic gain control and low latency audio with support for multiple audio standards. Mumble includes an in-game overlay compatible with most open-source and commercial 3D applications. Mumble is just a client and uses a non-standard protocol. You will need a dedicated server to talk to other users. Server functionality is provided by the package "mumble-server".

Mumble has a number of advantages:

• The software is open source and packaged in Debian, as well as for all major operating systems.
• Client to server encryption is supported.
• The communication is high quality and low latency.
• It is possible to check nobody is wiretapping the connection (MITM) by verifying client/server certificates.
• Push to talk is supported.
• The interface is similar to Team Speak, but without its disadvantages.
• It supports TCP mode which is necessary because the Tor network does not support UDP yet.

Tips

To use Mumble, one party must act as a server while everyone else can act as a client. If the server administrator runs the server on its local machine and also wants to connect to the server, then local (127.0.0.1) connections are recommended since it is faster than connecting to the onion service domain.

Group chats pose a greater risk since there is no end-to-end encryption. This means if the server is compromised, all conversations are no longer private. However, if only two parties use Mumble for communications, then end-to-end encryption protects against this threat.

When one of the two communicating parties hosts a mumble server as a Tor onion service and the other party connects over Tor, encryption is already provided by Tor. This means Mumble's own encryption is not required and so long as a server password is set (see below), this configuration should be secure.

For detailed instructions on using and configuring Mumble, refer to:

• Mumble Server Support
• Mumble Documentation Wiki

Mumble Server Instructions

Newcomers are recommended to first read the introduction to Onion Services and to learn about security benefits compared to regular 'clearnet' connections. This wiki resource is also useful if configuring a hidden web server on the same .onion domain, since it helps users to grasp basic operations and test them.

1. Make necessary Whonix-Gateway^™ adjustments.

If Sandbox 1 was previously set in the Tor configuration file, it must be removed for Mumble functionality.

Open file /usr/local/etc/torrc.d/50_user.conf in a text editor of your choice with sudoedit.

If you are using Qubes-Whonix^™, complete the following steps.

Qubes App Launcher (blue/grey "Q") → Whonix-Gateway™ ProxyVM (commonly named sys-whonix) → Tor User Config (Torrc)

If you are using a graphical Whonix-Gateway, complete the following steps.

Start Menu → Applications → Settings → /usr/local/etc/torrc.d/50_user.conf

If you are using a terminal-only Whonix-Gateway, complete the following steps. sudoedit /usr/local/etc/torrc.d/50_user.conf

Add.

Qubes-Whonix^™ note: The IP of Whonix-Workstation^™ AppVM needs to be replaced with the actual IP address. To find out the IP address of the Qubes-Whonix^™ Whonix-Workstation^™ AppVM, the following command can be run within the Qubes-Whonix^™ Whonix-Workstation^™ AppVM.

qubesdb-read /qubes-ip

Do not use IP 10.152.152.11 because that only works with Non-Qubes-Whonix but not with Qubes-Whonix. The IP 10.152.152.11 in line starting with HiddenServicePort needs to be replaced.

HiddenServiceDir /var/lib/tor/mumble_service/ HiddenServicePort 64738 10.152.152.11:64738 HiddenServiceVersion 3

Save.

2. Reload Tor.

Reload Tor.

After changing Tor configuration, Tor must be reloaded for changes to take effect.

Note: If Tor does not connect after completing all these steps, then a user mistake is the most likely explanation. Recheck /usr/local/etc/torrc.d/50_user.conf and repeat the steps outlined in the sections above. If Tor then connects successfully, all the necessary changes have been made.

If you are using Qubes-Whonix^™, complete the following steps.

Qubes App Launcher (blue/grey "Q") → Whonix-Gateway™ ProxyVM (commonly named 'sys-whonix') → Reload Tor

If you are using a graphical Whonix-Gateway, complete the following steps.

Start Menu → Applications → Settings → Reload Tor

If you are using a terminal-only Whonix-Gateway, click HERE for instructions.

Complete the following steps.

Reload Tor.

sudo service tor@default reload

Check Tor's daemon status.

sudo service tor@default status

It should include a a message saying.

Active: active (running) since ...

In case of issues, try the following debugging steps.

Check Tor's config.

sudo -u debian-tor tor --verify-config

The output should be similar to the following.

Sep 17 17:40:41.416 [notice] Read configuration file "/usr/local/etc/torrc.d/50_user.conf".
Configuration was valid

3. Retrieve the Tor onion service url.

sudo cat /var/lib/tor/mumble_service/hostname

Reminder: Always backup the onion service key. This is necessary in order to restore it on another machine, on a newer Whonix-Gateway^™, after HDD/SSD failure, etc. Follow the instructions below to find its location; root permission is required to access it.

/var/lib/tor/mumble_service/hs_ed25519_secret_key

Qubes-Whonix^™

The following example shows how to copy the /var/lib/tor/mumble_service/hs_ed25519_secret_key from the sys-whonix VM to the vault VM (which should be started beforehand) using qvm-copy. A dialog will appear asking for the destination VM.

sudo qvm-copy /var/lib/tor/mumble_service/hs_ed25519_secret_key

When the dialog appears asking to confirm, select vault. This copies the Tor onion service private key file to the QubesIncoming folder of the vault VM.

/home/user/QubesIncoming/sys-whonix/hs_ed25519_secret_key

Consider moving the file from the QubesIncoming folder to another preferred location.

Qubes VM Manager can be used to conveniently backup the vault and/or other VMs. Please refer to the Qubes backups documentation for necessary steps to accomplish that.

Non-Qubes-Whonix

See also:

• file manager Thunar with Administrator Rights
• File Transfer

Documentation for this is incomplete. Contributions are happily considered! See this for potential alternatives.

4. Adjust Whonix-Workstation^™ firewall settings.

Modify Whonix-Workstation^™ User Firewall Settings

Note: If no changes have yet been made to Whonix Firewall Settings, then the Whonix User Firewall Settings File /etc/whonix_firewall.d/50_user.conf appears empty (because it does not exist). This is expected.

If using Qubes-Whonix^™, complete these steps.
In Whonix-Workstation App Qube. Make sure folder /usr/local/etc/whonix_firewall.d exists.

sudo mkdir -p /usr/local/etc/whonix_firewall.d

Qubes App Launcher (blue/grey "Q") → Whonix-Workstation App Qube (commonly called anon-whonix) → Whonix User Firewall Settings

If using a graphical Whonix-Workstation, complete these steps.

Start Menu → Applications → System → User Firewall Settings

If using a terminal-only Whonix-Workstation, complete these steps.

Open file /usr/local/etc/whonix_firewall.d/50_user.conf with root rights.

sudoedit /usr/local/etc/whonix_firewall.d/50_user.conf

For more help, press on Expand on the right.

Note: This is for informational purposes only! Do not edit /etc/whonix_firewall.d/30_whonix_workstation_default.conf.

The Whonix Global Firewall Settings File /etc/whonix_firewall.d/30_whonix_workstation_default.conf contains default settings and explanatory comments about their purpose. By default, the file is opened read-only and is not meant to be directly edited. Below, it is recommended to open the file without root rights. The file contains an explanatory comment on how to change firewall settings.

## Please use "/etc/whonix_firewall.d/50_user.conf" for your custom configuration,
## which will override the defaults found here. When {{project_name_short}} is updated, this
## file may be overwritten.

Also see: Whonix modular flexible .d style configuration folders.

To view the file, follow these instructions.

If using Qubes-Whonix, complete these steps.

Qubes App Launcher (blue/grey "Q") → Template: whonix-workstation-17 → Whonix Global Firewall Settings

If using a graphical Whonix-Workstation, complete these steps.

Start Menu → Applications → Settings → Global Firewall Settings

If using a terminal-only Whonix-Workstation, complete these steps.

In Whonix-Workstation, open the whonix_firewall configuration file in an editor. nano /etc/whonix_firewall.d/30_whonix_workstation_default.conf

Add.

EXTERNAL_OPEN_PORTS+=" 64738 "

Save.

5. Reload the firewall.

Reload Whonix-Workstation^™ Firewall.

If you are using Qubes-Whonix^™, complete the following steps.

Qubes App Launcher (blue/grey "Q") → Whonix-Workstation App Qube (commonly named anon-whonix) → Reload Whonix Firewall

If you are using a graphical Whonix-Workstation, complete the following steps.

Start Menu → Applications → System → Reload Whonix Firewall

If you are using a terminal-only Whonix-Workstation, run. sudo whonix_firewall

6. Update the package lists and install necessary software.

sudo apt update

Install the mumble-server package.

sudo apt install mumble-server

7. Configure the server.

sudo dpkg-reconfigure mumble-server

Follow the recommendations below:

• Autostart is suggested, unless you want to run sudo service mumble-server start (which failed in the past).
• Higher priority? Select 'Yes'.
• Password: choose a secure password.

There is also an upstream Mumble server guide, but it does not consider onion services which are already described here. For any additional questions regarding the server setup, refer to the upstream documentation.

8. Set a server password in the relevant file.

Open file /etc/mumble-server.ini in an editor with root rights.

Non-Qubes-Whonix^™

This box uses sudoedit for better security.

sudoedit /etc/mumble-server.ini

Qubes-Whonix^™

NOTES:

• When using Qubes-Whonix, this needs to be done inside the Template.

sudoedit /etc/mumble-server.ini

• After applying this change, shutdown the Template.
• All App Qubes based on the Template need to be restarted if they were already running.
• This is a general procedure required for Qubes and unspecific to Qubes-Whonix^™.

Others and Alternatives

• This is just an example. Other tools could achieve the same goal.
• If this example does not work for you or if you are not using Whonix, please refer to this link.

sudoedit /etc/mumble-server.ini

Search for "serverpassword=" and file in.

serverpassword=use_a_long_and_secure_server_password

9. Restart mumble-server.

sudo service mumble-server restart

Mumble Client

Installation

Update the package lists.

sudo apt update

Install mumble.

sudo apt install mumble

Start

Launch Mumble.

Start menu → Applications → Internet → Voice Chat

Or in a terminal, run.

mumble

Figure: Mumble Client in Whonix

Configure

Configure Mumble to suit your preferences.

Next, enable Force TCP mode.

Go to Configure → Select "Settings" → Network → Check "Force TCP mode" → Ok

Figure: Mumble Network Setting

Add Server

Follow these steps to add a new server.

Server → Connect → Add New...

1. Servername: anything - this can be same as the .onion domain name
2. Address: enter your .onion domain name or if the mumble server is running in your own Whonix-Workstation, choose 127.0.0.1
3. Port: 64738
4. Username: anything

It is now possible to connect to the server.

Figure: Mumble Server Information

Technical Notes

Mumble (and mumble-server) connections pass through Tor's TransPort, but this should not have a negative anonymity impact. The reason is connections to and from onion services are stream-isolated.

Security-conscious, free software developers consider browsers as a poor and dangerous option for implementing privacy-critical software. Browsers have a large attack surface (numerous security holes) and lack adequate process isolation, which can lead to the theft of private encryption keys if malicious code is run.

Asterisk VoIP Server over OpenVPN in Tor Hidden Service

Introduction

This entry was contributed by Norbert Szczybelski. For questions and further information, refer to the forum discussion: How To setup Asterisk VoIP server over OpenVPN in Tor hidden service.

Asterisk is:

... a software implementation of a private branch exchange (PBX). In conjunction with suitable telephony hardware interfaces and network applications, Asterisk is used to establish and control telephone calls between telecommunication endpoints, such as customary telephone sets, destinations on the public switched telephone network (PSTN), and devices or services on voice over Internet Protocol (VoIP) networks.

Since Asterisk is open source and supports several standard VoIP protocols, it can be configured in Whonix to enable the PC to run as a server for a VoIP service.

Official Asterisk wiki documentation can be found here.

Configuration Overview

Configuration files are outlined below for:

• OpenVPN server
• OpenVPN clients
• Tor hidden service
• Tor clients
• Asterisk SIP protocol
• Asterisk extensions

Note: this is a chrooted configuration. If necessary, servers can also be isolated in virtual machines. Be sure to also update CPU microcode to protect against the Spectre and Meltdown vulnerabilities.

As an illustration, simply set up:

• 172.16.0.2/10.8.0.1 OpenVPN Server - bhyve VM on server.
• 172.16.0.3/10.8.0.10 OpenVPN Client with Apache - bhyve VM on server.
• 172.16.0.4/10.8.0.20 OpenVPN Client with Asterisk - bhyve VM on server.
• 172.16.0.5/10.8.0.30 OpenVPN Client with UnrealIRCd - bhyve VM on server.

...

• 172.31.0.9/10.8.10.10 OpenVPN Client with Apache - bhyve VM on client.
• 192.168.38.37/10.8.10.20 OpenVPN Client with UnrealIRCd - bhyve VM on client.

And so on. Next, set up static IP addresses in ccd directory for OpenVPN Client servers. Finally, generate encryption keys with OpenSSL (modified OpenSSL can be utilized for quantum-resistant cryptography).

OpenVPN Server openvpn.conf Configuration File

mode server tls-server dev tun proto tcp-server port 1194 server 10.8.0.0 255.255.0.0 ca /vpn/ca.crt cert /vpn/server.crt key /vpn/server.key dh /vpn/dh2048.pem tls-crypt /vpn/ta.key cipher AES-256-CBC auth SHA3-512 log /var/log/openvpn.log status /var/log/openvpn-status.log user nobody group nobody persist-key persist-tun chroot /usr/local/etc/openvpn/jail auth-nocache # If you want to allow clients to communicate between themselves e.g. start own services like UnrealIRCd Servers. client-to-client client-config-dir /ccd

OpenVPN Clients client.conf Configuration File

client remote-cert-tls server dev tun <connection> remote youroniondomain.onion 1194 tcp-client socks-proxy 127.0.0.1 9050 </connection> cipher AES-256-CBC auth SHA3-512 user nobody group nogroup persist-key persist-tun chroot /etc/openvpn/jail auth-nocache log /var/log/openvpn/openvpn.log status /var/log/openvpn/openvpn-status.log <ca> </ca> <cert> </cert> <key> </key> <tls-crypt> </tls-crypt>

Tor Hidden Service torrc Configuration File

HiddenServiceDir /usr/local/torhs/hiddenservice/ HiddenServicePort 1194 127.0.0.1:1194

Tor clients torrc Configuration File

SOCKSPort 9050

Asterisk sip.conf Configuration File

[general] transport=udp port=5060 bindaddr=10.8.0.1 disallow=all allow=ulaw allow=alaw allow=gsm directmedia=no nat=yes localnet=10.8.0.0/255.255.255.0 [friends_internal](!) type=friend host=dynamic context=from-internal disallow=all allow=ulaw allow=alaw allow=gsm [demo-alice](friends_internal) secret=password [demo-bob](friends_internal) secret=password

Asterisk extensions.conf Configuration File

[from-internal] exten=>6001,1,Dial(SIP/demo-alice,20) exten=>6002,1,Dial(SIP/demo-bob,20)

Quantum Resistant OpenVPN

For greater security, a modified form of OpenSSL can be utilized:

• OPEN QUANTUM SAFE - Software for prototyping quantum-resistant cryptography
• liboqs
• OQS-OpenSSL

Use of the above software is at the user's own risk and security is not guaranteed; always conduct research beforehand to assess whether it is suitable in your circumstances.

Warnings

Skype

Does this mean if I combine Whonix with proprietary software like Skype, that my IP address and location will be safe?

Yes, the IP address and location remain hidden. Skype was tested to work in Whonix several years ago, but it appears to have stopped working around 2013/14. Developers have very little interest in testing or providing functional Skype instructions, because it is strongly recommended against. As gnu.org notes: "Skype contains spyware. Microsoft changed Skype specifically for spying."

Any corporation that willingly changes flagship software to enable secretive surveillance of users (without notice) cannot redeem itself. In addition:

• Microsoft has long delayed providing a secure end-to-end encrypted communication channel until the announcement of the non-default "Conversations" option in 2018.
• After Microsoft purchased Skype in 2010 they changed the architecture, leading observers to note this would increase the ease of surveillance. Client-side encryption was replaced with server-side encryption, allowing unencrypted data to be disseminated when requested.
• Skype is closed source software and inherently distrusted based on Microsoft's behavior. For example it was revealed in 2013 that Skype had a program entitled "Project Chess", which was exploring legal and technical issues in making communications available to law enforcement and other agencies.
• Company executives lied in 2012 when they denied giving government agency access to customer communications.
• Skype has a long history of serious security flaws and conducting unannounced spying, such as reading BIOS data from the PC and accessing the Firefox profile folder during execution (where passwords are stored).

None of these issues are related to Whonix or Tor; the blame falls squarely on the company producing the software. At best, Skype usage can only be considered pseudonymous rather than anonymous, particularly since it acts like malware. It would be completely unsurprising if Skype linked all account names inside Whonix-Workstation to the same pseudonym.

As well as the threat posed by Skype's design, behavior and parent company, there are additional risks to this non-freedom software:

• Accounts: if you log into an account without Tor, even once, then it should be considered non-anonymous. It is virtually certain logs are retained that can link Tor and non-Tor use together.
  • Always follow the wiki recommendations to not mix anonymity modes.
• Communication partner: if the other party did not create their account over Tor, or has not exclusively paired the account with Tor, then it is easy to verify your identity.
• Encryption: as noted above, the encryption architecture is weak by default and the Skype authority is unworthy of trust -- consider the encryption broken at the outset. Always remember you do not control the encryption keys and the closed source software is hostile to privacy by design.
• Voice recognition: as noted in the introduction, today's sophisticated software can easily identify you, even if Skype encryption is not broken.

In conclusion, Skype cannot be used for truly (pseudo-)anonymous activites, even though it does not leak the IP address/location. This means it is useful for circumvention only. Anybody capable and willing to communicate with partners who exclusively create and use accounts over Tor have far better options available.

Refer to the technical footnotes if you are interested in why Skype works at all in Whonix over Tor (since Tor only supports TCP).

TORFone

Whonix has consistently advised against TORFone -- a fork of SpeakFreely -- since the developer in 2013 recommended against using the software: "I did not think this project as a finished product for practical use." At that time, the project received an overall poor review in the mailing list thread.

It is unclear whether the situation has improved over the last several years, but the software is under active development based on the number of recent commits. Any reader who is interested in testing TORFone in Whonix is encouraged to report their experience here.

USB Webcam Passthrough

Avoid this course of action -- the firmware of USB devices could be flashed by malware and cross infect the host.

VoIP Software List

There is a Comparison of VoIP software page on Wikipedia. Any client that is chosen should be open source and if onion services are not being used on both ends of the communication (where Tor handles the encryption), then it should also support voice encryption such as ZRTP.

Sources

• guardianproject.info: Mumble and the Bandwidth Anonymous CB radio with Mumble and Tor

Footnotes

Whonix The most watertight privacy operating system in the world.

Dark mode

Follow us on social media

Supported by Power Up Privacy

Whonix is proudly supported until 2025 by Power Up Privacy, a privacy advocacy group that seeks to supercharge privacy projects with resources so they can complete their mission of making our world a better place. (Strictly subject to our sponsorship policy.)

At Whonix we value freedom and trust, supporting Open Source and Freedom Software

By using this website, you acknowledge you have read, understood, and agree to be bound by these agreements: Terms of Service, Privacy Policy, Cookie Policy, E-Sign Consent, DMCA, Imprint 2012- 2024 ENCRYPTED SUPPORT LP

Your support makes
all the difference!

We believe security software like Whonix needs to remain open source and independent. Would you help sustain and grow the project? Learn more about our 12 year success story and maybe DONATE!