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
In case of database leak it is possible to cross-reference machine-id hashes from other leaks, which is rather serious privacy issue taking into account collected data.
I suggest changing line 82 from hashed_id = hashlib.sha256(machine_id.encode()).digest()
to hashed_id = hashlib.sha256(machine_id.encode() + b"manjarodatadonor").digest()
It will change ids for machines already accounted during testing, so change should be coordinated with server-side.
The text was updated successfully, but these errors were encountered:
In case of database leak it is possible to cross-reference machine-id hashes from other leaks, which is rather serious privacy issue taking into account collected data.
What other leaks are you thinking about? Your random social media platform doesn't have access to your machine id.
In case of database leak it is possible to cross-reference machine-id hashes from other leaks, which is rather serious privacy issue taking into account collected data.
I suggest changing line 82 from
hashed_id = hashlib.sha256(machine_id.encode()).digest()
to
hashed_id = hashlib.sha256(machine_id.encode() + b"manjarodatadonor").digest()
It will change ids for machines already accounted during testing, so change should be coordinated with server-side.
The text was updated successfully, but these errors were encountered: