since i see several people leeching at this, i might as well publish the setup guide (you will find this also in the readme on the vm). there will be a release as torrent (hopefully) soon, that might be easier to download. anyway:
Quick setup guide for the impatient (and the only one so far)
-Download image with i2p snark (prefered) or download at http://acmsrfsbsogtuhvk.onion/ffvm_beta.ova
-If you use the direct download, check that you received the image correctly, by comparing the checksum to the one from the checksumfile
from the website http://acmsrfsbsogtuhvk.onion/ffvm_beta.ova.checksumfile
Example how to this check in debian:
apt install libdigest-sha3-perl
sha3sum --check ./ffvm_beta.ova.checksumfile
-use with I2p: -create server tunnels pointing to port 60080 and 60119 on the host system (assumed to have the ip 192.168.1.15 in this example)
-create a server tunnel pointing to the news server you want to sync with (the address must come from the admin of this service)
-use with Tor:
-create a hidden service pointing to port 60080 and 60119 on the host system
-create a connection to the hidden service you want to sync with. You can use the script create_tor_tunnel.sh to do this with socat.
-setup firewall rules to block all incoming traffic to the host machine except to the needed ports (60022,60080,60119)
-setup firewall rules to block all outgoing traffic from the host except to tor or i2p (typically 4444 for i2p (and another port of your choosing for the news server), 8118 for privoxy, 9050 for tor)
-import the ova file with virtualbox (if you want to use virtualbox), or untar the ova file and convert the image to use qemu.
tar xvf ./*.ova
convert for the use with qemu with:
qemu-img convert -c -O qcow2 -f vdi ./NetServices/NetServices-disk1.vdi ./ffvm_beta.qcow2
-Start up the vm with your program of choice.
-cli example for qemu: qemu-system-x86_64 /path/to/image/ffvm_beta.qcow2 -netdev user,id=ethernet.0,hostfwd=tcp::60119-:119,hostfwd=tcp::60080-:80,hostfwd=tcp::60022-:22 -device rtl8139,netdev=ethernet.0 -nographic
-this command will make the vm start up with a nat that allows all outgoing connections from guest. The ports 22,80 and 119 on the guest machine are made available on your host system on the ports 60022, 60080 and 60119. The -nographic at the end makes it start without
a graphic interface.
-append --enable-kvm to the command above to boost the performance of the vm (only possible if host is a x86_64 machine).
-with virtualbox, start up the machine, the network setup is included. Just make sure later that ingoing and outgoing connections work
like expected (from guest to host and from host to guest).
-Login into your vm directly (if you started it with an interface), with user/filter24.
You can do the same remotely (if you started without an interface), using ssh email@example.com -p 60022
The example above assumes that the host system has the ip 192.168.1.15 and that the port 22 on the guest system is forwarded to port 60022 on the host system like described above. Adapt the ip and port to your setup if neccessary.
-Become root with su
The password is filter24 as well.
-Change password for user to something secure with passwd user
-Change password for root to something secure with
-If you want the vm to use a proxy (see optional step before), set the proxy with export http_proxy="192.168.1.10:8118" Adapt to your setup if needed, this example has a privoxy server running on the machine with the ip 192.168.1.10 on the port 8118. Make sure the vm can access the machine running the proxy.
-Update the guest system with
apt update && apt upgrade
-if you want to sync with another node, get in contact with the admin, and get the address of the news server on tor and/or i2p, as well as
the username and password needed. Provide the other admin with the address of your news server. -change the directory with cd /home/user -run the config script
if you do not have the username and password from the admin of the other news server at this point, just put in something. You can
rerun the script later when you have them.
-edit the config files of the frontends to your liking (/var/www/data/bbs.config and /var/www/html/rslight/rslight.inc.php).
-the groups installed by default are those of the hierarchy rocksolid.shared. If you want other groups, you can create and delete groups
on the news server with the help of the scripts
or directly using ctlinnd newgroup $Groupname
ctlinnd rmgroup $Groupname
After doing this you have to edit the files /var/www/data/bbs.config and /var/www/html/rslight/$hierachy/groups.txt to follow the changes on the frontends as well (if you have deleted any groups, make sure to delete them as well in the file /var/www/data/bbs.config.
bbs will not start up if it cannot read all the groups it should display).
-reboot the vm with
Done, your node should work now. Check if you can reach the webserver and post something, see if the message is pushed to the other node. Do a pullnews update with /home/user/pull.sh and check if it works (a complete pullnews run will get all the old messages from the other news server).
Posted on def4