Differences between revisions 1 and 2
Revision 1 as of 2017-06-10 15:35:26
Size: 26
Comment:
Revision 2 as of 2017-12-09 15:06:28
Size: 1153
Comment: add call notes
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:

 * Status of Diaspora (joseph, sunil)
   * Focus for next release
   * 2 problems
     * diaspora package installation bugs, and in contrib instead of main
     * Plinth work for Diaspora has problems when obtaining certificate, changing domain after installation, etc.
 * SearX
   * Integration into !FreedomBox half done
 * Carefully review all commits
 * Put together a security guide
   * If you leave your desktop/laptops unattended, use a hardware token to store passwords, SSH and GPG keys
     * Make multiple copies or paper copies of such data and hide a copy in a safe place
   * If you leave your desktop/laptops unattended and powered off, encrypt the disk
     * encrypting the disk is not useful if the host is left in standby. Use X locking as a mitigation
   * Isolate your activities using multiple users and/or browser sessions and/or VMs and/or Qubes OS perhaps
   * Reinstall your desktop! (the likelyhood that a desktop has been compromised *at least once* can only increase over time)
 * !LetsEncrypt integration with mumble-server
   * https://github.com/freedombox/Plinth/issues/701

Hack call: 14:00 UTC

  • Status of Diaspora (joseph, sunil)
    • Focus for next release
    • 2 problems
      • diaspora package installation bugs, and in contrib instead of main
      • Plinth work for Diaspora has problems when obtaining certificate, changing domain after installation, etc.
  • SearX
    • Integration into FreedomBox half done

  • Carefully review all commits
  • Put together a security guide
    • If you leave your desktop/laptops unattended, use a hardware token to store passwords, SSH and GPG keys
      • Make multiple copies or paper copies of such data and hide a copy in a safe place
    • If you leave your desktop/laptops unattended and powered off, encrypt the disk
      • encrypting the disk is not useful if the host is left in standby. Use X locking as a mitigation
    • Isolate your activities using multiple users and/or browser sessions and/or VMs and/or Qubes OS perhaps
    • Reinstall your desktop! (the likelyhood that a desktop has been compromised *at least once* can only increase over time)
  • LetsEncrypt integration with mumble-server