Since storage devices are auto-mounted as root, they also need to be unmounted
as root.
The assumption here is that this wouldn't have any impact on being able to
write to the devices.
Fixes#1411
Signed-off-by: Joseph Nuthalapati <njoseph@thoughtworks.com>
Reviewed-by: James Valleroy <jvalleroy@mailbox.org>
- Change the base URL of the app so that functional tests can guess the URLs.
- Assign classes to generate HTML elements.
- Indentation.
- Normalize URLs to have '/' at the end as per Django convention.
Reviewed-by: James Valleroy <jvalleroy@mailbox.org>
Currently, monkeysphere does not get installed properly unless FreedomBox
security is disabled. Skip these tests until the monkeysphere is patched
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911907 .
Another way to enable these tests is to disable restricted logins (write steps
to do that) before running them.
Reviewed-by: James Valleroy <jvalleroy@mailbox.org>
OpenSSH 7.8 and above use OpenSSH key format instead of the earlier PEM format
by default for RSA keys. This format is not understood by openssl/monkeysphere
yet. Convert it to PEM before importing into monkeysphere.
Reviewed-by: James Valleroy <jvalleroy@mailbox.org>
Disk labels are unreliable. They may not exist. There are not unique and two
disks in the system may have the same label. Instead use the device path of the
disk/partition.
Reviewed-by: James Valleroy <jvalleroy@mailbox.org>
When a disk does not have a label, its device path is used. This contains a '/'
which by default is not encoded by 'urlencode' filter in Django templates. This
leads to the expected URL not matching the regex in urls.py. Fix this by
ensuring that '/' is also encoded by 'urlencode'.
Reviewed-by: James Valleroy <jvalleroy@mailbox.org>
Changing the ownership of the backup archives from "root" to "plinth" fixes the
permission errors when downloading backup archives.
Fixes#1402
Signed-off-by: Joseph Nuthalapati <njoseph@thoughtworks.com>
Reviewed-by: James Valleroy <jvalleroy@mailbox.org>
There might be data to backup in future if we allow configuration. Currently, it
is just an assurance to the user that there is no data to backup.
Reviewed-by: James Valleroy <jvalleroy@mailbox.org>
There might be data to backup in future if we allow configuration. Currently, it
is just an assurance to the user that there is no data to backup.
Reviewed-by: James Valleroy <jvalleroy@mailbox.org>
There might be data to backup in future if we allow customizing domain
configuration. Currently, it is just an assurance to the user that there is no
data to backup.
Reviewed-by: James Valleroy <jvalleroy@mailbox.org>
There might be data to backup in future if we allow configuration. Currently, it
is just an assurance to the user that there is no data to backup.
Reviewed-by: James Valleroy <jvalleroy@mailbox.org>
There might be data to backup in future if we allow adding custom rules or
provide features such as blocking untrusted devices at home. Currently, it is
just an assurance to the user that there is no data to backup.
Reviewed-by: James Valleroy <jvalleroy@mailbox.org>
Each application will be able to implement backup_pre, backup_post, restore_pre
and restore_post hooks that get called before/after backup/restore
appropriately. This is to handle any edge cases that backup manifest mechanism
does not handle.
Reviewed-by: James Valleroy <jvalleroy@mailbox.org>
snapper set-config expects each key-value pair to be passed as a separate
argument separated by '='.
Reviewed-by: James Valleroy <jvalleroy@mailbox.org>
