freedombone-client(1)

NAME
freedombone-client - Secure client machines for optimal interoperability with a Freedombone system

SYNOPSIS
    freedombone-client

DESCRIPTION
The freedombone-client command provides a simple way to secure GNU/Linux clients which connect to a Freedombone server. It alters encryption settings to increase resistance to passive interception.

INSTALLATION
If you have the debian package then you can just:
    dpkg -i freedombone_x.xx.deb Or alternatively you can download the latest code and install it.
    sudo apt-get update
    apt-get install git dialog build-essential
    git clone https://github.com/bashrc/freedombone
    cd freedombone
    make install

USAGE
Assuming that you are using a Debian based GNU/Linux distro, typically just run the following command on your laptop or desktop machine before connecting to the Freedombone:
    freedombone-client When ssh keys are generated it's a good idea to add a password to them so that if they key are later compromised an attacker would still need to know the password in order to be able to log in. You can add ssh keys for users on the administrator control panel under "manage users". If you want to use your system on a mesh network then additional mesh packages can be installed with:
    freedombone-client --mesh yes If you want to install and configure the Hexchat IRC client in a way suitable for connecting to the Freedombone server then do the following:
    freedombone-client --setup hexchat

VERIFYING THE SERVER SSH PUBLIC KEY
When you ssh to the Freedombone system for the first time it will usually display a message showing a hash of the server ssh public key (aka host key). You can check that this is correct by going to the administrator control panel and selecting the "about" screen, then in a separate terminal window run the command:
    freedombone-client --verify You can then check the hashes to see that they match. This isn't foolproof because a truly evil machine-in-the-middle would do a search and replace on the data stream to fool you into believing its host key was the Freedombone host key. Another more manual way to check would be to power off the Freedombone, remove the microSD drive, insert it into a laptop and then check the public keys within the /etc/ssh directory of the drive.

BUGS
Report bugs at https://github.com/bashrc/freedombone/issues

AUTHOR
Bob Mottram <bob@freedombone.net>
PGP/GPG: EA982E38
Web: https://freedombone.net