Add simple range constraints to Mojo IDL |
||||||
Issue descriptionThis would make security auditing tremendously simpler. The basic idea is optional annotations for a maximum length on strings, vectors, and buffers. We should also be able to specify an optional max and min for any numeric values. These constraints would then be enforced by mojo at the marshalling level, probably on both ends in debug builds and on the receiving end only in release builds.
,
Jan 9 2017
,
May 29 2017
,
May 29 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 17
,
Nov 15
Something to consider for near future work. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by ranjitkan@chromium.org
, Dec 13 2016