4 ms·
Encrypting the message AND the upload seems a no-brainer to me, if you want to call it E2EE. If the upload would not be encrypted then the (admin of the) server
by m4lvin 6y ago
Encrypting the message AND the upload seems a no-brainer to me, if you want to call it E2EE. If the upload would not be encrypted then the (admin of the) server running XEP-0363 HTTP File Upload could see the contents.
- pmlnr 6y agoI agree. The part I don't see is then what plugin should handle which part, and how. Most XMPP clients are plugin based as well. Should the OMEMO plugin then look for aesgcm:// urls, download it, and decrypt it, or should the http upload plugin look for the availability of encryption and try to decrypt?
- xorcist 6y agoClient authors should do what Conversations do. End users should probably stick with Conversations, for now. There will always be hacky and badly implemented clients. It comes with the idea of an open specification. That doesn't mean we should use them as a point of comparison.
- m4lvin 6y agoThat is only a question if HTTP upload and OMEMO are different plugins. With https://dino.im/ https://dino.im/ it also "just works" and as a user I do not care which part pf the program does what.