Using SSHFS would very secure as access to the drive would be give via SSH key pairs generated locally by the bridge - with the public key being transferred to proton. The bridge could have a setting that, when turned on, would do this automatically, and ensure that the mount was persistent. The tunnel could be authenticated via SSH key pairs, generated by the bridge and rotated on a frequent basis.īefore syncing, you could ask Linux users to define a directory where the drive is synced and then encrypt it with GPG.Īnything placed in that directory would be automatically encrypted and then transferred to Proton for storage.Īnything removed from the directory would remain encrypted - but could still be decrypted by the user as the GPG key would be stored on their system and kept in their key vault.Īlternatively, you could let us mount the drive using SSHFS. LDAPS uses TLS to encrypt data while in transit and the bridge could also establish a secure encrypted tunnel using the latest encryption protocols employed by Proton, through which the TLS encrypted data was transferred.

The bridge should have a setting that when turned on adds proton contacts to Thunderbird via an LDAPS contacts directory. Although I feel that allowing the bridge to decrypt the calendar information as it passes though on its way to the local machine, and then encrypt it as it passes through on its way to Proton would be sufficient for the short term.Įspecially if this was an optional setting that made the user aware that the calendar would be decrypted by the bridge. This might be a bit complicated as there is no good way to sync secure calendars right now. There should be a setting, that when turned on creates a new calendar in Thunderbird that syncs with the Proton calendar via the bridge. Please expand the bridge so that Linux users can use it to sync all your products:Ĭalendars should sync with Calendar in Thunderbird.

Thunderbird calendar sync