You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using the latest version v0.6.7 of Frame on Linux and I'm using the DERP website and RPC endpoint to monitor what requests Frame is sending. I see that it is including the following user agent:
That user agent is distinctly different from e.g. all other browser based wallets. IMO that is too much information that I am not willing to share with all those RPC providers. It should be possible for frame to conceal or spoof this user agent to increase user data privacy.
This is not just a privacy concern but it might even be a security concern if an RPC provider finds out which version of node/electron I am using which might be subject to specific exploits.
The text was updated successfully, but these errors were encountered:
I'm using the latest version v0.6.7 of Frame on Linux and I'm using the DERP website and RPC endpoint to monitor what requests Frame is sending. I see that it is including the following user agent:
That user agent is distinctly different from e.g. all other browser based wallets. IMO that is too much information that I am not willing to share with all those RPC providers. It should be possible for frame to conceal or spoof this user agent to increase user data privacy.
This is not just a privacy concern but it might even be a security concern if an RPC provider finds out which version of node/electron I am using which might be subject to specific exploits.
The text was updated successfully, but these errors were encountered: