There are a few other glitches that need attention.
VENTOY PFSENSE UPDATE
The most recent stable Tor port in FreeBSD is tor-0.2.4.21, and I’ll update before the next LiveDVD trial. I’m currently using tor-0.2.3.25 (out of laziness).
VENTOY PFSENSE PATCH
At best, I’d need to patch and recompile bootcdwrite. At least, there is no way to change it in nf or command-line options. However, the allocation seems quite deeply hard-coded.
If that were possible, this LiveDVD would easily run in 4 GB RAM, even with some additional apps. Ideally, I would like to change the allocation of RAM for /ram1 and /ram2. I need to add additional apps, but I’d like to keep the RAM requirement under 6 GB. And, given that there are just two VMs, it should be OK on dual-core CPUs. I’m also confident that it would run on older Intel and AMD quad-core CPUs. I’m confident that this LiveDVD would run on a box with 5 GB RAM (if that’s possible). From top, I see that 3.38 GB RAM is available. It loads ~2.1 GB into /ram1, but there’s virtually nothing in /ram2. Given 8 GB RAM, the current LiveDVD creates two 3.88 GB ramdisks (each half of total RAM). The system is very responsive after that, except for some lag when starting apps for the first time. The initial DVD load takes ~5.6 minutes, and VM startup takes ~3.5 minutes. Using the build machine, it takes ~9.2 minutes to reach the Tor Project check page. I’ve verified that it boots in the build machine, and also in a ThinkPad T420 (also with 8 GB RAM). Using bootcdwrite, I’ve created a 2.46 GB LiveDVD (LiveDVD_0.1.iso). I’ve added menu entries there to start VirtualBox, and also to shutdown the host (everything). Shutting down the Whonix workstation VM drops focus to the host fluxbox desktop. I’ve added menu entries in the Whonix workstation VM to manually start the Tor Browser, and also to shutdown the VM. I’ll get advice on fixing that from pfSense support. That breaks some things in Whonix Workstation, most importantly (I think) “New Identity” and the rest of “Torbutton”. I’ve verified that there’s no LANInternet connectivity except through the Tor process.Īlso, I’ve commented out ControlPort, ControlSocket and cookie authentication, because user _tor doesn’t have enough rights to use them. However, pfSense has no DNS server configured, and won’t accept one via WAN. I’ve changed DnsPort to 1053, because pfSense claims 53. I’ve used all of the settings from the Whonix Gateway, with two exceptions. The Tor data directory is /var/db/tor, and torrc is in /usr/local/etc/tor. The only exception is recovery from lockouts, which requires VirtualBox intervention (ACPI shutdown and restart). All management and configuration can be performed using the WebGUI.
VENTOY PFSENSE PASSWORD
Workspace VM: custom Whonix 8.1 Workstation (1.79 GB VMDK)įrom “df -aBM” on the host machine, I get:Īlthough the pfSense VM is running headless, its WebGUI is available at with username “admin” and password “drowssap”. Host OS: Debian 7.4 x86 with fluxbox desktop and VirtualBox 4.3.10
The setup for creating the current version (LiveDVD_0.1.iso) is as follows: To create the LiveDVD, I configure a “build machine” (i5 quad-core with 8 GB RAM and 120 GB SSD) as desired, and then run bootcdwrite. That would require installing Guest Additions, mounting another partition, and creating and mounting a shared folder. But there’s no easy way to save anything.
VENTOY PFSENSE INSTALL
However, it’s also possible to access everything normally, and to even install new VMs or whatever. After bootup has completed, the user sees the Tor Browser full-screen, with as home page. For the most part, all of the guts (such as the host OS, VirtualBox, and the Tor gateway VM) are kept in the background. In this exercise, my goal is a LiveDVD with TBB-like behavior.
0 kommentar(er)
