From 6bdbcdeb95422d98161b85c16df6cdbc606ae6de Mon Sep 17 00:00:00 2001 From: Bob Mottram Date: Tue, 29 Sep 2015 13:06:36 +0100 Subject: [PATCH] Wording --- doc/EN/backups.org | 4 ++-- website/EN/backups.html | 6 +++--- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/doc/EN/backups.org b/doc/EN/backups.org index baf8ca30..4e1075fe 100644 --- a/doc/EN/backups.org +++ b/doc/EN/backups.org @@ -76,7 +76,7 @@ Enter the password for the USB drive. When the restore is complete you can remov * Distributed backups Distributed backups are a better way of ensuring the persistence of your data, such that even if your system gets stolen or destroyed then the data will still be recoverable from your friends. Since the backups are encrypted your friends (or anyone else with access to their systems) won't be able to read your backed up content even if their systems are subsequently compromised. -Firstly you will need to have a user account on one or more of your friends servers. They don't necessarily need to be using Freedombone, just some version of GNU/Linux with ssh access. They can create a user account for you with the *adduser * command when logged in as root and then give you the username and password via a secure method, such as on paper or via an encrypted email or via an XMPP chat using OTR. Make sure that the password used is a strong one - preferably a long random string stored in a password manager - so that dictionary attacks not be easy. Also for maximum resilience put your password manager file onto a USB thumb drive and carry it with you. +Firstly you will need to have a user account on one or more of your friends servers. They don't necessarily need to be using Freedombone, just some version of GNU/Linux with ssh access. They can create a user account for you with the *adduser * command when logged in as root and then give you the username and password via a secure method, such as on paper or via an encrypted email or via an XMPP chat using OTR. Make sure that the password used is a strong one - preferably a long random string stored in a password manager - so that dictionary attacks will not be easy. Also for maximum resilience put your password manager file onto a USB thumb drive and carry it with you. #+BEGIN_SRC bash ssh username@domainname -p 2222 @@ -86,7 +86,7 @@ freedombone-remote You can then enter the usernames, domains and ssh logins for one or more remote servers. The system will try to backup to these remote locations once per day. * Restore from a friend ** With a completely new Freedombone installation -This is the ultimate disaster recovery scenario in which you are beginning completely from scratch with new hardware and a new Freedombone installation (configured with the same username and domain names). It is assumed that the old hardware was destroyed, but that you have the backup key stored within a password manager on a USB thumb drive. +This is the ultimate disaster recovery scenario in which you are beginning completely from scratch with new hardware and a new Freedombone installation (configured with the same username and domain names). It is assumed that the old hardware was destroyed, but that you have the backup key stored on a USB thumb drive. First log in and if you don't already have one then create a new friends list: diff --git a/website/EN/backups.html b/website/EN/backups.html index 262571ca..28a2eecb 100644 --- a/website/EN/backups.html +++ b/website/EN/backups.html @@ -4,7 +4,7 @@ - + @@ -310,7 +310,7 @@ Distributed backups are a better way of ensuring the persistence of your data, s

-Firstly you will need to have a user account on one or more of your friends servers. They don't necessarily need to be using Freedombone, just some version of GNU/Linux with ssh access. They can create a user account for you with the adduser <username> command when logged in as root and then give you the username and password via a secure method, such as on paper or via an encrypted email or via an XMPP chat using OTR. Make sure that the password used is a strong one - preferably a long random string stored in a password manager - so that dictionary attacks not be easy. Also for maximum resilience put your password manager file onto a USB thumb drive and carry it with you. +Firstly you will need to have a user account on one or more of your friends servers. They don't necessarily need to be using Freedombone, just some version of GNU/Linux with ssh access. They can create a user account for you with the adduser <username> command when logged in as root and then give you the username and password via a secure method, such as on paper or via an encrypted email or via an XMPP chat using OTR. Make sure that the password used is a strong one - preferably a long random string stored in a password manager - so that dictionary attacks will not be easy. Also for maximum resilience put your password manager file onto a USB thumb drive and carry it with you.

@@ -332,7 +332,7 @@ You can then enter the usernames, domains and ssh logins for one or more remote

With a completely new Freedombone installation

-This is the ultimate disaster recovery scenario in which you are beginning completely from scratch with new hardware and a new Freedombone installation (configured with the same username and domain names). It is assumed that the old hardware was destroyed, but that you have the backup key stored within a password manager on a USB thumb drive. +This is the ultimate disaster recovery scenario in which you are beginning completely from scratch with new hardware and a new Freedombone installation (configured with the same username and domain names). It is assumed that the old hardware was destroyed, but that you have the backup key stored on a USB thumb drive.