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
Object header has payload checksums (not a homomorphic one) and there is no restriction about hashing algorithm. However, in practice, it is fixed and there is no sense in using TZ hash in regular hashing.
Object header has payload checksums (not a homomorphic one) and there is no restriction about hashing algorithm. However, in practice, it is fixed and there is no sense in using TZ hash in regular hashing.
Current Behavior
Hash is not fixed and our nodes' behavior is undefined if we meet such objects. E.g., it is impossible to search by such hashes: https://github.com/nspcc-dev/neofs-sdk-go/blob/256513c1b29bbb59326eecdc0ae669cc67e33155/object/search.go#L336-L341.
Expected Behavior
Objects hashing with any algo that is not sha256 should be prohibited.
Possible Solution
Add comments to this field.
Steps to Reproduce
Use your eyes, look at
neofs-api/object/types.proto
Lines 87 to 88 in 01229b4
Regression
No.
The text was updated successfully, but these errors were encountered: