freedombone/usage.org at 071527b45d85766a70cf8a2eee76f82b1c4c9f0a

Readme

After the system has installed a README file will be generated which contains passwords and some brief advice on using the installed systems. You can read this with the following commands:

ssh username@domainname -p 2222
emacs ~/README

You should transfer any passwords to a password manager such as KeepassX and then delete them from the README file. To save the file after removing passwords use CTRL-x CTRL-s.

To exit you can either just close the terminal or use CTRL-x CTRL-c followed by the exit command.

Improving ssh security

To improve ssh security you can generate an ssh key pair on your system and then upload the public key to the Freedombone.

On your local machine:

ssh-keygen

For extra security you may also want to add a passphrase to the ssh private key. You can show the generated public key with:

cat ~/.ssh/id_rsa.pub

Copy the contents of ~/.ssh/id_rsa and ~/.ssh/id_rsa.pub to you password manager, together with the private key password if you created one.

ssh to the Freedombone and edit the authorized keys:

ssh username@domain -p 2222
emacs ~/.ssh/authorized_keys

Now copy and paste the contents of id_rsa.pub into the authorized_keys file. Save the file and exit. Open another terminal window and try logging in again and you should notice that you are no longer asked for a password, because the ssh key is used instead.

There are advantages and disadvantages to using ssh keys for logins. The advantage is that this is much more secure than a memorised password, but the disadvantage is that you need to carry your ssh keys around and be able to install them on any computer of mobile device that you use. In high security or hostile infosec environments it may not be possible to carry or use USB thumb drives containing your keys and so memorised passwords may be the only available choice.

If you wish to only use ssh keys then log in to the Freedombone and edit /etc/ssh/sshd_config, then change PasswordAuthentication to "no", save and run service ssh restart. Any subsequent attempts to log in via a password will then be denied.

Using Email

A technical note about email transport security

Port 465 is used for SMTP and this is supposedly deprecated for secure email. However, using TLS from the start of the communications seems far more secure than starting off with insecure communications and then trying to upgrade it with a command to begin TLS, as happens with STARTTLS. There are possible attacks against STARTTLS in which the command to begin secure communications is removed or overwritten which could then result in email being transferred in plain text over the internet and be readable by third parties.

From http://motherboard.vice.com/read/email-encryption-is-broken:

The researchers also uncovered mass scale attacks of STARTTLS sessions being stripped of their encryption. That attack itself isn't new: internet service providers sometimes do it to monitor users; organizations may use it to keep an eye on employees; or it may come from a malicious actor

Add a password to your GPG key

If you didn't use existing GPG keys during the Freedombone installation then you'll need to add a password to your newly generated private key. This is highly recommended. Go through the following sequence of commands to ssh into the Freedombone and then change your GPG password.

ssh username@domainname -p 2222
gpg --edit-key username@domain
passwd
save
quit
exit

Having a password on your GPG key will prevent someone from reading your email even if your server gets lost or stolen or if someone else has physical access to it. Make the password something long and unlikely to be guessable or vulnerable to a brute force dictionary attack.

Publishing your GPG public key

If you havn't already then you should publish your GPG public key so that others can find it.

ssh username@domainname -p 2222
gpg --send-keys username@domainname
exit

Mutt email client

Mutt is a terminal based email client which comes already installed onto the Freedombone. To access it you'll need to access it via ssh with:

ssh username@domainname -p 2222

If you're using Windows there is an ssh client called putty, on Linux just open a terminal and enter the above command with your username and domain name. On Android you can use the ConnectBot app with the hostname username@domain:2222

Once you have logged in via ssh then just type mutt. Like most terminal programs mutt is quite easy once you've learned the main keys.

Some useful keys to know are:

