Backblaze - Revision history

Maltfield: cleanup TODOs

2024-09-22T18:47:40Z

cleanup TODOs

← Older revision		Revision as of 18:47, 22 September 2024
Line 122:		Line 122:

	Finally, '''delete the master key''' created above from the Backblaze B2 WUI		Finally, '''delete the master key''' created above from the Backblaze B2 WUI

	~~TODO: configure rclone with append-only key~~
	~~TODO: test rclone~~
	~~TODO: delete high-permission api key~~

	==Configure rclone==		==Configure rclone==

Maltfield: added commands to configure rclone

2024-09-22T18:41:02Z

added commands to configure rclone

Show changes

Maltfield at 18:06, 22 September 2024

2024-09-22T18:06:45Z

← Older revision		Revision as of 18:06, 22 September 2024
Line 73:		Line 73:
	{{Warning\|To provide '''protection from ransomeware''', it's critically important that the server cannot delete files from backblaze. This is why '''we only generate [https://en.wikipedia.org/wiki/Append-only append-only] keys''' with very limited permissions '''for use on the server'''.		{{Warning\|To provide '''protection from ransomeware''', it's critically important that the server cannot delete files from backblaze. This is why '''we only generate [https://en.wikipedia.org/wiki/Append-only append-only] keys''' with very limited permissions '''for use on the server'''.

	'''Never put a "master key" on the server!''' If you need a key with more permissions (eg a key to create keys), then you should create a new master key and only use it locally on your laptop. And delete the master key when you're done using it.		'''Never put a "master key" on the server!''' If you need a key with more permissions (eg a key to create keys), then you should create a new master key and only use it locally on your laptop. And '''delete the master key when you're done''' using it.
	}}		}}

