-
msavoritias
the roster is uploaded on the server for presence purposes, usability (remote stuff, add roster by default and such) and being available on all devices right?
-
msavoritias
at least thats the main reasons i can think of
-
msavoritias
right the rfc says about devices
-
jonas’
pretty much yes
-
msavoritias
noted
-
jonas’
some people have prototyped or discussed an encrypted-at-rest roster
-
msavoritias
so only one client can decrypt it? That sounds complicated /thinking✎ -
msavoritias
so only the client can decrypt it? That sounds complicated /thinking ✏
-
jonas’
no
-
jonas’
the server can decrypt it but only after the client has authenticated
-
jonas’
the idea would be that you trust your server to some extent, but don't want to be caught up in a random data breach
-
msavoritias
ah so when all clients are offline then the roster is encrypted?
-
jonas’
yes
-
jonas’
the data on disk is encrypted, and the data is only kept in memory while at least one session is connected.
-
msavoritias
makes sense
-
jonas’
with always-online clients that's less useful than it used to be, but it helps with dormant/inactive account data being vulnerable.
-
msavoritias
yeah
-
Zash
Or just full disk encryption
-
jonas’
FDE is the "pull disk from server" case, not "random data breach"