Changes between Version 3 and Version 4 of PublicProcedures


Ignore:
Timestamp:
02/11/16 02:43:23 (10 years ago)
Author:
dkg
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • PublicProcedures

    v3 v4  
    33== Standard Operating Procedures ==
    44
    5 This page describes baseline policies that we use in our routine provision of services. Where possible, we try to comply with the [https://policy.sarava.org/policy/  Providers' Commitment for Privacy (PCP)]. Information is current as per the last edit in the [wiki:PublicProcedures?action=history history].
     5This page describes some baseline policies that we use in our routine provision of services. Where possible, we try to comply with the [https://policy.sarava.org/policy/  Providers' Commitment for Privacy (PCP)].
    66
    77=== Provision of virtual machines (VMs) ===
    88
    9 Wherever possible, we set up our infrastructure in a way that administrators of the Tachanka! collective have no access to the cryptographic keys of hosted virtual machines.  Therefore, we have extremely limited knowledge about the data and the activities of our users. In cases where we are making backups, this applies to them as well.
     9Wherever possible, we set up our infrastructure in a way that administrators of the Tachanka! collective have no access to the hosted virtual machines.  Therefore, we have extremely limited knowledge about the data and the activities of our users. In cases where we are making backups for our guests, our backups will be opaque to the members of the Tachanka! collective.
    1010
    1111 * We use a base layer of encryption on host servers.
    1212 * Virtual machines have individualised block devices that employ a second layer of encryption. Consequently, these each require a separate, individual key.
    13  * We strongly encourage users of virtual machines to manage their own LUKS passphrases independently of the Tachanka! collective.
    14  * Users are informed about the technical setup of their working environments and, if required, supported in setting up appropriate encryption.
     13 * We strongly encourage users of virtual machines to manage their own keys and passphrases independently of the Tachanka! collective.
     14 * The Tachanka! collective will communicate with the users about the technical setup of their working environments and, if required, will support them in setting up appropriate encryption.
    1515