diff options
| -rw-r--r-- | index.mdwn | 58 |
1 files changed, 29 insertions, 29 deletions
@@ -32,36 +32,36 @@ The core protocol is composed by the following metadata: * The hosting group? * The hosted group? * Security: - * Security and privacy policy for the layer. - * Crypto - * Implementation. - * Cipher. - * Used procedure. - * Shared password? Which sharing scheme? - * Boot procedure: - * The host has automatic boot loading. - * No boot loading in the host, manual boot. + * Security and privacy policy for the layer. + * Crypto + * Implementation. + * Cipher. + * Used procedure. + * Shared password? Which sharing scheme? + * Boot procedure: + * The host has automatic boot loading. + * No boot loading in the host, manual boot. * Backups - * Backup availability - * No backups. - * Local backups. - * Remote backups in more than a single place but in the same building/country/etc. - * Remote backups in more than a single place and also in other countries. - * Backup security - * Have unencrypted backups. - * Have encrypted backups only. - * Have encrypted backups only with a key that needs more than one sysadmin to unlock. - * Have encrypted backups only with a key that the sysadmins do not have access to. - * Backup integrity - * No integrity checking. - * Signed backups only. - * Push and signed backups. - * Pull and signed backups only. - * Backup and users - * Users are informed whether their private data are being backed up and in which ways. - * Have backup data always available to private download by users and/or groups with admin aid. - * Have backup data always available to private download by users and/or groups without admin aid. - * Users and/or groups can choose to not have backups of their data. + * Backup availability + * No backups. + * Local backups. + * Remote backups in more than a single place but in the same building/country/etc. + * Remote backups in more than a single place and also in other countries. + * Backup security + * Have unencrypted backups. + * Have encrypted backups only. + * Have encrypted backups only with a key that needs more than one sysadmin to unlock. + * Have encrypted backups only with a key that the sysadmins do not have access to. + * Backup integrity + * No integrity checking. + * Signed backups only. + * Push and signed backups. + * Pull and signed backups only. + * Backup and users + * Users are informed whether their private data are being backed up and in which ways. + * Have backup data always available to private download by users and/or groups with admin aid. + * Have backup data always available to private download by users and/or groups without admin aid. + * Users and/or groups can choose to not have backups of their data. * Legal * Applicable law where layer is located. * Hosting group has legal team/support? |