https://bugs.documentfoundation.org/show_bug.cgi?id=162630
--- Comment #2 from Bill Zaumen <[email protected]> --- Allowing a document to always be encrypted to additional users other than self handles two use cases. An individual creating an important document - financial data information, etc. - might add an additional GPG key for a trusted third party in case the user is incapacitated. For example, for some backups, I've created a GPG key on a separate keyring and copied the corresponding public key to my keyring. The keyring containing the private key is kept in a secure location such as a safe deposit box. For corporate or government use, this would allow an employee to encrypt files while the employee's employer can, if necessary, access these files if the employee is injured, or if the employer is legally required to provide the files due to a subpoena or in order to comply with public-records laws. In typical usage, all versions of a document would be encrypted so as to be accessible to the same additional users. There should be just a single document: when GPG is used to encrypt a file with multiple recipients, the file is encrypted using a symmetric cipher and that cipher's password (or key and initial vector) is encrypted multiple times using public key encryption. As a result, encrypting for multiple recipients generally adds a small amount of additional data to the encrypted file and all recipients can decrypt the same file. -- You are receiving this mail because: You are the assignee for the bug.
