aguinetqb
aguinetqb
This Javascript code, when ran in a browser, properly throws an exception when trying to unwrap the modified wrapped key: ``` "use strict"; const subtle = crypto.subtle; const AESWrapKeyFormat =...
Ticket to track ideas/advances on that [known limitation](https://github.com/quarkslab/mattermost-plugin-e2ee#filesattachments-not-encrypted). Looks like using a combination of https://developers.mattermost.com/integrate/plugins/webapp/reference/#registerFilesWillUploadHook & https://developers.mattermost.com/integrate/plugins/webapp/reference/#registerFilesWillUploadHook could do the job. We will still have some limitations. For instance, Mattermost...
Ticket to track ideas/advances on that [known limitation](https://github.com/quarkslab/mattermost-plugin-e2ee#initial-support-for-notifications-from-mentions)
Ticket to track ideas/advances on that [known limitation](https://github.com/quarkslab/mattermost-plugin-e2ee#webapp-integrity).
Nothing prevents two (or more) users from sharing the same private/public key pair. We should check for this server side, and reject an already known public key. Initial report: https://twitter.com/Tangeek42/status/1449005868196958212
Currently, if someone activates e2ee on a channel but some channel members don't have a public key, the e2ee bot just post the list of these members in the channel...
Today we have two commands to setup e2ee: * /init generate a new key & publish it * /import imports a previously backuped key We have errors messages depending on...
The keylock left margin renders differently in FF vs. Chrome/Electron. Use an SVG to make sure it's always render the same.
Propose a plugin-wide configuration that would automatically activate encryption for a channel if everyone in this channel has a key setup.