"/"	Search for text within headers
*	Move to the last message
TAB	Move to the next unread message
d	Delete a message
u	Undelete a mail which is pending deletion
$	Delete all messages selected and check for new messages
a	Add to the address book
m	Send a new mail
ESC-m	Mark all messages as having been read
S	Mark a message as spam
H	Mark a message as ham
CTRL-b	Toggle side bar on/off
CTRL-n	Next mailbox (on side bar)
CTRL-p	Previous mailbox (on side bar)
CTRL-o	Open mailbox (on side bar)
r	Reply to an email
L	Reply to a mailing list email
]	Expand or collapse all threads
[	Expand of collapse the current thread
CTRL-k	Import a PGP/GPG public key
q	Quit

To use the address book system open an email by pressing the enter key on it and then to add the sender to the address list press the A key. It will ask you for an alias which may be used the next time you want to send a mail. Alternatively you may just edit the ~/.mutt-alias file directly to add email addresses.

One of the most common things which you might wish to do is to send an email. To do this first press m to create a new message. Enter the address to send to and the subject, then after a few seconds the Emacs editor will appear with a blank document. Type your email then press CTRL-x CTRL-s to save it and CTRL-x CTRL-c to exit. You will then see a summary of the email to be sent out. Press y to send it and then enter your GPG key passphrase (the one you gave when creating a PGP/GPG key). The purpose of that is to add a signature which is a strong proof that the email was written by you and not by someone else.

When reading emails you will initially need to enter your GPG password. It will be retained in RAM for a while afterwards.

Thunderbird/Icedove

Another common way in which you may want to access email is via Thunderbird (also known as Icedove on Debian). This may be especially useful if you're trying to convert former Windows users who may previously have been using some version of Outlook.

The following instructions should be carried out on the client machines (laptop, etc), not on the BBB itself.

Initial setup

Install Thunderbird and Enigmail. How you do this just depends upon your distro and software manager or "app store".

Open Thinderbird

Select "Skip this and use existing email"

Enter your name, email address (myusername@mydomainname.com) and the password for your user.

You'll get a message saying "Thunderbird failed to find the settings"

The settings should be as follows, substituting mydomainname.com for your domain name and myusername for the username.

Incoming: IMAP, mydomainname.com, 993, SSL/TLS, Normal Password
Outgoing: SMTP, mydomainname.com, 465, SSL/TLS, Normal Password
Username: myusername

Click Done.

Click Get Certificate and make sure "permanently store this exception" is selected", then click Store Security Exception.

From OpenPGP setup select "Yes, I would like the wizard to get me started". If the wizard doesn't start automatically then "setup wizard" can be selected from OpenPGP on the menu bar.

Select "Yes, I want to sign all of my email"

Select "No, I will create per-recipient rules"

Select "yes" to change default settings.

Import your GPG keys

On the Freedombone export your GPG public and private keys.

ssh username@domainname -p 2222
gpg --list-keys username@domainname
gpg --output ~/public_key.gpg --armor --export KEY_ID
gpg --output ~/private_key.gpg --armor --export-secret-key KEY_ID

On your laptop or desktop you can import the keys with:

scp -P 2222 username@domain:/home/username/*.gpg ~/

Select "I have existing public and private keys".

Select your public and private GPG exported key files.

Select the account which you want to use and click Next, Next and Finish.

Remove your exported key files, both on your laptop/desktop and also on the Freedombone.

shred -zu ~/public_key.gpg
shred -zu ~/private_key.gpg

Using for the first time

Click on the Thunderbird menu, which looks like three horizontal bars on the right hand side.

Hover over preferences and then Account settings.

Select OpenPGP Security and make sure that use PGP/MIME by default is ticked. This will enable you to sign/encrypt attachments, HTML bodies and UTF-8 without any problems.

Select Synchronization & Storage.

Make sure that Keep messages for this account on this computer is unticked, then click Ok.

Click on Inbox. Depending upon how much email you have it may take a while to import the subject lines.

Note that when sending an email for the first time you will also need to accept the SSL certificate.

Get into the habit of using email encryption and encourage others to do so. Remember that you may not think that your emails are very interesting but the Surveillance State is highly interested in them and will be actively trying to data mine your private life looking for "suspicious" patterns, regardless of whether you are guilty of any crime or not.

Making folders visible

By default you won't be able to see any folders which you may have created earlier using the mailinglistrule script. To make folders visible select:

Menu, hover over Preferences, select Account Settings, select Server Settings then click on the Advanced button.

Make sure that "show only subscribed folders" is not checked. Then click the ok buttons. Folders will be re-scanned, which may take some time depending upon how much email you have, but your folders will then appear.

K9 Android client

A point about GPG on Android

Before trying to set up email on Android you may want to consider whether you really need to do this. Android (and its variants) is not a particularly secure operating system and whether or not you wish to store GPG keys on it depends on your threat model and in what situations you'll be using your device.

If you are going to use email on an Android device then ensure that you have full encryption enabled via the security settings, so that if you subsequently lose it, or if it gets stolen, the chances of encryption keys being exposed are minimised.

Compiling the development version

To get K9 working with Freedombone you'll need to install development versions of OpenKeychain and K9. At the time of writing the versions available in F-Droid do not support PGP/MIME or the "hidden recipient" feature of GPG. It is hoped that at some stage the patches will be integrated into the mainline or functionally equivalent changes made. Admittedly, this is not at all user friendly, but currently it's the only way to read Freedombone email on Android systems.

Build script for OpenKeychain:

mkdir ~/develop
cd ~/develop
git clone https://github.com/bashrc/open-keychain
cd open-keychain
git checkout origin/bashrc/hidden-recipient-minimal
git checkout -b bashrc/hidden-recipient-minimal
cd tools
nano build.sh

Then add the following:

#!/bin/bash

# This script is intended to be used on Debian systems for building
# the project. It has been tested with Debian 8

USERNAME=$USER
SIGNING_NAME='openkeychain'
SDK_VERSION='r23.3.4'
SDK_DIR=$HOME/android-sdk

cd ..

PROJECT_HOME=$(pwd)

sudo apt-get install build-essential default-jdk \
     lib32stdc++6 lib32z1 lib32z1-dev

if [ ! -d $SDK_DIR ]; then
    mkdir -p $SDK_DIR
fi
cd $SDK_DIR

# download the SDK
if [[ ! -f $SDK_DIR/android-sdk_$SDK_VERSION-linux.tgz ]]; then
    wget https://dl.google.com/android/android-sdk_$SDK_VERSION-linux.tgz
fi
tar -xzvf android-sdk_$SDK_VERSION-linux.tgz
SDK_DIR=$SDK_DIR/android-sdk-linux

echo 'Check that you have the SDK tools installed for Android 22, SDK 21.1.2'

export ANDROID_HOME=$SDK_DIR
echo "sdk.dir=$SDK_DIR" > $ANDROID_HOME/local.properties
export PATH=${PATH}:$ANDROID_HOME/tools:$ANDROID_HOME/platform-tools

cd $SDK_DIR/tools
./android sdk

if [ ! -f $SDK_DIR/tools/android ]; then
    echo "$SDK_DIR/tools/android not found"
    exit -1
fi
cd $SDK_DIR
chmod -R 0755 $SDK_DIR
chmod a+rx $SDK_DIR/tools

# android sdk
cd $PROJECT_HOME
git submodule init && git submodule update

if [ ! -f $SDK_DIR/tools/templates/gradle/wrapper/gradlew ]; then
    echo "$SDK_DIR/tools/templates/gradle/wrapper/gradlew not found"
    exit -2
fi
. $PROJECT_HOME/gradlew assembleDebug

# cleaning up
cd $PROJECT_HOME/OpenKeychain/build/outputs/apk
if [ ! -f OpenKeychain-debug.apk ]; then
    echo 'OpenKeychain-debug.apk was not found'
    exit -3
fi

echo 'Build script ended successfully'
echo -n 'apk is available at: '
echo "$PROJECT_HOME/OpenKeychain/build/outputs/apk/OpenKeychain-debug.apk"
exit 0

Save and exit with CTRL-o, CTRL-x.

chmod +x build.sh
./build.sh

Build script for K9:

cd ~/develop
git clone https://github.com/k9mail/k-9
cd k-9
cd tools
nano build.sh

Then add the following:

#!/bin/bash

# This script is intended to be used on Debian systems for building
# the project. It has been tested with Debian 8

USERNAME=$USER
SIGNING_NAME='k-9'
SDK_VERSION='r24.3.3'
SDK_DIR=$HOME/android-sdk

cd ..

PROJECT_HOME=$(pwd)

sudo apt-get install build-essential default-jdk \
     lib32stdc++6 lib32z1 lib32z1-dev

if [ ! -d $SDK_DIR ]; then
    mkdir -p $SDK_DIR
fi
cd $SDK_DIR

# download the SDK
if [ ! -f $SDK_DIR/android-sdk_$SDK_VERSION-linux.tgz ]; then
    wget https://dl.google.com/android/android-sdk_$SDK_VERSION-linux.tgz
    tar -xzvf android-sdk_$SDK_VERSION-linux.tgz
fi
SDK_DIR=$SDK_DIR/android-sdk-linux

echo 'Check that you have the SDK tools installed for Android 17, SDK 19.1'
if [ ! -f $SDK_DIR/tools/android ]; then
    echo "$SDK_DIR/tools/android not found"
    exit -1
fi
cd $SDK_DIR
chmod -R 0755 $SDK_DIR
chmod a+rx $SDK_DIR/tools

ANDROID_HOME=$SDK_DIR
echo "sdk.dir=$SDK_DIR" > $ANDROID_HOME/local.properties
PATH=${PATH}:$ANDROID_HOME/tools:$ANDROID_HOME/platform-tools

android sdk
cd $PROJECT_HOME

if [ ! -f $SDK_DIR/tools/templates/gradle/wrapper/gradlew ]; then
    echo "$SDK_DIR/tools/templates/gradle/wrapper/gradlew not found"
    exit -2
fi
. $PROJECT_HOME/gradlew assembleDebug

# cleaning up
cd $PROJECT_HOME/k9mail/build/outputs/apk
if [ ! -f k9mail-debug.apk ]; then
    echo 'k9mail-debug.apk was not found'
    exit -3
fi
echo 'Build script ended successfully'
echo -n 'apk is available at: '
echo "$PROJECT_HOME/k9mail/build/outputs/apk/k9mail-debug.apk"
exit 0

Save and exit with CTRL-o, CTRL-x.

chmod +x build.sh
./build.sh

Import your GPG key into OpenKeychain

With your device connected to a laptop via USB cable and with USB debugging enabled on it:

ssh username@domainname -p 2222
gpg --list-keys username@domainname
gpg --output ~/public_key.gpg --armor --export KEY_ID
gpg --output ~/private_key.gpg --armor --export-secret-key KEY_ID
cat ~/public_key.gpg ~/private_key.gpg > ~/mygpgkey.asc
exit
scp -P 2222 username@domainname:/home/username/mygpgkey.asc ~/
sudo apt-get install android-tools-adb
push ~/mygpgkey.asc /sdcard/
shred -zu ~/mygpgkey.asc

Then on your device select OpenKeychain and import your key from file.

Incoming server settings

Select settings/account settings
Select Fetching mail/incoming server
Enter your username and password
IMAP server should be your domain name
Security: SSL/TLS (always)
Authentication: Plain
Port: 993

Outgoing (SMTP) server settings

Select settings/account settings
Select Sending mail/outgoing server
Set SMTP server to your domain name
Set Security to SSL/TLS (always)
Set port to 465
Set authentication to PLAIN
Enter your username and password
Accept the SSL certificate

Crypto settings

Select settings, Account settings, OpenKeychain and then select your key and press Allow. You should now be able to decrypt emails by entering your GPG passphrase.

You may also want to change the amount of time for which passwords are remembered, so that you don't need to enter your passphrase very often.

Folders

To view any new folders which you may have created using the mailinglistrule script from your inbox press the K9 icon at the top left to access folders, then press the menu button and select refresh folder list.

If your folder still doesn't show up then press the menu button, select show folders and select all folders.

Subscribing to mailing lists

To subscribe to a mailing list log in as your user (i.e. not the root user).

ssh username@domainname -p 2222
freedombone-addlist -l <mailing list name> -s <subject tag> -e <list email address>
exit

The subject tag should be the word or phrase which appears within the brackets in the subject line of emails from the mailing list. The mailing list name should be something short so that it is readable within the left side column of the mutt email client, and contain no spaces. You can also use the freedombone-rmlist if you wish not to show a particular list within Mutt.

Adding email addresses to a group/folder

Similar to adding mailing list folders you can also add specified email addresses into a group/folder.

ssh username@domainname -p 2222
freedombone-addemail -e <email address> -g <group name>
exit

The group name should be something short so that it is readable within the left side column of the mutt email client, and not contain any spaces. You can also use the freedombone-rmemail command to remove an email address rule.

Ignoring incoming emails

It is possible to ignore incoming emails if they are from a particular email address or if the subject line contains particular text.

ssh username@domainname -p 2222
freedombone-ignore -e baduser@baddomain
exit

Or:

ssh username@domainname -p 2222
freedombone-ignore -t "make $$$ now!"
exit

You can also reverse this by using the freedombone-unignore command with the same options.

Mailing List

If you want to set up a public mailing list then when installing the system remember to set the PUBLIC_MAILING_LIST variable within freedombone.cfg to the name of your list. The name should have no spaces in it. Public mailing lists are unencrypted so anyone will be able to read the contents, including non subscribers.

To subscribe to your list send a cleartext email to:

mymailinglistname+subscribe@domainname

Tip: When using the Mutt email client if you want to send an email in cleartext then press p (for PGP) on the sending screen and select clear. Unsecure email is treated as being the exception rather than the default.

Syncing to the Cloud

Initial install

Within a browser go to your owncloud domain, then create an administrator account. The username and password can be anything, and ideally should be generated from a password manager.

You will also need to enter database details:

Owncloud database user	owncloudadmin
Owncloud database password	See the /free/freedombone/src/commit/071527b45d85766a70cf8a2eee76f82b1c4c9f0a/doc/EN/Readme file
Owncloud database name	owncloud

After creating an administrator account then create a user account via the Users dropdown menu entry on the right hand side and log the details in a password manager. Give the user a quota suitable for the size of your microSD card or other storage.

Log out from the administrator account and then log back in as the user you just created.

On Android

Within F-droid search for owncloud and install the client. Also install CalDAV Sync Adapter.

Open the owncloud app and enter your owncloud domain name (including the https prefix) and login details for the user you created.

Open the calendar app (S planner) and under settings select Calendars then Add account then CalDAV Sync Adapter. Enter your owncloud username and password and the following URL:

https://myownclouddomain/remote.php/caldav/principals/myowncloudusername

You will also be prompted to enter login details. Your Android and Owncloud calendars should now be synchronised.

On Linux

Open your software center and search for "owncloud client". Enter your owncloud domain name (with the https prefix) and login details.

You can now drag files into the ~/owncloud directory and they will automatically sync to your server. It's that easy.

Play Music

With the DLNA service

An easy way to play music on any mobile device in your home is to use the DLNA service. Copy your music into a directory called "Music" on a USB thumb drive and then insert it into from socket on the Beaglebone.

ssh into the system with:

ssh myusername@mydomain.com -p 2222

Then mount the USB drive with:

su
attach-music

The system will scan the Music directory, which could take a while if there are thousands of files, but you don't need to do anything further with the Beaglebone other than perhaps to log out by typing exit a couple of times.

If you have an Android device then go to F-Droid (if you don't already have it installed then it can be downloaded here) and search for ControlDLNA. On running the app you should see a red Debian icon which you can press on, then you may need to select "local". After a few seconds the list of albums or tracks should then appear and you can browse and play them.

The DLNA service will only work within your local home network, and isn't remotely accessible from other locations via the internet. That can be both a good and a bad thing. Another consideration is that there are no access controls on DLNA services, so any music or videos on the USB drive will be playable by anyone within your home network. If you need to restrict access to certain files then it may be better to use the music player within Owncloud.

With Owncloud

The main advantage of playing music via Owncloud is that you can do that from anywhere - not only within your home network.

By default a music player is installed into Owncloud, so all you need to do is to visit your Owncloud web site, select the music directory and then upload some music files. Afterwards you can select the music icon from the top left drop down menu and albums will then appear which can be played. If you want to share music with other users then you can select the share option from within the files view to make the tracks available.

Microblogging

Initial configuration

To set up your microblog go to:

https://yourmicroblogdomainname/install.php

and enter the following settings:

Server SSL	enable
Hostname	localhost
Type	MySql/MariaDB
Name	gnusocial
DB username	root
DB Password	See the MariaDB password in the /free/freedombone/src/commit/071527b45d85766a70cf8a2eee76f82b1c4c9f0a/doc/EN/Readme file
Administrator nickname	Your username
Administrator password	See the /free/freedombone/src/commit/071527b45d85766a70cf8a2eee76f82b1c4c9f0a/doc/EN/Readme file
Subscribe to announcements	ticked
Site profile	Community

When the install is complete you will see a lot of warnings but just ignore those and navigate to your microblog domain and you can then complete the configuration via the Admin section on the header bar. Some recommended admin settings are:

Site settings	Text limit 140, Dupe Limit 60000
User settings	Bio limit 1000
Access settings	Invite only ticked

Social Network

Certificates

You will need to have a non self-signed SSL certificate in order to use Hubzilla. Put the public certificate in /etc/ssl/certs/yourhubzilladomainname.crt and the private certificate in /etc/ssl/private/yourhubzilladomainname.key. If there is an intermediate certificate needed (such as with StartSSL) then this will need to be concatenated onto the end of the crt file, like this:

cat /etc/ssl/certs/yourhubzilladomainname.crt /etc/ssl/chains/startssl-sub.class1.server.ca.pem >
 /etc/ssl/certs/yourhubzilladomainname.bundle.crt

Then change ssl_certificate to /etc/ssl/certs/yourhubzilladomainname.bundle.crt within /etc/nginx/sites-available/yourhubzilladomainname

Initial install

Visit the URL of your Hubzilla site and you should be taken through the rest of the installation procedure. Note that this may take a few minutes so don't be concerned if it looks as if it has crashed - just leave it running.

When installation is complete you can register a new user.

Chat Services

IRC

IRC is useful for multi-user chat. The classic use case is for software development where many engineers might need to coordinate their activities, but it's also useful for meetings, parties and general socialising.

Irssi

If you are using the irssi IRC client then you can use the following commands to connect to your IRC server.

/server add -auto -ssl yourdomainname 6697
/connect yourdomainname
/join freedombone

XChat

If you are using the XChat client:

Within the network list click, Add and enter your domain name then click Edit.

Select the entry within the servers box, then enter mydomainname/6697 and press Enter.

Uncheck use global user information.

Enter first and second nicknames and check auto connect to this network on startup.

Check use SSL and accept invalid SSL certificate.

Enter #freedombone as the channel name.

Click close and then connect.

XMPP/Jabber

Managing users

To add a user:

ssh username@domainname -p 2222
su
freedombone-addxmpp -e newusername@newdomainname
exit
exit

To change a user password:

ssh username@domainname -p 2222
su
freedombone-xmpp-pass -e username@domainname
exit
exit

To remove a user:

ssh username@domainname -p 2222
su
freedombone-rmxmpp -e username@domainname
exit
exit

Report the status of the XMPP server:

ssh username@domainname -p 2222
su
prosodyctl status
exit
exit

Using with Jitsi

Jitsi is the recommended communications client for desktop or laptop systems, since it includes the off the record (OTR) feature which provides some additional security beyond the usual SSL certificates.

Jitsi can be downloaded from https://jitsi.org

On your desktop/laptop open Jitsi and select Options from the Tools menu.

Click Add to add a new user, then enter the Jabber ID which you previously specified with prosodyctl when setting up the XMPP server. Close and then you should notice that your status is "Online" (or if not then you should be able to set it to online).

From the File menu you can add contacts, then select the chat icon to begin a chat. Click on the lock icon on the right hand side and this will initiate an authentication procedure in which you can specify a question and answer to verify the identity of the person you're communicating with. Once authentication is complete then you'll be chating using OTR, which provides an additional layer of security.

When opening Jitsi initially you will get a certificate warning for your domain name (assuming that you're using a self-signed certificate). If this happens then select View Certificate and enable the checkbox to trust the certificate, then select Continue Anyway. Once you've done this then the certificate warning will not appear again unless you reinstall Jitsi or use a different computer.

You can also see this video as an example of using OTR.

Using with Ubuntu

The default XMPP client in Ubuntu is Empathy. Using Empathy isn't as secure as using Jitsi, since it doesn't include the off the record feature, but since it's the default it's what many users will have easy access to.

Open System Settings and select Online Accounts, Add account and then Jabber.

Enter your username (username@domainname) and password.

Click on Advanced and make sure that Encryption required and Ignore SSL certificate errors are checked. Ignoring the certificate errors will allow you to use the self-signed certificate created earlier. Then click Done and set your Jabber account and Empathy to On.

Using with Android

Install F-Droid

Search for and install Xabber.

Add an account and enter your Jabber/XMPP ID and password.

From the menu select Settings then Security then OTR mode. Set the mode to Required.

Make sure that Check server certificate is not checked.

Go back to the initial screen and then using the menu you can add contacts and begin chatting. Both parties will need to go through the off-the-record question and answer verification before the chat can begin, but that only needs to be done once for each person you're chatting with.

Tox

Tox is an encrypted peer-to-peer messaging system and so should work without Freedombone. It uses a system of nodes which act as a sort of directory service allowing users to find and connect to each other. The Tox node ID on the Freedombone can be found within the README within your home directory. If you have other users connect to your node then you will be able to continue chatting even when no other nodes are available.

Using the Toxic client

To connect to your node use the command:

/connect [yourdomainname] 33445 [your tox node ID]

VoIP (Voice chat)

Using with Ubuntu

Within the software center search for "mumble" and install the client then run it. Skip through the audio setup wizard.

Click on "add new" to add a new server and enter the default domain name for the Freedombone, your username (which can be anything) and the VoIP server password which can be found in the README file on the Freedombone. Accept the self-signed SSL certificate. You are now ready to chat.

Note: if you don't know the default domain name and you did a full installation then it will be the same as the wiki domain name.

Using with Android

Install F-Droid

Search for and install Plumble.

Press the plus button to add a Mumble server.

Enter a label (which can be any name you choose for the server), the default domain name of the Freedombone, your username (which can also be anything) and the VoIP server password which can be found in the README file on the Freedombone.

Selecting the server by pressing on it then connects you to the server so that you can chat with other connected users.

Note: if you don't know the default domain name and you did a full installation then it will be the same as the wiki domain name.

33 KiB Raw Blame History

Readme

Improving ssh security

Using Email

A technical note about email transport security

Add a password to your GPG key

Publishing your GPG public key

Mutt email client

Thunderbird/Icedove

Initial setup

Import your GPG keys

Using for the first time

Making folders visible

K9 Android client

A point about GPG on Android

Compiling the development version

Import your GPG key into OpenKeychain

Incoming server settings

Outgoing (SMTP) server settings

Crypto settings

Folders

Subscribing to mailing lists

Adding email addresses to a group/folder

Ignoring incoming emails

Mailing List

Syncing to the Cloud

Initial install

On Android

On Linux

Play Music

With the DLNA service

With Owncloud

Microblogging

Initial configuration

Social Network

Certificates

Initial install

Chat Services

IRC

Irssi

XChat

XMPP/Jabber

Managing users

Using with Jitsi

Using with Ubuntu

Using with Android

Tox

Using the Toxic client

VoIP (Voice chat)

Using with Ubuntu

Using with Android

33 KiB

Raw Blame History