Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • T tails
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 982
    • Issues 982
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 40
    • Merge requests 40
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • tails
  • tails
  • Issues
  • #16299
Closed
Open
Issue created Jan 05, 2019 by sajolida@sajolidaMaintainer

Disable Autocrypt even for existing persistent Thunderbird profiles

Originally created by @sajolida on #16299 (Redmine)

See #16223 (comment 15143): people who upgraded through 3.10 will still have Autocrypt enabled and might send unencrypted emails unwillingly.

We could have a migration script that automatically applies the default configuration from Autocrypt 3.11 (Autocrypt disabled + acPreferEncrypt) when we detect the configuration we had in 3.10 (Autocrypt enabled + no acPreferEncrypt).

We could keep this migration script around during some release cycles and document that if people want to enable Autocrypt they have to enable acPreferEncrypt to avoid triggering the migration script.

Feature Branch: hefee/bugfix/16186-disable-autocrypt+force-all-tests

Parent Task: #15923 (closed)

Subtasks

  • #16359 (closed)

Related issues

  • Related to #16223 (closed)
  • Related to #16186 (closed)
  • Blocks tails/accounting#15507
Edited May 15, 2020 by sajolida
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking