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
Since this issue was opened, the hash.* field set has grown and guidance added that entity-specific hashes should be placed in their related fieldset (for example, ja3 is underneath tls.*).
I can see value to having the various hash.* types to hash the value of the user.*. However, I also see value in how the current user.hash field is described: "Unique user hash to correlate information for a user in anonymized form.".
Having a single field remain that holds the "anonymised" value of the user.name or user.id seems useful. Any thoughts?
#426 added hash.* fields but "user" already contains hash. So user.hash should become user.hash.*.
The text was updated successfully, but these errors were encountered: