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
{{ message }}
This repository has been archived by the owner on Dec 27, 2024. It is now read-only.
Unrecognized fields can be detected during unmarshaling of binary protobuf messages. These fields can carry sensitive data, so it seems that software should process them in a special way, such as denial of service or redirection to other parties.
Since almost all messages are signed/verified, unrecognized fields force verification failure even in case of correct signing. In this scenario sender will receive INCORRECT_SIGNATURE response status which is definitely unexpected.
I propose to think about possible reactions of applications on unrecognized fields and provide some functionality to catch/process them.
The text was updated successfully, but these errors were encountered:
Unrecognized fields can be detected during unmarshaling of binary protobuf messages. These fields can carry sensitive data, so it seems that software should process them in a special way, such as denial of service or redirection to other parties.
Since almost all messages are signed/verified, unrecognized fields force verification failure even in case of correct signing. In this scenario sender will receive
INCORRECT_SIGNATURE
response status which is definitely unexpected.I propose to think about possible reactions of applications on unrecognized fields and provide some functionality to catch/process them.
The text was updated successfully, but these errors were encountered: