Re: [Standards] XEP Wishlist: Encrypted Information Storage
Le 2021-03-13 13:59, Paul Schaub a écrit : Hey everyone! It would be nice to have a way for clients to store end-to-end encrypted information on the server (imagine Private XML Storage or private PubSub nodes, but encrypted). As I heard that there are efforts of specifying ways to store signed data, I thought storage of encrypted data would come close enough to that to be discussed in the same breath. Since both signed and encrypted data would require some sort of asymmetric client/account key pair, we could define that as well? It would open the door to many very interesting use cases, one of them being a single identity key for end-to-end encryption. What do you think? Paul Hi Paul, I'll actually be working on e2ee encryption for Pubsub (including signing) this year thanks to a NLnet grant. I've only mentioned that on xsf@ and sat@ MUC rooms so far, but I'll soon publish a blog post with more details, and of course I'll reach standard@ in time to discuss that. And yeah, this will open the doors to many, many interesting things. Goffi ___ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org ___
Re: [Standards] XEP Wishlist: Encrypted Information Storage
Hiya, On Sat, 13 Mar 2021 at 13:00, Paul Schaub wrote: > Hey everyone! > > It would be nice to have a way for clients to store end-to-end encrypted > information on the server (imagine Private XML Storage or private PubSub > nodes, but encrypted). > > As I heard that there are efforts of specifying ways to store signed > data, I thought storage of encrypted data would come close enough to > that to be discussed in the same breath. > > I believe that's part of the same project, in fact. I just happened to be more interested in signed data rather than encrypted, but it is, as you say, all much the same principles. The difficulty is always in the key distribution and authentication. > Since both signed and encrypted data would require some sort of > asymmetric client/account key pair, we could define that as well? It > would open the door to many very interesting use cases, one of them > being a single identity key for end-to-end encryption. > > What do you think? > Paul > > > ___ > Standards mailing list > Info: https://mail.jabber.org/mailman/listinfo/standards > Unsubscribe: standards-unsubscr...@xmpp.org > ___ > ___ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org ___
[Standards] XEP Wishlist: Encrypted Information Storage
Hey everyone! It would be nice to have a way for clients to store end-to-end encrypted information on the server (imagine Private XML Storage or private PubSub nodes, but encrypted). As I heard that there are efforts of specifying ways to store signed data, I thought storage of encrypted data would come close enough to that to be discussed in the same breath. Since both signed and encrypted data would require some sort of asymmetric client/account key pair, we could define that as well? It would open the door to many very interesting use cases, one of them being a single identity key for end-to-end encryption. What do you think? Paul ___ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org ___
