privacy preserving selfAddr (M2)
#6216
Labels
Comments
r10s
added a commit
that referenced
this issue
Nov 21, 2024
this PR adds the address to be used by the UI for `window.webxdc.selfAddr` to webxdc-info. UIs need to be changed accordingly and must not use configured_addr any longer. the address is created by sha256(private-key + rfc724_mid) , which results in different addresses for each webxdc, without the option to find out the real address of the user. this also returns the same address for a multi-device-setup - sending totally random self address around might be an alternative, however would require connectivity (both devices may be offline on first start). for existing app, after the change, there will be a new user, resulting eg. in a new highscore, otherwise, things should be mostly fine. this assumption is also important as we might change the thing another time when it comes to multi-transport. ftr, addresses look like `0f187e3f420748b03e3da76543e9a84ecff822687ce7e94f250c04c7c50398bc` now when this is merged, we need to adapt #6230 and file issues for all UI to use `info.selfAddr` closes #6216
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Design, implement and test privacy-preserving
selfAddrgeneration inside Delta Chat core.selfAddrshould not be trackable across apps, are scoped to app instances and need to work consistently in multi-device settings (i.e. theselfAddrfor a given app needs to be the same on all devices)Notes:
we should have multi-transport already in mind here, so things derived from the email address should be double-checked
while renaming
selfAddrto sth. else seems to be tempting, it leads to a lot of additional discussions and work if we want to avoid breaking changes, so this is out of scope of M2 and this issue.also out of scope of this issue is adding a
senderAddrout of the payload. however, as that would not introduce breaking changes (only rollout before the feature gets into use), we can consider that when everything else of M2/M3 is done.some previous discussion at #6097
The text was updated successfully, but these errors were encountered: