Hedgehog release (v2.7.0)

image courtesy of pixabay

Goals

This release overlapped with the publication and presentation of a paper written about CryptPad’s architecture. As such, we didn’t plan for any very ambitious new features, and instead focused on bug fixes and some new workflows.

Update notes

This is a fairly simple release. Just download the latest commits and update your cache-busting string.

Features

• In order to address some privacy concerns, we’ve changed CryptPad such that pads are not immediately stored in your CryptDrive as soon as you open them. Instead, users are presented with a prompt in the bottom-right corner which asks them whether they’d like to store it manually. Alternatively, you can use your settings page to revert to the old automatic behaviour, or choose not to store, and to never be asked.
• It was brought to our attention that it was possible to upload base64-encoded images in the rich text editor. These images had a negative performance impact on such pads. From now on, if these images are detected in a pad, users are prompted to run a migration to convert them to uploaded (and encrypted) files.
• We’ve added a progress bar which is displayed while you are loading a pad, as we found that it was not very clear whether large pads were loading, or if they had become unresponsive due to a bug.
• We’ve added an option to allow users to right-click uploaded files wherever they appear, and to store that file in their CryptDrive.
• We’ve improved the dialog which is used to modify the properties of encrypted media embedded within rich text pads.

Bug fixes

• Due to a particularly disastrous bug in Chrome 68 which was unfortunately beyond our power to fix, we’ve added a warning for anyone affected by that bug to let them know the cause.
• We’ve increased the module loading timeout value used by requirejs in our sharedWorker implementation to match the value used by the rest of CryptPad.