Line 88:		Line 88:

	{{Warning\|		{{Warning\|
	'''Never put a "master key" on the server!'' Use your personal laptop.		'''Never put a "master key" on the server!''' Use your personal laptop.
	}}		}}

Maltfield: /* Create Key */

2024-09-22T18:06:00Z

Create Key

← Older revision		Revision as of 18:06, 22 September 2024
Line 71:		Line 71:
	The root user includes <code>listFiles</code> for the purpose of executing <code>/root/backups/backupReport.sh</code>, which lists the backups that have been successfully uploaded to Backblaze, and it generates an email to let us know if any backups are missing (it also sends an email on the 2nd of every month if everything is OK, so we know that the backupReport itself is operating correctly).		The root user includes <code>listFiles</code> for the purpose of executing <code>/root/backups/backupReport.sh</code>, which lists the backups that have been successfully uploaded to Backblaze, and it generates an email to let us know if any backups are missing (it also sends an email on the 2nd of every month if everything is OK, so we know that the backupReport itself is operating correctly).

	{{Warning\|To provide '''protection from ransomeware''', it's critically important that the server cannot delete files from backblaze. This is why '''we only generate "[https://en.wikipedia.org/wiki/Append-only append-only]" keys''' with very limited permissions '''for use on the server'''.		{{Warning\|To provide '''protection from ransomeware''', it's critically important that the server cannot delete files from backblaze. This is why '''we only generate [https://en.wikipedia.org/wiki/Append-only append-only] keys''' with very limited permissions '''for use on the server'''.

	'''Never put a "master key" on the server!''' If you need a key with more permissions (eg a key to create keys), then you should create a new master key and only use it locally on your laptop. And delete the master key when you're done using it.		'''Never put a "master key" on the server!''' If you need a key with more permissions (eg a key to create keys), then you should create a new master key and only use it locally on your laptop. And delete the master key when you're done using it.

Maltfield at 18:05, 22 September 2024

2024-09-22T18:05:21Z

← Older revision		Revision as of 18:05, 22 September 2024
Line 71:		Line 71:
	The root user includes <code>listFiles</code> for the purpose of executing <code>/root/backups/backupReport.sh</code>, which lists the backups that have been successfully uploaded to Backblaze, and it generates an email to let us know if any backups are missing (it also sends an email on the 2nd of every month if everything is OK, so we know that the backupReport itself is operating correctly).		The root user includes <code>listFiles</code> for the purpose of executing <code>/root/backups/backupReport.sh</code>, which lists the backups that have been successfully uploaded to Backblaze, and it generates an email to let us know if any backups are missing (it also sends an email on the 2nd of every month if everything is OK, so we know that the backupReport itself is operating correctly).

	{{Warning\|To provide '''protection from ransomeware''', it's critically important that the server cannot delete files from backblaze. This is why '''we only generate "append-only" keys''' with very limited permissions '''for use on the server'''.		{{Warning\|To provide '''protection from ransomeware''', it's critically important that the server cannot delete files from backblaze. This is why '''we only generate "[https://en.wikipedia.org/wiki/Append-only append-only]" keys''' with very limited permissions '''for use on the server'''.

	* https://en.wikipedia.org/wiki/Append-only		'''Never put a "master key" on the server!''' If you need a key with more permissions (eg a key to create keys), then you should create a new master key and only use it locally on your laptop. And delete the master key when you're done using it.

	'''Never put a "master key" on the server!'' If you need a key with more permissions (eg a key to create keys), then you should create a new master key and only use it locally on your laptop. And delete the master key when you're done using it.
	}}		}}

Maltfield at 18:03, 22 September 2024

2024-09-22T18:03:56Z

← Older revision		Revision as of 18:03, 22 September 2024
Line 71:		Line 71:
	The root user includes <code>listFiles</code> for the purpose of executing <code>/root/backups/backupReport.sh</code>, which lists the backups that have been successfully uploaded to Backblaze, and it generates an email to let us know if any backups are missing (it also sends an email on the 2nd of every month if everything is OK, so we know that the backupReport itself is operating correctly).		The root user includes <code>listFiles</code> for the purpose of executing <code>/root/backups/backupReport.sh</code>, which lists the backups that have been successfully uploaded to Backblaze, and it generates an email to let us know if any backups are missing (it also sends an email on the 2nd of every month if everything is OK, so we know that the backupReport itself is operating correctly).

	{{Warning To provide '''protection from ransomeware''', it's critically important that the server cannot delete files from backblaze. This is why '''we only generate "append-only" keys''' with very limited permissions '''for use on the server'''.		{{Warning\|To provide '''protection from ransomeware''', it's critically important that the server cannot delete files from backblaze. This is why '''we only generate "append-only" keys''' with very limited permissions '''for use on the server'''.

	* https://en.wikipedia.org/wiki/Append-only		* https://en.wikipedia.org/wiki/Append-only
Line 89:		Line 89:
	On your Debian laptop, install the <code>backblaze-b2</code> package		On your Debian laptop, install the <code>backblaze-b2</code> package

	{{Warning		{{Warning\|
	'''Never put a "master key" on the server!'' Use your personal laptop.		'''Never put a "master key" on the server!'' Use your personal laptop.
	}}		}}

Maltfield: added how to create a new append only key set

2024-09-22T18:03:00Z

added how to create a new append only key set

@@ Line 62: / Line 62: @@
 The [[OSE Server]] should have two keys:
-# append-only
+# <code>append-only</code>
-# list-and-append-only
+# <code>list-and-append-only</code>
 The less privileged <code>b2user</code> user on the server uses the <code>append-only</code> key, which only has access to the <code>ose-server-backups</code> bucket and only has the following capabilities: <code>readFiles, writeFiles</code>
@@ Line 78: / Line 78: @@
 }}
-TODO: create a key with all permissions in the backblaze b2 wui
+At the time of writing, it's not possible to create a new append-only key from the Backblaze WUI. You have to use the B2 CLI.
-TODO: install backblaze-b2 cli locally on your laptop computer
-TODO: configure local backblaze-b2 cli with the high-permission key
+In order to use the B2 CLI, you'll first need to create a (temporary) master key in the Backblaze WUI.
-TODO: create append-only key
 TODO: configure rclone with append-only key
 TODO: test rclone

Maltfield: add warning

2024-09-22T17:50:04Z

add warning

← Older revision		Revision as of 17:50, 22 September 2024
Line 59:		Line 59:

	==Create Key==		==Create Key==

			The [[OSE Server]] should have two keys:

			# append-only
			# list-and-append-only

			The less privileged <code>b2user</code> user on the server uses the <code>append-only</code> key, which only has access to the <code>ose-server-backups</code> bucket and only has the following capabilities: <code>readFiles, writeFiles</code>

			The root user on the server uses the <code>list-and-append-only</code> key, which only has access to the <code>ose-server-backups</code> bucket and only has the following capabilities: <code>listFiles, readFiles, writeFiles</code>.

			The root user includes <code>listFiles</code> for the purpose of executing <code>/root/backups/backupReport.sh</code>, which lists the backups that have been successfully uploaded to Backblaze, and it generates an email to let us know if any backups are missing (it also sends an email on the 2nd of every month if everything is OK, so we know that the backupReport itself is operating correctly).

			{{Warning To provide '''protection from ransomeware''', it's critically important that the server cannot delete files from backblaze. This is why '''we only generate "append-only" keys''' with very limited permissions '''for use on the server'''.

			* https://en.wikipedia.org/wiki/Append-only

			'''Never put a "master key" on the server!'' If you need a key with more permissions (eg a key to create keys), then you should create a new master key and only use it locally on your laptop. And delete the master key when you're done using it.
			}}

	TODO: create a key with all permissions in the backblaze b2 wui		TODO: create a key with all permissions in the backblaze b2 wui

Maltfield: fix order of section

2024-09-22T17:30:30Z

fix order of section

← Older revision		Revision as of 17:30, 22 September 2024
Line 57:		Line 57:
	sudo apt-get install rclone		sudo apt-get install rclone
	</pre>		</pre>
	~~=Restore from backups=~~

	~~This section will describe how to extract data from an encrypted backup file stored in Backblaze B2.~~

	==Create Key==		==Create Key==
Line 76:		Line 73:

	TODO		TODO

			=Restore from backups=

			This section will describe how to extract data from an encrypted backup file stored in Backblaze B2.

	==Download from WUI==		==Download from WUI==

Maltfield at 03:49, 22 September 2024

2024-09-22T03:49:58Z

← Older revision		Revision as of 03:49, 22 September 2024
Line 70:		Line 70:
	TODO: test rclone		TODO: test rclone
	TODO: delete high-permission api key		TODO: delete high-permission api key

			TODO: now do it again for root, but this time with 'listFiles'

	==Configure rclone==		==Configure rclone==