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
Today you can binary-and a subset or all namefilters in the private filesystem without access to read keys. This can reveal some information.
We should instead just add a public salt to namefilters and use that salt when hashing for its indices. This makes it very unlikely that the binary and of two namefilters has meaningful information, since most likely their salts are different & that completely scrambles them.
We also use namefilters as a consistent naming scheme - sort of like a pointer machine. So we need to make sure that we keep having consistent namefilters for newer revisions. We can't re-use the same salt for all versions, but we can derive some uniformly random salt from the internal ratchet.
The text was updated successfully, but these errors were encountered:
Today you can binary-and a subset or all namefilters in the private filesystem without access to read keys. This can reveal some information.
We should instead just add a public salt to namefilters and use that salt when hashing for its indices. This makes it very unlikely that the binary and of two namefilters has meaningful information, since most likely their salts are different & that completely scrambles them.
We also use namefilters as a consistent naming scheme - sort of like a pointer machine. So we need to make sure that we keep having consistent namefilters for newer revisions. We can't re-use the same salt for all versions, but we can derive some uniformly random salt from the internal ratchet.
The text was updated successfully, but these errors were encountered: