Merge branch 'stretch' of https://github.com/bashrc/freedombone
This commit is contained in:
Bob Mottram
commit
6b0397e414
|
|
@ -30,6 +30,6 @@ This applies to messages for help, too; not only is a public support request muc
|
|||
|
||||
While this code of conduct should be adhered to by participants, we recognize that sometimes people may have a bad day, or be unaware of some of the guidelines in this code of conduct. When that happens, you may reply to them and point out this code of conduct. Such messages may be in public or in private, whatever is most appropriate. However, regardless of whether the message is public or not, it should still adhere to the relevant parts of this code of conduct; in particular, it should not be abusive or disrespectful. Assume good faith; it is more likely that participants are unaware of their bad behaviour than that they intentionally try to degrade the quality of the discussion.
|
||||
|
||||
Serious or persistent offenders will be kicked from chat rooms and any of their subsequent patches will be unlikely to be upstreamed.
|
||||
Serious or persistent offenders will be kicked from chat rooms and any of their subsequent patches will be unlikely to be upstreamed. In this context "serious" means that someone is causing others to feel unsafe or be unable to contribute, for whatever reason.
|
||||
|
||||
Complaints should be made (in private) to the maintainer or chat room admin. The typical email address can be found in the source code headers. Preferably use GPG/OpenPGP if you can, or XMPP with OTR/OMEMO to bob@freedombone.net.
|
||||
This is not a big project and so there is no division of labor or special enforcement committee or bureaucratic process. Complaints should be made (in private) to the maintainer or chat room admin. The typical email address can be found in the source code headers. Preferably use GPG/OpenPGP if you can, or XMPP with OTR/OMEMO to bob@freedombone.net. XMPP messages are likely to get a quicker response.
|
||||
|
|
|
|||
|
|
@ -44,6 +44,6 @@ This applies to messages for help, too; not only is a public support request muc
|
|||
|
||||
While this code of conduct should be adhered to by participants, we recognize that sometimes people may have a bad day, or be unaware of some of the guidelines in this code of conduct. When that happens, you may reply to them and point out this code of conduct. Such messages may be in public or in private, whatever is most appropriate. However, regardless of whether the message is public or not, it should still adhere to the relevant parts of this code of conduct; in particular, it should not be abusive or disrespectful. Assume good faith; it is more likely that participants are unaware of their bad behaviour than that they intentionally try to degrade the quality of the discussion.
|
||||
|
||||
Serious or persistent offenders will be kicked from chat rooms and any of their subsequent patches will be unlikely to be upstreamed.
|
||||
Serious or persistent offenders will be kicked from chat rooms and any of their subsequent patches will be unlikely to be upstreamed. In this context "serious" means that someone is causing others to feel unsafe or be unable to contribute, for whatever reason.
|
||||
|
||||
Complaints should be made (in private) to the maintainer or chat room admin. The typical email address can be found in the source code headers. Preferably use GPG/OpenPGP if you can, or XMPP with OTR/OMEMO to bob@freedombone.net.
|
||||
This is not a big project and so there is no division of labor or special enforcement committee or bureaucratic process. Complaints should be made (in private) to the maintainer or chat room admin. The typical email address can be found in the source code headers. Preferably use GPG/OpenPGP if you can, or XMPP with OTR/OMEMO to bob@freedombone.net. XMPP messages are likely to get a quicker response.
|
||||
|
|
|
|||
|
|
@ -32,7 +32,6 @@
|
|||
| [[Can I add a clearnet domain to an onion build?]] |
|
||||
| [[Why use Github?]] |
|
||||
| [[Keys and emails should not be stored on servers. Why do you do that?]] |
|
||||
| [[./mirrors.html][I have a question about mirrors or upstream repositories]] |
|
||||
| [[Why can't I access my .onion site with a Tor browser?]] |
|
||||
| [[What is the best hardware to run this system on?]] |
|
||||
| [[Can I add more users to the system?]] |
|
||||
|
|
@ -91,13 +90,16 @@ The FreedomBox project supports Raspberry Pi builds, and the image build system
|
|||
|
||||
So although the Raspberry Pi is cheap and hugely popular it's not supported by the Freedombone project. Perhaps future versions of the Pi won't have the proprietary blob requirement, or maybe the blob will be open sourced at some stage.
|
||||
* Why use Tor? I've heard it's used by bad people
|
||||
Before you run screaming for the hills based upon whatever scare story you may have just read in the mainstream media there are a few things worthy of consideration. Tor is installed by default on Freedombone, /but not as a relay or exit node/. It's only used to provide onion addresses so that this gives you or the viewers of your sites some choice about how they access the information. It also allows you to subscribe to and read RSS feeds privately.
|
||||
Years ago Tor was usually depicted in the mainstream media as something scary inhabited by cyberterrorists and other bad cybers, but today to a large extent Tor is accepted as just another way of routing data in a network. Depending upon where you live there may still be some amount of fearmongering about Tor, but it now seems clear that the trajectory is towards general acceptance.
|
||||
|
||||
Onion routing - which is what Tor provides - gives you some level of protection against bulk surveillance of metadata. These days governments and other organisations are in the business of collecting and analysing your metadata. They want to have comprehensive lists of which sites you visited, or who visited your sites. Tor may at least partially help to thwart their totalitarian ambitions to know everything about everyone all of the time.
|
||||
Tor and its onion addresses, previously called hidden addresses, have a few key advantages:
|
||||
|
||||
Tor is not a perfect system and is not fully decentralised. Like all software it has bugs, but it can be considered to probably be an effective tactic against some of the most egregious surveillance fanatics out there.
|
||||
* NAT traversal
|
||||
* Firewall traversal
|
||||
* Avoiding the domain name system (DNS), which is mostly centralized and not secure
|
||||
* Avoiding passive bulk surveillance in which governments try to find out who is communicating with who
|
||||
|
||||
The media may also have sold you torrid tales about individual Tor project developers. While the conduct of individuals does matter, what matters far more is whether the technical system works and is practical for the average user. Don't allow your opinions of the technical system to be deflected by transient sex scandals or oppressive moralising, and /don't hold anyone to standards higher than you would apply to yourself/.
|
||||
On the negative side it's a complex system which is not fully decentralized.
|
||||
* How is Tor integrated with Freedombone?
|
||||
Within this project Tor is used more to provide /accessibility/ than the /anonymity/ factor for which Tor is better known. The onion address system provides a way of being able to access sites even if you don't own a conventional domain name or don't have administrator access to your local internet router to be able to do port forwarding.
|
||||
|
||||
|
|
@ -115,7 +117,7 @@ At present Github is useful just because of the sheer number of eyeballs and the
|
|||
|
||||
The source code for this project is experimentally independently hosted, and it is expected that in future the main development will shift over to an independent site, maybe with mirrors on Github if it still exists in a viable form.
|
||||
|
||||
Currently many of the repositories used for applications which are not yet packaged for Debian are on Github, and to provide some degree of resilliance against depending too much upon that it's possible to use [[./mirrors.html][mirrors stored on another server]].
|
||||
Currently many of the repositories used for applications which are not yet packaged for Debian are on Github, and to provide some degree of resilliance against depending too much upon that copies of them also exist within disk images.
|
||||
* Keys and emails should not be stored on servers. Why do you do that?
|
||||
Ordinarily this is good advice. However, the threat model for a device in your home is different from the one for a generic server in a massive warehouse. Compare and contrast:
|
||||
|
||||
|
|
|
|||
|
|
@ -23,7 +23,7 @@ The Freedombone Mesh is a wireless solution for autonomous or internet connected
|
|||
* [[./mesh_usage.html][How to use it]]
|
||||
|
||||
#+BEGIN_CENTER
|
||||
[[file:images/mesh_logo.jpg]]
|
||||
[[file:images/mesh_desktop1.png]]
|
||||
#+END_CENTER
|
||||
|
||||
Mesh networks are useful as a quick way to make a fully decentralised communications system which is not connected to or reliant upon the internet. Think festivals, hacker conferences, onboard ships at sea, disaster/war zones, small businesses who don't want the overhead of server maintenance, protests, remote areas of the world, temporary "digital blackouts", scientific expeditions and off-world space colonies.
|
||||
|
|
|
|||
|
|
@ -61,7 +61,7 @@ wget https://freedombone.net/downloads/current/freedombone-meshclient-insecure-i
|
|||
wget https://freedombone.net/downloads/current/freedombone-meshclient-insecure-i386.img.xz.sig
|
||||
gpg --verify freedombone-meshclient-insecure-i386.img.xz.sig
|
||||
sha256sum freedombone-meshclient-insecure-i386.img.xz
|
||||
066ef17f90078de8ae85807fa0207f5e3b994a74442cb0683a3bbce1a1b6253b
|
||||
c11783741e66df5072ffcbef8d9b04260a2298d84e33c72fefa4bb539d094810
|
||||
unxz freedombone-meshclient-insecure-i386.img.xz
|
||||
sudo dd if=/dev/zero of=/dev/sdX bs=1M count=8
|
||||
sudo dd bs=1M if=freedombone-meshclient-insecure-i386.img of=/dev/sdX conv=fdatasync
|
||||
|
|
@ -102,7 +102,7 @@ wget https://freedombone.net/downloads/current/freedombone.tar.gz
|
|||
wget https://freedombone.net/downloads/current/freedombone.tar.gz.sig
|
||||
gpg --verify freedombone.tar.gz.sig
|
||||
sha256sum freedombone.tar.gz
|
||||
|
||||
afbb536564140aa28c6491d45b7474ced5a0b018539ffd3e96b13b242a41792e
|
||||
tar -xzvf freedombone.tar.gz
|
||||
cd freedombone
|
||||
git checkout stretch
|
||||
|
|
|
|||
|
|
@ -0,0 +1,55 @@
|
|||
-- OMEMO all access module
|
||||
-- Copyright (c) 2017 Daniel Gultsch
|
||||
--
|
||||
-- This module is MIT/X11 licensed
|
||||
--
|
||||
|
||||
local jid_bare = require "util.jid".bare;
|
||||
local st = require "util.stanza"
|
||||
local white_listed_namespace = "eu.siacs.conversations.axolotl."
|
||||
local disco_feature_namespace = white_listed_namespace .. "whitelisted"
|
||||
|
||||
local mod_pep = module:depends"pep";
|
||||
local pep_data = mod_pep.module.save().data;
|
||||
|
||||
local function on_account_disco_info(event)
|
||||
(event.reply or event.stanza):tag("feature", {var=disco_feature_namespace}):up();
|
||||
end
|
||||
|
||||
local function on_pep_request(event)
|
||||
local session, stanza = event.origin, event.stanza
|
||||
local payload = stanza.tags[1];
|
||||
if stanza.attr.type == 'get' then
|
||||
local node, requested_id;
|
||||
payload = payload.tags[1]
|
||||
if payload and payload.name == 'items' then
|
||||
node = payload.attr.node
|
||||
local item = payload.tags[1];
|
||||
if item and item.name == 'item' then
|
||||
requested_id = item.attr.id;
|
||||
end
|
||||
end
|
||||
if node and string.sub(node,1,string.len(white_listed_namespace)) == white_listed_namespace then
|
||||
local user = stanza.attr.to and jid_bare(stanza.attr.to) or session.username..'@'..session.host;
|
||||
local user_data = pep_data[user];
|
||||
if user_data and user_data[node] then
|
||||
local id, item = unpack(user_data[node]);
|
||||
if not requested_id or id == requested_id then
|
||||
local stanza = st.reply(stanza)
|
||||
:tag('pubsub', {xmlns='http://jabber.org/protocol/pubsub'})
|
||||
:tag('items', {node=node})
|
||||
:add_child(item)
|
||||
:up()
|
||||
:up();
|
||||
session.send(stanza);
|
||||
module:log("debug","provided access to omemo node",node)
|
||||
return true;
|
||||
end
|
||||
end
|
||||
module:log("debug","requested node was white listed", node)
|
||||
end
|
||||
end
|
||||
end
|
||||
|
||||
module:hook("iq/bare/http://jabber.org/protocol/pubsub:pubsub", on_pep_request, 10);
|
||||
module:hook("account-disco-info", on_account_disco_info);
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 103 KiB After Width: | Height: | Size: 87 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 118 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 9.9 KiB After Width: | Height: | Size: 7.8 KiB |
|
|
@ -42,7 +42,7 @@ IPFS_N_VERSION='2.1.4'
|
|||
IPFS_JS_VERSION='0.14.3'
|
||||
IPFS_JS_RONIN_VERSION='0.3.11'
|
||||
IPFS_KEY_LENGTH=2048
|
||||
IPFS_GO_VERSION=0.4.2
|
||||
IPFS_GO_VERSION=0.4.13
|
||||
|
||||
ipfs_variables=(IPFS_GO_VERSION
|
||||
IPFS_KEY_LENGTH
|
||||
|
|
@ -451,11 +451,14 @@ function mesh_install_ipfs_go {
|
|||
|
||||
echo '[Unit]' > $IPFS_USER_DAEMON
|
||||
echo 'Description=IPFS go daemon' >> $IPFS_USER_DAEMON
|
||||
echo 'After=syslog.target' >> $IPFS_USER_DAEMON
|
||||
echo 'After=network.target' >> $IPFS_USER_DAEMON
|
||||
echo '' >> $IPFS_USER_DAEMON
|
||||
echo '[Service]' >> $IPFS_USER_DAEMON
|
||||
echo 'Type=simple' >> $IPFS_USER_DAEMON
|
||||
echo "ExecStart=$IPFS_PATH/ipfs daemon" >> $IPFS_USER_DAEMON
|
||||
echo 'Restart=on-failure' >> $IPFS_USER_DAEMON
|
||||
echo 'RestartSec=10' >> $IPFS_USER_DAEMON
|
||||
echo 'RestartSec=60' >> $IPFS_USER_DAEMON
|
||||
echo '' >> $IPFS_USER_DAEMON
|
||||
echo '[Install]' >> $IPFS_USER_DAEMON
|
||||
echo 'WantedBy=default.target' >> $IPFS_USER_DAEMON
|
||||
|
|
@ -539,6 +542,7 @@ function install_ipfs_go {
|
|||
fi
|
||||
|
||||
# initialise
|
||||
chmod 755 $IPFS_PATH/ipfs
|
||||
su -c "$IPFS_PATH/ipfs init -b 2048" - $MY_USERNAME
|
||||
if [ ! -d /home/$MY_USERNAME/.ipfs ]; then
|
||||
echo "IPFS could not be initialised for user $MY_USERNAME"
|
||||
|
|
|
|||
|
|
@ -49,6 +49,15 @@ pelican_variables=(MY_USERNAME
|
|||
PELICAN_DOMAIN_NAME
|
||||
PELICAN_BLOG_CODE)
|
||||
|
||||
function pelican_remove_bad_blog_links {
|
||||
find ./ -type f -name *.css -exec sed -i -e '/googleapi/d' {} \;
|
||||
find ./ -type f -name *.scss -exec sed -i -e '/googleapi/d' {} \;
|
||||
find ./ -type f -name *.html -exec sed -i -e '/googleapi/d' {} \;
|
||||
find ./ -type f -name *.css -exec sed -i -e '/bootstrapcdn/d' {} \;
|
||||
find ./ -type f -name *.scss -exec sed -i -e '/bootstrapcdn/d' {} \;
|
||||
find ./ -type f -name *.html -exec sed -i -e '/bootstrapcdn/d' {} \;
|
||||
}
|
||||
|
||||
function logging_on_pelican {
|
||||
echo -n ''
|
||||
}
|
||||
|
|
@ -275,13 +284,6 @@ function pelican_delete_blog {
|
|||
esac
|
||||
}
|
||||
|
||||
function pelican_remove_bad_blog_links {
|
||||
current_theme=$1
|
||||
if [ -f $PELICAN_BLOG_INSTALL_DIR/themes/$current_theme/static/css/style.css ]; then
|
||||
sed -i '/googleapi/d' $PELICAN_BLOG_INSTALL_DIR/themes/$current_theme/static/css/style.css
|
||||
fi
|
||||
}
|
||||
|
||||
function pelican_change_theme {
|
||||
THEMES=()
|
||||
for d in $PELICAN_BLOG_INSTALL_DIR/themes/*/ ; do
|
||||
|
|
@ -330,7 +332,10 @@ function pelican_change_theme {
|
|||
CHOSEN_THEME_INDEX=$((CHOSEN_THEME_INDEX - 1))
|
||||
|
||||
CHOSEN_THEME=${THEMES[$CHOSEN_THEME_INDEX]}
|
||||
pelican_remove_bad_blog_links $CHOSEN_THEME
|
||||
|
||||
cd $PELICAN_BLOG_INSTALL_DIR/themes/$CHOSEN_THEME
|
||||
pelican_remove_bad_blog_links
|
||||
|
||||
if grep -q "THEME=" $PELICAN_BLOG_INSTALL_DIR/pelicanconf.py; then
|
||||
sed -i "s|THEME=.*|THEME='themes/${CHOSEN_THEME}'|g" $PELICAN_BLOG_INSTALL_DIR/pelicanconf.py
|
||||
else
|
||||
|
|
@ -742,13 +747,7 @@ function pelican_themes {
|
|||
git clone https://github.com/jarv/water-iris
|
||||
git clone https://github.com/kplaube/yapeme
|
||||
|
||||
# remove any dubious css
|
||||
for d in */ ; do
|
||||
THEME_NAME=$(echo "$d" | awk -F '/' '{print $1}')
|
||||
if [ -d $d/static/css/style.css ]; then
|
||||
sed -i '/googleapi/d' $d/static/css/style.css
|
||||
fi
|
||||
done
|
||||
pelican_remove_bad_blog_links
|
||||
}
|
||||
|
||||
function mesh_install_pelican {
|
||||
|
|
|
|||
|
|
@ -330,6 +330,8 @@ function install_riot {
|
|||
|
||||
sed '/Content-Security-Policy/d' $riot_nginx_site
|
||||
sed -i 's| DENY;| SAMEORIGIN;|g' $riot_nginx_site
|
||||
sed -i 's|limit_conn conn_limit_per_ip.*|limit_conn conn_limit_per_ip 50;|g' $riot_nginx_site
|
||||
sed -i 's|limit_req zone.*|limit_req zone=req_limit_per_ip burst=20 nodelay;|g' $riot_nginx_site
|
||||
|
||||
function_check create_site_certificate
|
||||
if [ ! -f /etc/ssl/certs/${RIOT_DOMAIN_NAME}.pem ]; then
|
||||
|
|
|
|||
|
|
@ -326,6 +326,46 @@ function update_prosody_modules {
|
|||
return
|
||||
fi
|
||||
|
||||
# This module is a workaround for OMEMO within group chat
|
||||
# See https://github.com/iNPUTmice/omemo_all_access
|
||||
if [ -f ~/freedombone/image_build/mod_omemo_all_access.lua ]; then
|
||||
if [ ! -d /var/lib/prosody/prosody-modules ]; then
|
||||
mkdir -p /var/lib/prosody/prosody-modules
|
||||
fi
|
||||
|
||||
copy_omemo_all_access=1
|
||||
if [ -f /usr/lib/prosody/modules/mod_omemo_all_access.lua ]; then
|
||||
curr_hash=$(sha256sum /usr/lib/prosody/modules/mod_omemo_all_access.lua)
|
||||
new_hash=$(sha256sum ~/freedombone/image_build/mod_omemo_all_access.lua)
|
||||
if [[ "$curr_hash" == "$new_hash" ]]; then
|
||||
copy_omemo_all_access=
|
||||
fi
|
||||
fi
|
||||
|
||||
if [ $copy_omemo_all_access ]; then
|
||||
systemctl stop prosody
|
||||
cp ~/freedombone/image_build/mod_omemo_all_access.lua /var/lib/prosody/prosody-modules/mod_omemo_all_access.lua
|
||||
cp ~/freedombone/image_build/mod_omemo_all_access.lua /usr/lib/prosody/modules/mod_omemo_all_access.lua
|
||||
|
||||
chmod +x /var/lib/prosody/prosody-modules/mod_omemo_all_access.lua
|
||||
chmod +x /usr/lib/prosody/modules/mod_omemo_all_access.lua
|
||||
|
||||
if ! grep -q "omemo_all_access" /etc/prosody/prosody.cfg.lua; then
|
||||
sed -i '/"pep";/a "omemo_all_access"; -- Fix for PEP with OMEMO' /etc/prosody/prosody.cfg.lua
|
||||
sed -i 's|"omemo_all_access";| "omemo_all_access";|g' /etc/prosody/prosody.cfg.lua
|
||||
fi
|
||||
|
||||
if ! grep -q "omemo_all_access" /etc/prosody/conf.avail/xmpp.cfg.lua; then
|
||||
sed -i '/"pep";/a "omemo_all_access"; -- Fix for PEP with OMEMO' /etc/prosody/conf.avail/xmpp.cfg.lua
|
||||
sed -i 's|"omemo_all_access";| "omemo_all_access";|g' /etc/prosody/conf.avail/xmpp.cfg.lua
|
||||
fi
|
||||
|
||||
chown -R prosody:prosody /var/lib/prosody/prosody-modules
|
||||
chown -R prosody:prosody /usr/lib/prosody/modules
|
||||
systemctl start prosody
|
||||
fi
|
||||
fi
|
||||
|
||||
if [ ! -f $INSTALL_DIR/$prosody_modules_filename ]; then
|
||||
# Obtain the modules
|
||||
if [ -f ~/freedombone/image_build/$prosody_modules_filename ]; then
|
||||
|
|
@ -624,6 +664,7 @@ function xmpp_modules {
|
|||
echo ' "smacks"; -- Stream management' >> $filename
|
||||
echo ' "smacks_offline"; -- Stream management' >> $filename
|
||||
echo ' "pep"; -- Personal Eventing Protocol (to support OMEMO)' >> $filename
|
||||
echo ' "omemo_all_access"; -- Fix for PEP with OMEMO' >> $filename
|
||||
echo ' "vcard"; -- Personal Eventing Protocol (to support OMEMO)' >> $filename
|
||||
echo ' "e2e_policy"; -- To support OMEMO' >> $filename
|
||||
echo ' "pep_vcard_avatar"; -- Personal Eventing Protocol (to support OMEMO)' >> $filename
|
||||
|
|
|
|||
|
|
@ -985,6 +985,7 @@ function setup_ipfs {
|
|||
IPFS_COMMAND=$IPFS_PATH/ipfs
|
||||
IPFS_PUBLIC=/home/$MY_USERNAME/.ipfs-public
|
||||
|
||||
chmod 755 $IPFS_COMMAND
|
||||
su -c "systemctl --user enable ipfs" - $MY_USERNAME
|
||||
|
||||
if [ -f $CURRENT_BLOG_INDEX ]; then
|
||||
|
|
@ -1033,6 +1034,7 @@ function setup_ipfs {
|
|||
shred -zu /home/$MY_USERNAME/.ipfs-public
|
||||
fi
|
||||
|
||||
chmod 755 $IPFS_COMMAND
|
||||
su -c "$IPFS_COMMAND init -b $IPFS_KEY_LENGTH" - $MY_USERNAME
|
||||
if [ ! -d /home/$MY_USERNAME/.ipfs ]; then
|
||||
echo "IPFS could not be initialised for user $MY_USERNAME" >> $INSTALL_LOG
|
||||
|
|
|
|||
|
|
@ -42,10 +42,12 @@ BLOG_EDITOR='pluma'
|
|||
DEFAULT_BLOG_TITLE=$"Freedombone Blog"
|
||||
|
||||
function remove_bad_blog_links {
|
||||
current_theme=$1
|
||||
if [ -f $BLOG_PATH/themes/$current_theme/static/css/style.css ]; then
|
||||
sed -i '/googleapi/d' $BLOG_PATH/themes/$current_theme/static/css/style.css
|
||||
fi
|
||||
find ./ -type f -name *.css -exec sed -i -e '/googleapi/d' {} \;
|
||||
find ./ -type f -name *.scss -exec sed -i -e '/googleapi/d' {} \;
|
||||
find ./ -type f -name *.html -exec sed -i -e '/googleapi/d' {} \;
|
||||
find ./ -type f -name *.css -exec sed -i -e '/bootstrapcdn/d' {} \;
|
||||
find ./ -type f -name *.scss -exec sed -i -e '/bootstrapcdn/d' {} \;
|
||||
find ./ -type f -name *.html -exec sed -i -e '/bootstrapcdn/d' {} \;
|
||||
}
|
||||
|
||||
function ipfs_publish {
|
||||
|
|
@ -80,6 +82,10 @@ function regenerate_blog {
|
|||
sed -i "s|SITENAME=.*|SITENAME=u\"${BLOG_TITLE}\"|g" $BLOG_PATH/pelicanconf.py
|
||||
fi
|
||||
make html
|
||||
|
||||
cd $BLOG_PATH
|
||||
remove_bad_blog_links
|
||||
|
||||
ipfs_publish
|
||||
}
|
||||
|
||||
|
|
@ -206,7 +212,8 @@ function change_theme {
|
|||
CHOSEN_THEME_INDEX=$((CHOSEN_THEME_INDEX - 1))
|
||||
|
||||
CHOSEN_THEME=${THEMES[$CHOSEN_THEME_INDEX]}
|
||||
remove_bad_blog_links $CHOSEN_THEME
|
||||
cd cd $BLOG_PATH/themes/$CHOSEN_THEME
|
||||
remove_bad_blog_links
|
||||
if grep -q "THEME=" $BLOG_PATH/pelicanconf.py; then
|
||||
sed -i "s|THEME=.*|THEME='themes/${CHOSEN_THEME}'|g" $BLOG_PATH/pelicanconf.py
|
||||
else
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@
|
|||
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
|
||||
<head>
|
||||
<!-- 2017-12-20 Wed 12:45 -->
|
||||
<!-- 2017-12-29 Fri 10:25 -->
|
||||
<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1" />
|
||||
<title>‎</title>
|
||||
|
|
@ -246,27 +246,27 @@ for the JavaScript code in this tag.
|
|||
|
||||
<center><h1>Code of Conduct</h1></center>
|
||||
|
||||
<div id="outline-container-orga839710" class="outline-2">
|
||||
<h2 id="orga839710">Be respectful</h2>
|
||||
<div class="outline-text-2" id="text-orga839710">
|
||||
<div id="outline-container-org7389049" class="outline-2">
|
||||
<h2 id="org7389049">Be respectful</h2>
|
||||
<div class="outline-text-2" id="text-org7389049">
|
||||
<p>
|
||||
In any Free Software project with more than one participant inevitably there may be people with whom you may disagree, or find it difficult to cooperate. Accept that, but even so, remain respectful. Disagreement is no excuse for poor behaviour or personal attacks, and a community in which people feel threatened is not a healthy community.
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div id="outline-container-org890f143" class="outline-2">
|
||||
<h2 id="org890f143">Assume good faith</h2>
|
||||
<div class="outline-text-2" id="text-org890f143">
|
||||
<div id="outline-container-orgb4a8701" class="outline-2">
|
||||
<h2 id="orgb4a8701">Assume good faith</h2>
|
||||
<div class="outline-text-2" id="text-orgb4a8701">
|
||||
<p>
|
||||
Freedombone Contributors have many ways of reaching our common goal of providing freedom respecting internet or mesh systems which may differ from your ways. Assume that other people are working towards this goal.
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
<div id="outline-container-orgccafefb" class="outline-2">
|
||||
<h2 id="orgccafefb">Be collaborative</h2>
|
||||
<div class="outline-text-2" id="text-orgccafefb">
|
||||
<div id="outline-container-org323e1d5" class="outline-2">
|
||||
<h2 id="org323e1d5">Be collaborative</h2>
|
||||
<div class="outline-text-2" id="text-org323e1d5">
|
||||
<p>
|
||||
Freedombone is a moderately complex project, though nothing big and professional like GNU. It's good to ask for help when you need it. Similarly, offers for help should be seen in the context of our shared goal of improving the system.
|
||||
</p>
|
||||
|
|
@ -277,9 +277,9 @@ When you make something for the benefit of the project, be willing to explain to
|
|||
</div>
|
||||
</div>
|
||||
|
||||
<div id="outline-container-org960241b" class="outline-2">
|
||||
<h2 id="org960241b">Try to be concise</h2>
|
||||
<div class="outline-text-2" id="text-org960241b">
|
||||
<div id="outline-container-org2247eb7" class="outline-2">
|
||||
<h2 id="org2247eb7">Try to be concise</h2>
|
||||
<div class="outline-text-2" id="text-org2247eb7">
|
||||
<p>
|
||||
If you're submitting documentation then keep in mind that what you write once could be read by many other people. To avoid TL;DR keep it as short and concise as possible. This will also reduce the amount of translations effort needed.
|
||||
</p>
|
||||
|
|
@ -290,9 +290,9 @@ If you're discussing an issue or bug, try to stay on topic, especially in discus
|
|||
</div>
|
||||
</div>
|
||||
|
||||
<div id="outline-container-orgd3249bd" class="outline-2">
|
||||
<h2 id="orgd3249bd">Be open</h2>
|
||||
<div class="outline-text-2" id="text-orgd3249bd">
|
||||
<div id="outline-container-org9d2afa5" class="outline-2">
|
||||
<h2 id="org9d2afa5">Be open</h2>
|
||||
<div class="outline-text-2" id="text-org9d2afa5">
|
||||
<p>
|
||||
Most ways of communication used within Freedombone (eg Matrix/XMPP) allow for public and private communication. Prefer public methods of communication for Freedombone-related messages, unless posting something sensitive.
|
||||
</p>
|
||||
|
|
@ -303,19 +303,19 @@ This applies to messages for help, too; not only is a public support request muc
|
|||
</div>
|
||||
</div>
|
||||
|
||||
<div id="outline-container-org8f9612f" class="outline-2">
|
||||
<h2 id="org8f9612f">In case of problems</h2>
|
||||
<div class="outline-text-2" id="text-org8f9612f">
|
||||
<div id="outline-container-orgeac99f0" class="outline-2">
|
||||
<h2 id="orgeac99f0">In case of problems</h2>
|
||||
<div class="outline-text-2" id="text-orgeac99f0">
|
||||
<p>
|
||||
While this code of conduct should be adhered to by participants, we recognize that sometimes people may have a bad day, or be unaware of some of the guidelines in this code of conduct. When that happens, you may reply to them and point out this code of conduct. Such messages may be in public or in private, whatever is most appropriate. However, regardless of whether the message is public or not, it should still adhere to the relevant parts of this code of conduct; in particular, it should not be abusive or disrespectful. Assume good faith; it is more likely that participants are unaware of their bad behaviour than that they intentionally try to degrade the quality of the discussion.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
Serious or persistent offenders will be kicked from chat rooms and any of their subsequent patches will be unlikely to be upstreamed.
|
||||
Serious or persistent offenders will be kicked from chat rooms and any of their subsequent patches will be unlikely to be upstreamed. In this context "serious" means that someone is causing others to feel unsafe or be unable to contribute, for whatever reason.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
Complaints should be made (in private) to the maintainer or chat room admin. The typical email address can be found in the source code headers. Preferably use GPG/OpenPGP if you can, or XMPP with OTR/OMEMO to bob@freedombone.net.
|
||||
This is not a big project and so there is no division of labor or special enforcement committee or bureaucratic process. Complaints should be made (in private) to the maintainer or chat room admin. The typical email address can be found in the source code headers. Preferably use GPG/OpenPGP if you can, or XMPP with OTR/OMEMO to bob@freedombone.net. XMPP messages are likely to get a quicker response.
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@
|
|||
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
|
||||
<head>
|
||||
<!-- 2017-11-11 Sat 18:24 -->
|
||||
<!-- 2017-12-30 Sat 15:48 -->
|
||||
<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1" />
|
||||
<title>‎</title>
|
||||
|
|
@ -264,143 +264,139 @@ for the JavaScript code in this tag.
|
|||
</colgroup>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td class="org-left"><a href="#orgf3ee5ce">What applications are supported?</a></td>
|
||||
<td class="org-left"><a href="#org416597b">What applications are supported?</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td class="org-left"><a href="#orgec76339">I don't have a static IP address. Can I still install this system?</a></td>
|
||||
<td class="org-left"><a href="#org719e222">I don't have a static IP address. Can I still install this system?</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td class="org-left"><a href="#org2da13bd">Why Freedombone and not FreedomBox?</a></td>
|
||||
<td class="org-left"><a href="#org997ae78">Why Freedombone and not FreedomBox?</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td class="org-left"><a href="#orgd530659">Why not support building images for Raspberry Pi?</a></td>
|
||||
<td class="org-left"><a href="#org0fe5706">Why not support building images for Raspberry Pi?</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td class="org-left"><a href="#org4bb2842">Why use Tor? I've heard it's used by bad people</a></td>
|
||||
<td class="org-left"><a href="#orgf565b16">Why use Tor? I've heard it's used by bad people</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td class="org-left"><a href="#org8f15beb">How is Tor integrated with Freedombone?</a></td>
|
||||
<td class="org-left"><a href="#orgac61490">How is Tor integrated with Freedombone?</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td class="org-left"><a href="#orgd33d165">Can I add a clearnet domain to an onion build?</a></td>
|
||||
<td class="org-left"><a href="#orgbe35250">Can I add a clearnet domain to an onion build?</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td class="org-left"><a href="#org8e4a27d">Why use Github?</a></td>
|
||||
<td class="org-left"><a href="#org1ea193b">Why use Github?</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td class="org-left"><a href="#org3cd5f2c">Keys and emails should not be stored on servers. Why do you do that?</a></td>
|
||||
<td class="org-left"><a href="#org7057def">Keys and emails should not be stored on servers. Why do you do that?</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td class="org-left"><a href="./mirrors.html">I have a question about mirrors or upstream repositories</a></td>
|
||||
<td class="org-left"><a href="#orge669711">Why can't I access my .onion site with a Tor browser?</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td class="org-left"><a href="#org97f01de">Why can't I access my .onion site with a Tor browser?</a></td>
|
||||
<td class="org-left"><a href="#orgdb3b7a6">What is the best hardware to run this system on?</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td class="org-left"><a href="#org49504c7">What is the best hardware to run this system on?</a></td>
|
||||
<td class="org-left"><a href="#orgf1c38a0">Can I add more users to the system?</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td class="org-left"><a href="#orgf3e781c">Can I add more users to the system?</a></td>
|
||||
<td class="org-left"><a href="#orgd32f191">Why not use Signal for mobile chat?</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td class="org-left"><a href="#orgb408729">Why not use Signal for mobile chat?</a></td>
|
||||
<td class="org-left"><a href="#org16a21bb">What is the most secure chat app to use on mobile?</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td class="org-left"><a href="#orgd117b08">What is the most secure chat app to use on mobile?</a></td>
|
||||
<td class="org-left"><a href="#org279eac7">How do I remove a user from the system?</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td class="org-left"><a href="#orgb5b2126">How do I remove a user from the system?</a></td>
|
||||
<td class="org-left"><a href="#org12ac09e">Why is logging for web sites turned off by default?</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td class="org-left"><a href="#org1ab944e">Why is logging for web sites turned off by default?</a></td>
|
||||
<td class="org-left"><a href="#org5e9d3c7">How do I reset the tripwire?</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td class="org-left"><a href="#org576c1da">How do I reset the tripwire?</a></td>
|
||||
<td class="org-left"><a href="#org0613054">Is metadata protected?</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td class="org-left"><a href="#org575438d">Is metadata protected?</a></td>
|
||||
<td class="org-left"><a href="#orgdf75721">How do I create email processing rules?</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td class="org-left"><a href="#org249cb8e">How do I create email processing rules?</a></td>
|
||||
<td class="org-left"><a href="#org5b21211">Why isn't dynamic DNS working?</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td class="org-left"><a href="#org0026d12">Why isn't dynamic DNS working?</a></td>
|
||||
<td class="org-left"><a href="#org929e4ae">How do I change my encryption settings?</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td class="org-left"><a href="#orgcf9314c">How do I change my encryption settings?</a></td>
|
||||
<td class="org-left"><a href="#org087d147">How do I get a domain name?</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td class="org-left"><a href="#org623845a">How do I get a domain name?</a></td>
|
||||
<td class="org-left"><a href="#org4bb381a">How do I get a "real" SSL/TLS/HTTPS certificate?</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td class="org-left"><a href="#org80ee241">How do I get a "real" SSL/TLS/HTTPS certificate?</a></td>
|
||||
<td class="org-left"><a href="#orgfbd420c">How do I renew a Let's Encrypt certificate?</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td class="org-left"><a href="#org8b85e62">How do I renew a Let's Encrypt certificate?</a></td>
|
||||
<td class="org-left"><a href="#orgdaf57b7">I tried to renew a Let's Encrypt certificate and it failed. What should I do?</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td class="org-left"><a href="#org6aba810">I tried to renew a Let's Encrypt certificate and it failed. What should I do?</a></td>
|
||||
<td class="org-left"><a href="#org9fde76d">Why not use the services of $company instead? They took the Seppuku pledge</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td class="org-left"><a href="#orgc65717c">Why not use the services of $company instead? They took the Seppuku pledge</a></td>
|
||||
<td class="org-left"><a href="#org71ce92c">Why does my email keep getting rejected as spam by Gmail/etc?</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td class="org-left"><a href="#org76affcf">Why does my email keep getting rejected as spam by Gmail/etc?</a></td>
|
||||
<td class="org-left"><a href="#org1bd542d">Tor is censored/blocked in my area. What can I do?</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td class="org-left"><a href="#org93992f5">Tor is censored/blocked in my area. What can I do?</a></td>
|
||||
<td class="org-left"><a href="#orgcf6a401">I want to block a particular domain from getting its content into my social network sites</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td class="org-left"><a href="#org92ebfd1">I want to block a particular domain from getting its content into my social network sites</a></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td class="org-left"><a href="#orgd38ad08">The mesh system doesn't boot from USB drive</a></td>
|
||||
<td class="org-left"><a href="#org39004fe">The mesh system doesn't boot from USB drive</a></td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
</div>
|
||||
|
||||
<div id="outline-container-orgf3ee5ce" class="outline-2">
|
||||
<h2 id="orgf3ee5ce">What applications are supported?</h2>
|
||||
<div class="outline-text-2" id="text-orgf3ee5ce">
|
||||
<div id="outline-container-org416597b" class="outline-2">
|
||||
<h2 id="org416597b">What applications are supported?</h2>
|
||||
<div class="outline-text-2" id="text-org416597b">
|
||||
<p>
|
||||
<a href="./apps.html">See here</a> for the complete list of apps. In addition to those as part of the base install you get an email server.
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
<div id="outline-container-orgec76339" class="outline-2">
|
||||
<h2 id="orgec76339">I don't have a static IP address. Can I still install this system?</h2>
|
||||
<div class="outline-text-2" id="text-orgec76339">
|
||||
<div id="outline-container-org719e222" class="outline-2">
|
||||
<h2 id="org719e222">I don't have a static IP address. Can I still install this system?</h2>
|
||||
<div class="outline-text-2" id="text-org719e222">
|
||||
<p>
|
||||
Yes. The minimum requirements are to have some hardware that you can install Debian onto and also that you have administrator access to your internet router so that you can forward ports to the system which has Freedombone installed.
|
||||
</p>
|
||||
|
|
@ -410,17 +406,17 @@ The lack of a static IP address can be worked around by using a dynamic DNS serv
|
|||
</p>
|
||||
</div>
|
||||
</div>
|
||||
<div id="outline-container-org2da13bd" class="outline-2">
|
||||
<h2 id="org2da13bd">Why Freedombone and not FreedomBox?</h2>
|
||||
<div class="outline-text-2" id="text-org2da13bd">
|
||||
<div id="outline-container-org997ae78" class="outline-2">
|
||||
<h2 id="org997ae78">Why Freedombone and not FreedomBox?</h2>
|
||||
<div class="outline-text-2" id="text-org997ae78">
|
||||
<p>
|
||||
When the project began in late 2013 the FreedomBox project seemed to be going nowhere, and was only designed to work with the DreamPlug hardware. There was some new hardware out - the Beaglebone Black - which could run Debian and was also a free hardware design so seemed more appropriate. Hence the name "Freedombone", being like FreedomBox but on a Beaglebone. There are some similarities and differences between the two projects:
|
||||
</p>
|
||||
</div>
|
||||
|
||||
<div id="outline-container-orgfb1ae01" class="outline-3">
|
||||
<h3 id="orgfb1ae01">Similarities</h3>
|
||||
<div class="outline-text-3" id="text-orgfb1ae01">
|
||||
<div id="outline-container-org33179aa" class="outline-3">
|
||||
<h3 id="org33179aa">Similarities</h3>
|
||||
<div class="outline-text-3" id="text-org33179aa">
|
||||
<ul class="org-ul">
|
||||
<li>Uses freedom-maker and vmdebootstrap to build debian images</li>
|
||||
<li>Supports the use of Tor onion addresses to access websites</li>
|
||||
|
|
@ -434,9 +430,9 @@ When the project began in late 2013 the FreedomBox project seemed to be going no
|
|||
</ul>
|
||||
</div>
|
||||
</div>
|
||||
<div id="outline-container-orgea61850" class="outline-3">
|
||||
<h3 id="orgea61850">Differences</h3>
|
||||
<div class="outline-text-3" id="text-orgea61850">
|
||||
<div id="outline-container-orgc193b4e" class="outline-3">
|
||||
<h3 id="orgc193b4e">Differences</h3>
|
||||
<div class="outline-text-3" id="text-orgc193b4e">
|
||||
<ul class="org-ul">
|
||||
<li>FreedomBox is a Debian pure blend. Freedombone is not</li>
|
||||
<li>Freedombone only supports Free Software. FreedomBox includes some closed binary boot blobs for certain ARM boards</li>
|
||||
|
|
@ -451,9 +447,9 @@ When the project began in late 2013 the FreedomBox project seemed to be going no
|
|||
</div>
|
||||
</div>
|
||||
</div>
|
||||
<div id="outline-container-orgd530659" class="outline-2">
|
||||
<h2 id="orgd530659">Why not support building images for Raspberry Pi?</h2>
|
||||
<div class="outline-text-2" id="text-orgd530659">
|
||||
<div id="outline-container-org0fe5706" class="outline-2">
|
||||
<h2 id="org0fe5706">Why not support building images for Raspberry Pi?</h2>
|
||||
<div class="outline-text-2" id="text-org0fe5706">
|
||||
<p>
|
||||
The FreedomBox project supports Raspberry Pi builds, and the image build system for Freedombone is based on the same system. However, although the Raspberry Pi can run a version of Debian it requires a closed proprietary blob in order to boot the hardware. Who knows what that blob might contain or what exploits it could facilitate. From an adversarial point of view if you were trying to deliver "bulk equipment interference" then it doesn't get any better than piggybacking on something which has control of the boot process, and hence all subsequently run processes.
|
||||
</p>
|
||||
|
|
@ -463,29 +459,32 @@ So although the Raspberry Pi is cheap and hugely popular it's not supported by t
|
|||
</p>
|
||||
</div>
|
||||
</div>
|
||||
<div id="outline-container-org4bb2842" class="outline-2">
|
||||
<h2 id="org4bb2842">Why use Tor? I've heard it's used by bad people</h2>
|
||||
<div class="outline-text-2" id="text-org4bb2842">
|
||||
<div id="outline-container-orgf565b16" class="outline-2">
|
||||
<h2 id="orgf565b16">Why use Tor? I've heard it's used by bad people</h2>
|
||||
<div class="outline-text-2" id="text-orgf565b16">
|
||||
<p>
|
||||
Before you run screaming for the hills based upon whatever scare story you may have just read in the mainstream media there are a few things worthy of consideration. Tor is installed by default on Freedombone, <i>but not as a relay or exit node</i>. It's only used to provide onion addresses so that this gives you or the viewers of your sites some choice about how they access the information. It also allows you to subscribe to and read RSS feeds privately.
|
||||
Years ago Tor was usually depicted in the mainstream media as something scary inhabited by cyberterrorists and other bad cybers, but today to a large extent Tor is accepted as just another way of routing data in a network. Depending upon where you live there may still be some amount of fearmongering about Tor, but it now seems clear that the trajectory is towards general acceptance.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
Onion routing - which is what Tor provides - gives you some level of protection against bulk surveillance of metadata. These days governments and other organisations are in the business of collecting and analysing your metadata. They want to have comprehensive lists of which sites you visited, or who visited your sites. Tor may at least partially help to thwart their totalitarian ambitions to know everything about everyone all of the time.
|
||||
Tor and its onion addresses, previously called hidden addresses, have a few key advantages:
|
||||
</p>
|
||||
|
||||
<p>
|
||||
Tor is not a perfect system and is not fully decentralised. Like all software it has bugs, but it can be considered to probably be an effective tactic against some of the most egregious surveillance fanatics out there.
|
||||
</p>
|
||||
<ul class="org-ul">
|
||||
<li>NAT traversal</li>
|
||||
<li>Firewall traversal</li>
|
||||
<li>Avoiding the domain name system (DNS), which is mostly centralized and not secure</li>
|
||||
<li>Avoiding passive bulk surveillance in which governments try to find out who is communicating with who</li>
|
||||
</ul>
|
||||
|
||||
<p>
|
||||
The media may also have sold you torrid tales about individual Tor project developers. While the conduct of individuals does matter, what matters far more is whether the technical system works and is practical for the average user. Don't allow your opinions of the technical system to be deflected by transient sex scandals or oppressive moralising, and <i>don't hold anyone to standards higher than you would apply to yourself</i>.
|
||||
On the negative side it's a complex system which is not fully decentralized.
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
<div id="outline-container-org8f15beb" class="outline-2">
|
||||
<h2 id="org8f15beb">How is Tor integrated with Freedombone?</h2>
|
||||
<div class="outline-text-2" id="text-org8f15beb">
|
||||
<div id="outline-container-orgac61490" class="outline-2">
|
||||
<h2 id="orgac61490">How is Tor integrated with Freedombone?</h2>
|
||||
<div class="outline-text-2" id="text-orgac61490">
|
||||
<p>
|
||||
Within this project Tor is used more to provide <i>accessibility</i> than the <i>anonymity</i> factor for which Tor is better known. The onion address system provides a way of being able to access sites even if you don't own a conventional domain name or don't have administrator access to your local internet router to be able to do port forwarding.
|
||||
</p>
|
||||
|
|
@ -503,17 +502,17 @@ Even if you're running the "onion only" build, this only means that sites are ac
|
|||
</p>
|
||||
</div>
|
||||
</div>
|
||||
<div id="outline-container-orgd33d165" class="outline-2">
|
||||
<h2 id="orgd33d165">Can I add a clearnet domain to an onion build?</h2>
|
||||
<div class="outline-text-2" id="text-orgd33d165">
|
||||
<div id="outline-container-orgbe35250" class="outline-2">
|
||||
<h2 id="orgbe35250">Can I add a clearnet domain to an onion build?</h2>
|
||||
<div class="outline-text-2" id="text-orgbe35250">
|
||||
<p>
|
||||
You could if you manually edited the relevant nginx configuration files and installed some dynamic DNS system yourself. If you already have sysadmin knowledge then that's probably not too hard. But the builds created with the <b>onion-addresses-only</b> option aren't really intended to support access via clearnet domains.
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
<div id="outline-container-org8e4a27d" class="outline-2">
|
||||
<h2 id="org8e4a27d">Why use Github?</h2>
|
||||
<div class="outline-text-2" id="text-org8e4a27d">
|
||||
<div id="outline-container-org1ea193b" class="outline-2">
|
||||
<h2 id="org1ea193b">Why use Github?</h2>
|
||||
<div class="outline-text-2" id="text-org1ea193b">
|
||||
<p>
|
||||
Github is paradoxically a centralized, closed and proprietary system which happens to mostly host free and open source projects. Up until now it has been relatively benign, but at some point in the name of "growth" it will likely start becoming more evil, or just become like SourceForge - which was also once much loved by FOSS developers, but turned into a den of malvertizing.
|
||||
</p>
|
||||
|
|
@ -527,13 +526,13 @@ The source code for this project is experimentally independently hosted, and it
|
|||
</p>
|
||||
|
||||
<p>
|
||||
Currently many of the repositories used for applications which are not yet packaged for Debian are on Github, and to provide some degree of resilliance against depending too much upon that it's possible to use <a href="./mirrors.html">mirrors stored on another server</a>.
|
||||
Currently many of the repositories used for applications which are not yet packaged for Debian are on Github, and to provide some degree of resilliance against depending too much upon that copies of them also exist within disk images.
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
<div id="outline-container-org3cd5f2c" class="outline-2">
|
||||
<h2 id="org3cd5f2c">Keys and emails should not be stored on servers. Why do you do that?</h2>
|
||||
<div class="outline-text-2" id="text-org3cd5f2c">
|
||||
<div id="outline-container-org7057def" class="outline-2">
|
||||
<h2 id="org7057def">Keys and emails should not be stored on servers. Why do you do that?</h2>
|
||||
<div class="outline-text-2" id="text-org7057def">
|
||||
<p>
|
||||
Ordinarily this is good advice. However, the threat model for a device in your home is different from the one for a generic server in a massive warehouse. Compare and contrast:
|
||||
</p>
|
||||
|
|
@ -591,9 +590,9 @@ In the home environment a box with a good firewall and no GUI components install
|
|||
</div>
|
||||
</div>
|
||||
|
||||
<div id="outline-container-org97f01de" class="outline-2">
|
||||
<h2 id="org97f01de">Why can't I access my .onion site with a Tor browser?</h2>
|
||||
<div class="outline-text-2" id="text-org97f01de">
|
||||
<div id="outline-container-orge669711" class="outline-2">
|
||||
<h2 id="orge669711">Why can't I access my .onion site with a Tor browser?</h2>
|
||||
<div class="outline-text-2" id="text-orge669711">
|
||||
<p>
|
||||
Probably you need to add the site to the NoScript whitelist. Typically click/press on the noscript icon (or select from the menu on mobile) then select <i>whitelist</i> and add the site URL. You may also need to disable HTTPS Everywhere when using onion addresses, which don't use https.
|
||||
</p>
|
||||
|
|
@ -603,9 +602,9 @@ Another factor to be aware of is that it can take a while for the onion address
|
|||
</p>
|
||||
</div>
|
||||
</div>
|
||||
<div id="outline-container-org49504c7" class="outline-2">
|
||||
<h2 id="org49504c7">What is the best hardware to run this system on?</h2>
|
||||
<div class="outline-text-2" id="text-org49504c7">
|
||||
<div id="outline-container-orgdb3b7a6" class="outline-2">
|
||||
<h2 id="orgdb3b7a6">What is the best hardware to run this system on?</h2>
|
||||
<div class="outline-text-2" id="text-orgdb3b7a6">
|
||||
<p>
|
||||
It was originally designed to run on the Beaglebone Black, but that should be regarded as the most minimal system, because it's single core and has by today's standards a small amount of memory. Obviously the more powerful the hardware is the faster things like web pages (blog, social networking, etc) will be served but the more electricity such a system will require if you're running it 24/7. A good compromise between performance and energy consumption is something like an old netbook. The battery of an old netbook or laptop even gives you <a href="https://en.wikipedia.org/wiki/Uninterruptible_power_supply">UPS capability</a> to keep the system going during brief power outages or cable re-arrangements, and that means using full disk encryption on the server also becomes more practical.
|
||||
</p>
|
||||
|
|
@ -615,9 +614,9 @@ It was originally designed to run on the Beaglebone Black, but that should be re
|
|||
</p>
|
||||
</div>
|
||||
</div>
|
||||
<div id="outline-container-orgf3e781c" class="outline-2">
|
||||
<h2 id="orgf3e781c">Can I add more users to the system?</h2>
|
||||
<div class="outline-text-2" id="text-orgf3e781c">
|
||||
<div id="outline-container-orgf1c38a0" class="outline-2">
|
||||
<h2 id="orgf1c38a0">Can I add more users to the system?</h2>
|
||||
<div class="outline-text-2" id="text-orgf1c38a0">
|
||||
<p>
|
||||
Yes. Freedombone can support a small number of users, for a "<i>friends and family</i>" type of home installation. This gives them access to an email account, XMPP, SIP phone and the blog (depending on whether the variant which you installed includes those).
|
||||
</p>
|
||||
|
|
@ -640,9 +639,9 @@ Another point is that Freedombone installations are not intended to support many
|
|||
</p>
|
||||
</div>
|
||||
</div>
|
||||
<div id="outline-container-orgb408729" class="outline-2">
|
||||
<h2 id="orgb408729">Why not use Signal for mobile chat?</h2>
|
||||
<div class="outline-text-2" id="text-orgb408729">
|
||||
<div id="outline-container-orgd32f191" class="outline-2">
|
||||
<h2 id="orgd32f191">Why not use Signal for mobile chat?</h2>
|
||||
<div class="outline-text-2" id="text-orgd32f191">
|
||||
<p>
|
||||
Celebrities recommend Signal. It's Free Software so it must be good, right?
|
||||
</p>
|
||||
|
|
@ -665,9 +664,9 @@ To give credit where it's due Signal is good, but it could be a lot better. The
|
|||
</p>
|
||||
</div>
|
||||
</div>
|
||||
<div id="outline-container-orgd117b08" class="outline-2">
|
||||
<h2 id="orgd117b08">What is the most secure chat app to use on mobile?</h2>
|
||||
<div class="outline-text-2" id="text-orgd117b08">
|
||||
<div id="outline-container-org16a21bb" class="outline-2">
|
||||
<h2 id="org16a21bb">What is the most secure chat app to use on mobile?</h2>
|
||||
<div class="outline-text-2" id="text-org16a21bb">
|
||||
<p>
|
||||
On mobile there are various options. The apps which are likely to be most secure are ones which have end-to-end encryption enabled by default and which can also be onion routed via Orbot. End-to-end encryption secures the content of the message and onion routing obscures the metadata, making it hard for a passive adversary to know who is communicating with who.
|
||||
</p>
|
||||
|
|
@ -677,13 +676,13 @@ The current safest way to chat is to use <a href="https://conversations.im">Conv
|
|||
</p>
|
||||
|
||||
<p>
|
||||
There are many <a href="#orgb408729">other fashionable chat apps</a> with end-to-end security, but often they are closed source, have a single central server or can't be onion routed. It's also important to remember that closed source chat apps should be assumed to be untrustworthy, since their security cannot be independently verified.
|
||||
There are many <a href="#orgd32f191">other fashionable chat apps</a> with end-to-end security, but often they are closed source, have a single central server or can't be onion routed. It's also important to remember that closed source chat apps should be assumed to be untrustworthy, since their security cannot be independently verified.
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
<div id="outline-container-orgb5b2126" class="outline-2">
|
||||
<h2 id="orgb5b2126">How do I remove a user from the system?</h2>
|
||||
<div class="outline-text-2" id="text-orgb5b2126">
|
||||
<div id="outline-container-org279eac7" class="outline-2">
|
||||
<h2 id="org279eac7">How do I remove a user from the system?</h2>
|
||||
<div class="outline-text-2" id="text-org279eac7">
|
||||
<p>
|
||||
To remove a user:
|
||||
</p>
|
||||
|
|
@ -698,9 +697,9 @@ Select <i>Administrator controls</i> then <i>Manage Users</i> and then <i>Delete
|
|||
</p>
|
||||
</div>
|
||||
</div>
|
||||
<div id="outline-container-org1ab944e" class="outline-2">
|
||||
<h2 id="org1ab944e">Why is logging for web sites turned off by default?</h2>
|
||||
<div class="outline-text-2" id="text-org1ab944e">
|
||||
<div id="outline-container-org12ac09e" class="outline-2">
|
||||
<h2 id="org12ac09e">Why is logging for web sites turned off by default?</h2>
|
||||
<div class="outline-text-2" id="text-org12ac09e">
|
||||
<p>
|
||||
If you're making profits out of the logs by running large server warehouses and then data mining what users click on - as is the business model of well known internet companies - then logging everything makes total sense. However, if you're running a home server then logging really only makes sense if you're trying to diagnose some specific problem with the system, and outside of that context logging everything becomes more of a liability than an asset.
|
||||
</p>
|
||||
|
|
@ -714,9 +713,9 @@ On the Freedombone system web logs containing IP addresses are turned off by def
|
|||
</p>
|
||||
</div>
|
||||
</div>
|
||||
<div id="outline-container-org576c1da" class="outline-2">
|
||||
<h2 id="org576c1da">How do I reset the tripwire?</h2>
|
||||
<div class="outline-text-2" id="text-org576c1da">
|
||||
<div id="outline-container-org5e9d3c7" class="outline-2">
|
||||
<h2 id="org5e9d3c7">How do I reset the tripwire?</h2>
|
||||
<div class="outline-text-2" id="text-org5e9d3c7">
|
||||
<p>
|
||||
The tripwire will be automatically reset once per week. If you want to reset it earlier then do the following:
|
||||
</p>
|
||||
|
|
@ -731,9 +730,9 @@ Select <i>Administrator controls</i> then "reset tripwire" using cursors and spa
|
|||
</p>
|
||||
</div>
|
||||
</div>
|
||||
<div id="outline-container-org575438d" class="outline-2">
|
||||
<h2 id="org575438d">Is metadata protected?</h2>
|
||||
<div class="outline-text-2" id="text-org575438d">
|
||||
<div id="outline-container-org0613054" class="outline-2">
|
||||
<h2 id="org0613054">Is metadata protected?</h2>
|
||||
<div class="outline-text-2" id="text-org0613054">
|
||||
<blockquote>
|
||||
<p>
|
||||
"<i>We kill people based on metadata</i>"
|
||||
|
|
@ -749,9 +748,9 @@ Even when using Freedombone metadata analysis by third parties is still possible
|
|||
</p>
|
||||
</div>
|
||||
</div>
|
||||
<div id="outline-container-org249cb8e" class="outline-2">
|
||||
<h2 id="org249cb8e">How do I create email processing rules?</h2>
|
||||
<div class="outline-text-2" id="text-org249cb8e">
|
||||
<div id="outline-container-orgdf75721" class="outline-2">
|
||||
<h2 id="orgdf75721">How do I create email processing rules?</h2>
|
||||
<div class="outline-text-2" id="text-orgdf75721">
|
||||
<div class="org-src-container">
|
||||
<pre class="src src-bash">ssh username@domainname -p 2222
|
||||
</pre>
|
||||
|
|
@ -807,9 +806,9 @@ Spamassassin is also available and within Mutt you can use the S (shift+s) key t
|
|||
</p>
|
||||
</div>
|
||||
</div>
|
||||
<div id="outline-container-org0026d12" class="outline-2">
|
||||
<h2 id="org0026d12">Why isn't dynamic DNS working?</h2>
|
||||
<div class="outline-text-2" id="text-org0026d12">
|
||||
<div id="outline-container-org5b21211" class="outline-2">
|
||||
<h2 id="org5b21211">Why isn't dynamic DNS working?</h2>
|
||||
<div class="outline-text-2" id="text-org5b21211">
|
||||
<p>
|
||||
If you run the command:
|
||||
</p>
|
||||
|
|
@ -832,9 +831,9 @@ https://www.privateinternetaccess.com/pages/whats-my-ip/
|
|||
</div>
|
||||
</div>
|
||||
|
||||
<div id="outline-container-orgcf9314c" class="outline-2">
|
||||
<h2 id="orgcf9314c">How do I change my encryption settings?</h2>
|
||||
<div class="outline-text-2" id="text-orgcf9314c">
|
||||
<div id="outline-container-org929e4ae" class="outline-2">
|
||||
<h2 id="org929e4ae">How do I change my encryption settings?</h2>
|
||||
<div class="outline-text-2" id="text-org929e4ae">
|
||||
<p>
|
||||
Suppose that some new encryption vulnerability has been announced and that you need to change your encryption settings. Maybe an algorithm thought to be secure is now no longer so and you need to remove it. You can change your settings by doing the following:
|
||||
</p>
|
||||
|
|
@ -849,9 +848,9 @@ Select <i>Administrator controls</i> then select <i>Security Settings</i>. You w
|
|||
</p>
|
||||
</div>
|
||||
</div>
|
||||
<div id="outline-container-org623845a" class="outline-2">
|
||||
<h2 id="org623845a">How do I get a domain name?</h2>
|
||||
<div class="outline-text-2" id="text-org623845a">
|
||||
<div id="outline-container-org087d147" class="outline-2">
|
||||
<h2 id="org087d147">How do I get a domain name?</h2>
|
||||
<div class="outline-text-2" id="text-org087d147">
|
||||
<p>
|
||||
Suppose that you have bought a domain name (rather than using a free subdomain on freedns) and you want to use that instead.
|
||||
</p>
|
||||
|
|
@ -915,9 +914,9 @@ You should now be able to send an email from <i>postmaster@mynewdomainname</i> a
|
|||
</div>
|
||||
</div>
|
||||
|
||||
<div id="outline-container-org80ee241" class="outline-2">
|
||||
<h2 id="org80ee241">How do I get a "real" SSL/TLS/HTTPS certificate?</h2>
|
||||
<div class="outline-text-2" id="text-org80ee241">
|
||||
<div id="outline-container-org4bb381a" class="outline-2">
|
||||
<h2 id="org4bb381a">How do I get a "real" SSL/TLS/HTTPS certificate?</h2>
|
||||
<div class="outline-text-2" id="text-org4bb381a">
|
||||
<p>
|
||||
If you did the full install or selected the social variant then the system will have tried to obtain a Let's Encrypt certificate automatically during the install process. If this failed for any reason, or if you have created a new site which you need a certificate for then do the following:
|
||||
</p>
|
||||
|
|
@ -936,9 +935,9 @@ One thing to be aware of is that Let's Encrypt doesn't support many dynamic DNS
|
|||
</p>
|
||||
</div>
|
||||
</div>
|
||||
<div id="outline-container-org8b85e62" class="outline-2">
|
||||
<h2 id="org8b85e62">How do I renew a Let's Encrypt certificate?</h2>
|
||||
<div class="outline-text-2" id="text-org8b85e62">
|
||||
<div id="outline-container-orgfbd420c" class="outline-2">
|
||||
<h2 id="orgfbd420c">How do I renew a Let's Encrypt certificate?</h2>
|
||||
<div class="outline-text-2" id="text-orgfbd420c">
|
||||
<p>
|
||||
Normally certificates will be automatically renewed once per month, so you don't need to be concerned about it. If anything goes wrong with the automatic renewal then you should receive a warning email.
|
||||
</p>
|
||||
|
|
@ -957,9 +956,9 @@ Select <i>Administrator controls</i> then <b>Security settings</b> then <b>Renew
|
|||
</p>
|
||||
</div>
|
||||
</div>
|
||||
<div id="outline-container-org6aba810" class="outline-2">
|
||||
<h2 id="org6aba810">I tried to renew a Let's Encrypt certificate and it failed. What should I do?</h2>
|
||||
<div class="outline-text-2" id="text-org6aba810">
|
||||
<div id="outline-container-orgdaf57b7" class="outline-2">
|
||||
<h2 id="orgdaf57b7">I tried to renew a Let's Encrypt certificate and it failed. What should I do?</h2>
|
||||
<div class="outline-text-2" id="text-orgdaf57b7">
|
||||
<p>
|
||||
Most likely it's because Let's Encrypt doesn't support your particular domain or subdomain. Currently free subdomains tend not to work. You'll need to buy a domain name, link it to your dynamic DNS account and then do:
|
||||
</p>
|
||||
|
|
@ -974,17 +973,17 @@ Select <i>Administrator controls</i> then <b>Security settings</b> then <b>Creat
|
|||
</p>
|
||||
</div>
|
||||
</div>
|
||||
<div id="outline-container-orgc65717c" class="outline-2">
|
||||
<h2 id="orgc65717c">Why not use the services of $company instead? They took the Seppuku pledge</h2>
|
||||
<div class="outline-text-2" id="text-orgc65717c">
|
||||
<div id="outline-container-org9fde76d" class="outline-2">
|
||||
<h2 id="org9fde76d">Why not use the services of $company instead? They took the Seppuku pledge</h2>
|
||||
<div class="outline-text-2" id="text-org9fde76d">
|
||||
<p>
|
||||
<a href="https://cryptostorm.org/viewtopic.php?f=63&t=2954&sid=7de2d1e699cfde2f574e6a7f6ea5a173">That pledge</a> is utterly worthless. Years ago people trusted Google in the same sort of way, because they promised not be be evil and because a lot of the engineers working for them seemed like honest types who were "<i>on our side</i>". Post-<a href="https://en.wikipedia.org/wiki/Nymwars">nymwars</a> and post-<a href="https://en.wikipedia.org/wiki/PRISM_(surveillance_program)">PRISM</a> we know exactly how much Google cared about the privacy and security of its users. But Google is only one particular example. In general don't trust pledges made by companies, even if the people running them seem really sincere.
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
<div id="outline-container-org76affcf" class="outline-2">
|
||||
<h2 id="org76affcf">Why does my email keep getting rejected as spam by Gmail/etc?</h2>
|
||||
<div class="outline-text-2" id="text-org76affcf">
|
||||
<div id="outline-container-org71ce92c" class="outline-2">
|
||||
<h2 id="org71ce92c">Why does my email keep getting rejected as spam by Gmail/etc?</h2>
|
||||
<div class="outline-text-2" id="text-org71ce92c">
|
||||
<p>
|
||||
Welcome to the world of email. Email is really the archetypal decentralized service, developed during the early days of the internet. In principle anyone can run an email server, and that's exactly what you're doing with Freedombone. Email is very useful, but it has a big problem, and that's that the protocols are totally insecure. That made it easy for spammers to do their thing, and in response highly elaborate spam filtering and blocking systems were developed. Chances are that your emails are being blocked in this way. Sometimes the blocking is so indisciminate that entire countries are excluded. What can you do about it? Unless you control the block list at the receiving end you may not be able to do much unless you can find an email proxy server which is trusted by the receiving server.
|
||||
</p>
|
||||
|
|
@ -1015,9 +1014,9 @@ So the situation with email presently is pretty bad, and there's a clear selecti
|
|||
</p>
|
||||
</div>
|
||||
</div>
|
||||
<div id="outline-container-org93992f5" class="outline-2">
|
||||
<h2 id="org93992f5">Tor is censored/blocked in my area. What can I do?</h2>
|
||||
<div class="outline-text-2" id="text-org93992f5">
|
||||
<div id="outline-container-org1bd542d" class="outline-2">
|
||||
<h2 id="org1bd542d">Tor is censored/blocked in my area. What can I do?</h2>
|
||||
<div class="outline-text-2" id="text-org1bd542d">
|
||||
<p>
|
||||
If you can find some details for an obfs4 Tor bridge (its IP address, port number and key or nickname) then you can set up the system to use it to connect to the Tor network. Unlike relay nodes the IP addresses for bridges are not public information and so can't be easily known and added to block lists by authoritarian regimes or over-zealous ISPs.
|
||||
</p>
|
||||
|
|
@ -1048,9 +1047,9 @@ Return to the <a href="index.html">home page</a>
|
|||
</div>
|
||||
</div>
|
||||
|
||||
<div id="outline-container-org92ebfd1" class="outline-2">
|
||||
<h2 id="org92ebfd1">I want to block a particular domain from getting its content into my social network sites</h2>
|
||||
<div class="outline-text-2" id="text-org92ebfd1">
|
||||
<div id="outline-container-orgcf6a401" class="outline-2">
|
||||
<h2 id="orgcf6a401">I want to block a particular domain from getting its content into my social network sites</h2>
|
||||
<div class="outline-text-2" id="text-orgcf6a401">
|
||||
<p>
|
||||
If you're being pestered by some domain which contains bad/illegal/harrassing content or irritating users you can block domains at the firewall level. Go to the administrator control panel and select <i>domain blocking</i>. You can then block, unblock and view the list of blocked domains.
|
||||
</p>
|
||||
|
|
@ -1065,9 +1064,9 @@ Select <i>Administrator controls</i> then <i>Domain blocking</i>.
|
|||
</div>
|
||||
</div>
|
||||
|
||||
<div id="outline-container-orgd38ad08" class="outline-2">
|
||||
<h2 id="orgd38ad08">The mesh system doesn't boot from USB drive</h2>
|
||||
<div class="outline-text-2" id="text-orgd38ad08">
|
||||
<div id="outline-container-org39004fe" class="outline-2">
|
||||
<h2 id="org39004fe">The mesh system doesn't boot from USB drive</h2>
|
||||
<div class="outline-text-2" id="text-org39004fe">
|
||||
<p>
|
||||
If the system doesn't boot and reports an error which includes <b>/dev/mapper/loop0p1</b> then reboot with <b>Ctrl-Alt-Del</b> and when you see the grub menu press <b>e</b> and manually change <b>/dev/mapper/loop0p1</b> to <b>/dev/sdb1</b>, then press <b>Ctrl-x</b>. If that doesn't work then reboot and try <b>/dev/sdc1</b> instead.
|
||||
</p>
|
||||
|
|
|
|||
|
|
@ -3,10 +3,10 @@
|
|||
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
|
||||
<head>
|
||||
<!-- 2017-09-15 Fri 22:17 -->
|
||||
<!-- 2017-12-28 Thu 21:15 -->
|
||||
<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1" />
|
||||
<title></title>
|
||||
<title>‎</title>
|
||||
<meta name="generator" content="Org mode" />
|
||||
<meta name="author" content="Bob Mottram" />
|
||||
<meta name="description" content="Turn the Beaglebone Black into a personal communications server"
|
||||
|
|
@ -256,14 +256,14 @@ First install freedombone onto your local system (not the target hardware that y
|
|||
</p>
|
||||
|
||||
<div class="org-src-container">
|
||||
<pre><code class="src src-bash">sudo apt-get install git
|
||||
<pre class="src src-bash">sudo apt-get install git
|
||||
git clone https://github.com/bashrc/freedombone
|
||||
<span class="org-builtin">cd</span> freedombone
|
||||
git checkout stretch
|
||||
sudo make install
|
||||
freedombone-image --setup debian
|
||||
freedombone-image -t i386 --onion-addresses-only yes
|
||||
</code></pre>
|
||||
</pre>
|
||||
</div>
|
||||
|
||||
<p>
|
||||
|
|
@ -271,14 +271,14 @@ Or on Arch/Parabola:
|
|||
</p>
|
||||
|
||||
<div class="org-src-container">
|
||||
<pre><code class="src src-bash">sudo pacman -S git
|
||||
<pre class="src src-bash">sudo pacman -S git
|
||||
git clone https://github.com/bashrc/freedombone
|
||||
<span class="org-builtin">cd</span> freedombone
|
||||
git checkout stretch
|
||||
sudo make install
|
||||
freedombone-image --setup parabola
|
||||
freedombone-image -t i386 --onion-addresses-only yes
|
||||
</code></pre>
|
||||
</pre>
|
||||
</div>
|
||||
|
||||
<p>
|
||||
|
|
@ -286,8 +286,8 @@ Now prepare your local system to talk to the freedombone by running the followin
|
|||
</p>
|
||||
|
||||
<div class="org-src-container">
|
||||
<pre><code class="src src-bash">freedombone-client
|
||||
</code></pre>
|
||||
<pre class="src src-bash">freedombone-client
|
||||
</pre>
|
||||
</div>
|
||||
|
||||
<div class="org-center">
|
||||
|
|
@ -327,8 +327,8 @@ List what drives are on your system with:
|
|||
</p>
|
||||
|
||||
<div class="org-src-container">
|
||||
<pre><code class="src src-bash">ls /dev/sd*
|
||||
</code></pre>
|
||||
<pre class="src src-bash">ls /dev/sd*
|
||||
</pre>
|
||||
</div>
|
||||
|
||||
<p>
|
||||
|
|
@ -340,9 +340,9 @@ You can now copy the image to the USB thumb drive, replacing <b>sdX</b> with the
|
|||
</p>
|
||||
|
||||
<div class="org-src-container">
|
||||
<pre><code class="src src-bash">dd <span class="org-variable-name">if</span>=/dev/zero <span class="org-variable-name">of</span>=/dev/sdX <span class="org-variable-name">bs</span>=1M <span class="org-variable-name">count</span>=8
|
||||
<pre class="src src-bash">dd <span class="org-variable-name">if</span>=/dev/zero <span class="org-variable-name">of</span>=/dev/sdX <span class="org-variable-name">bs</span>=1M <span class="org-variable-name">count</span>=8
|
||||
dd <span class="org-variable-name">bs</span>=1M <span class="org-variable-name">if</span>=myimagefile.img <span class="org-variable-name">of</span>=/dev/sdX <span class="org-variable-name">conv</span>=fdatasync
|
||||
</code></pre>
|
||||
</pre>
|
||||
</div>
|
||||
|
||||
<p>
|
||||
|
|
@ -354,9 +354,9 @@ As the system boots for the first time the login is:
|
|||
</p>
|
||||
|
||||
<div class="org-src-container">
|
||||
<pre><code class="src src-bash">username: fbone
|
||||
<pre class="src src-bash">username: fbone
|
||||
password: freedombone
|
||||
</code></pre>
|
||||
</pre>
|
||||
</div>
|
||||
|
||||
<p>
|
||||
|
|
@ -364,8 +364,8 @@ If you're installing from a microSD card on a single board computer without a sc
|
|||
</p>
|
||||
|
||||
<div class="org-src-container">
|
||||
<pre><code class="src src-bash">ssh fbone@freedombone.local -p 2222
|
||||
</code></pre>
|
||||
<pre class="src src-bash">ssh fbone@freedombone.local -p 2222
|
||||
</pre>
|
||||
</div>
|
||||
|
||||
<p>
|
||||
|
|
@ -385,8 +385,8 @@ When it's installed on your local system open a terminal and verify the ssh serv
|
|||
</p>
|
||||
|
||||
<div class="org-src-container">
|
||||
<pre><code class="src src-bash">freedombone-client --verify
|
||||
</code></pre>
|
||||
<pre class="src src-bash">freedombone-client --verify
|
||||
</pre>
|
||||
</div>
|
||||
|
||||
<p>
|
||||
|
|
@ -406,9 +406,9 @@ Open another terminal window then run:
|
|||
</p>
|
||||
|
||||
<div class="org-src-container">
|
||||
<pre><code class="src src-bash">freedombone-client
|
||||
<pre class="src src-bash">freedombone-client
|
||||
ssh myusername@freedombone.local -p 2222
|
||||
</code></pre>
|
||||
</pre>
|
||||
</div>
|
||||
|
||||
<p>
|
||||
|
|
@ -472,8 +472,8 @@ Of course, this is just one way in which you can install the Freedombone system.
|
|||
</p>
|
||||
|
||||
<div class="org-src-container">
|
||||
<pre><code class="src src-bash">man freedombone-image
|
||||
</code></pre>
|
||||
<pre class="src src-bash">man freedombone-image
|
||||
</pre>
|
||||
</div>
|
||||
|
||||
<div class="org-center">
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@
|
|||
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
|
||||
<head>
|
||||
<!-- 2017-11-01 Wed 18:58 -->
|
||||
<!-- 2017-12-29 Fri 22:58 -->
|
||||
<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1" />
|
||||
<title>‎</title>
|
||||
|
|
@ -261,7 +261,7 @@ The Freedombone Mesh is a wireless solution for autonomous or internet connected
|
|||
<div class="org-center">
|
||||
|
||||
<div class="figure">
|
||||
<p><img src="images/mesh_logo.jpg" alt="mesh_logo.jpg" />
|
||||
<p><img src="images/mesh_desktop1.png" alt="mesh_desktop1.png" />
|
||||
</p>
|
||||
</div>
|
||||
</div>
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@
|
|||
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
|
||||
<head>
|
||||
<!-- 2017-12-09 Sat 23:07 -->
|
||||
<!-- 2017-12-29 Fri 23:16 -->
|
||||
<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
|
||||
<meta name="viewport" content="width=device-width, initial-scale=1" />
|
||||
<title>‎</title>
|
||||
|
|
@ -246,13 +246,13 @@ for the JavaScript code in this tag.
|
|||
|
||||
<center><h1>Mesh Network: Images</h1></center>
|
||||
|
||||
<div id="outline-container-org59e2a01" class="outline-2">
|
||||
<h2 id="org59e2a01">Pre-built Disk Images</h2>
|
||||
<div class="outline-text-2" id="text-org59e2a01">
|
||||
<div id="outline-container-org92a36a4" class="outline-2">
|
||||
<h2 id="org92a36a4">Pre-built Disk Images</h2>
|
||||
<div class="outline-text-2" id="text-org92a36a4">
|
||||
</div>
|
||||
<div id="outline-container-org58cbb17" class="outline-3">
|
||||
<h3 id="org58cbb17">Writing many images quickly</h3>
|
||||
<div class="outline-text-3" id="text-org58cbb17">
|
||||
<div id="outline-container-orgf74ea4c" class="outline-3">
|
||||
<h3 id="orgf74ea4c">Writing many images quickly</h3>
|
||||
<div class="outline-text-3" id="text-orgf74ea4c">
|
||||
<p>
|
||||
There may be situations where you need to write the same disk image to multiple drives at the same time in order to maximize rate of deployment. In the instructions given below the <b>dd</b> command is used for writing to the target drive, but to write to multiple drives you can use a tool such as <a href="https://wiki.gnome.org/Apps/MultiWriter">GNOME MultiWriter</a>.
|
||||
</p>
|
||||
|
|
@ -280,9 +280,9 @@ The MultiWriter tool is also available within mesh client images, so that you ca
|
|||
</p>
|
||||
</div>
|
||||
</div>
|
||||
<div id="outline-container-orgbec0fc8" class="outline-3">
|
||||
<h3 id="orgbec0fc8">Client images</h3>
|
||||
<div class="outline-text-3" id="text-orgbec0fc8">
|
||||
<div id="outline-container-orgdd8f201" class="outline-3">
|
||||
<h3 id="orgdd8f201">Client images</h3>
|
||||
<div class="outline-text-3" id="text-orgdd8f201">
|
||||
<div class="org-center">
|
||||
|
||||
<div class="figure">
|
||||
|
|
@ -301,7 +301,7 @@ wget https://freedombone.net/downloads/current/freedombone-meshclient-i386.img.x
|
|||
wget https://freedombone.net/downloads/current/freedombone-meshclient-i386.img.xz.sig
|
||||
gpg --verify freedombone-meshclient-i386.img.xz.sig
|
||||
sha256sum freedombone-meshclient-i386.img.xz
|
||||
3e88205461bb2061dc172ff0a1e65e5cae1013f8f7dc26c6d5cbe1c986c98555
|
||||
49391230de6a4f1966db091813deb8f9d93c947677f5483baa52400d7fcba7d3
|
||||
unxz freedombone-meshclient-i386.img.xz
|
||||
sudo dd <span class="org-variable-name">if</span>=/dev/zero <span class="org-variable-name">of</span>=/dev/sdX <span class="org-variable-name">bs</span>=1M <span class="org-variable-name">count</span>=8
|
||||
sudo dd <span class="org-variable-name">bs</span>=1M <span class="org-variable-name">if</span>=freedombone-meshclient-i386.img <span class="org-variable-name">of</span>=/dev/sdX <span class="org-variable-name">conv</span>=fdatasync
|
||||
|
|
@ -322,7 +322,7 @@ wget https://freedombone.net/downloads/current/freedombone-meshclient-insecure-i
|
|||
wget https://freedombone.net/downloads/current/freedombone-meshclient-insecure-i386.img.xz.sig
|
||||
gpg --verify freedombone-meshclient-insecure-i386.img.xz.sig
|
||||
sha256sum freedombone-meshclient-insecure-i386.img.xz
|
||||
09c059664daf56d210134735d37e8117bb7b755acc8b9b253cdfa42052249ccb
|
||||
c11783741e66df5072ffcbef8d9b04260a2298d84e33c72fefa4bb539d094810
|
||||
unxz freedombone-meshclient-insecure-i386.img.xz
|
||||
sudo dd <span class="org-variable-name">if</span>=/dev/zero <span class="org-variable-name">of</span>=/dev/sdX <span class="org-variable-name">bs</span>=1M <span class="org-variable-name">count</span>=8
|
||||
sudo dd <span class="org-variable-name">bs</span>=1M <span class="org-variable-name">if</span>=freedombone-meshclient-insecure-i386.img <span class="org-variable-name">of</span>=/dev/sdX <span class="org-variable-name">conv</span>=fdatasync
|
||||
|
|
@ -331,16 +331,16 @@ sudo dd <span class="org-variable-name">bs</span>=1M <span class="org-variable-n
|
|||
</div>
|
||||
</div>
|
||||
|
||||
<div id="outline-container-org6f3a05a" class="outline-3">
|
||||
<h3 id="org6f3a05a">Router images</h3>
|
||||
<div class="outline-text-3" id="text-org6f3a05a">
|
||||
<div id="outline-container-org231f975" class="outline-3">
|
||||
<h3 id="org231f975">Router images</h3>
|
||||
<div class="outline-text-3" id="text-org231f975">
|
||||
<p>
|
||||
Routers are intended to build network coverage for an area using small and low cost hardware. You can bolt them to walls or leave them on window ledges. They don't have any user interface and their only job is to haul network traffic across the mesh and to enable peers to find each other via running bootstrap nodes for Tox and IPFS. Copy the image to a microSD card and insert it into the router, plug in an Atheros wifi dongle and power on. That should be all you need to do.
|
||||
</p>
|
||||
</div>
|
||||
<div id="outline-container-org0387979" class="outline-4">
|
||||
<h4 id="org0387979">Beaglebone Black</h4>
|
||||
<div class="outline-text-4" id="text-org0387979">
|
||||
<div id="outline-container-orgbe92b46" class="outline-4">
|
||||
<h4 id="orgbe92b46">Beaglebone Black</h4>
|
||||
<div class="outline-text-4" id="text-orgbe92b46">
|
||||
<div class="org-center">
|
||||
|
||||
<div class="figure">
|
||||
|
|
@ -359,7 +359,7 @@ wget https://freedombone.net/downloads/current/freedombone-mesh_beaglebone-armhf
|
|||
wget https://freedombone.net/downloads/current/freedombone-mesh_beaglebone-armhf.img.xz.sig
|
||||
gpg --verify freedombone-mesh_beaglebone-armhf.img.xz.sig
|
||||
sha256sum freedombone-mesh_beaglebone-armhf.img.xz
|
||||
60017999340a6559d1de76f3d78d9771c11de5eeefb3d3b812747ce306251e67
|
||||
ad8f22c0d46c98a80aa47b5809402971cf5cf26ebf587c59a667307b2386c3d2
|
||||
unxz freedombone-mesh_beaglebone-armhf.img.xz
|
||||
sudo dd <span class="org-variable-name">bs</span>=1M <span class="org-variable-name">if</span>=freedombone-mesh_beaglebone-armhf.img <span class="org-variable-name">of</span>=/dev/sdX <span class="org-variable-name">conv</span>=fdatasync
|
||||
</pre>
|
||||
|
|
@ -377,9 +377,9 @@ There is still a software freedom issue with the Beaglebone Black, but it doesn'
|
|||
</div>
|
||||
</div>
|
||||
|
||||
<div id="outline-container-org0db60a2" class="outline-2">
|
||||
<h2 id="org0db60a2">Building Disk Images</h2>
|
||||
<div class="outline-text-2" id="text-org0db60a2">
|
||||
<div id="outline-container-orgd948176" class="outline-2">
|
||||
<h2 id="orgd948176">Building Disk Images</h2>
|
||||
<div class="outline-text-2" id="text-orgd948176">
|
||||
<p>
|
||||
It's better not to trust images downloaded from random places on the interwebs. Chances are that unless you are in the web of trust of the above GPG signatures then they don't mean very much to you. If you actually want something trustworthy then build the images from scratch. It will take some time. Here's how to do it.
|
||||
</p>
|
||||
|
|
@ -394,7 +394,7 @@ wget https://freedombone.net/downloads/current/freedombone.tar.gz
|
|||
wget https://freedombone.net/downloads/current/freedombone.tar.gz.sig
|
||||
gpg --verify freedombone.tar.gz.sig
|
||||
sha256sum freedombone.tar.gz
|
||||
3d2a7f2bd7a3475832756b7bb63b96ba5fc4a4f4d7bffe86e685be9a3b41b958
|
||||
afbb536564140aa28c6491d45b7474ced5a0b018539ffd3e96b13b242a41792e
|
||||
tar -xzvf freedombone.tar.gz
|
||||
<span class="org-builtin">cd</span> freedombone
|
||||
git checkout stretch
|
||||
|
|
|
|||
Loading…
Reference in New Issue