feat(client): hashed targets #2
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
To improve privacy, the observatory client should support hashing targets before setting/fetching. Hashing targets would mean that it's harder for an operator to pry information directly from the database or for someone to just iterate over the database and re-construct it.
Of course, by nature of observatory basically just being a tracked key store, clients can just not send hashed entities, and there's nothing the server can do about it. Hashing on the server-side would get expensive quick, and at the volume of requests i've seen to observatory, would likely end up slowing the service down. Doing it on the client would also mean the server never sees the unhashed tartget.
feat: hashed targetsto feat(client): hashed targets