summaryrefslogtreecommitdiff
path: root/src/or/policies.c
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2011-01-10 12:12:11 -0500
committerNick Mathewson <nickm@torproject.org>2011-01-10 12:12:11 -0500
commit373a1bc40e88d90e75f4a70b7d2018fe7288035a (patch)
tree4a95e8ab3eb5bc7b94d7681dfd6166ea2bb0ac96 /src/or/policies.c
parent729f404efec0795f7ed358e7b2fa08bd62cc1ae8 (diff)
downloadtor-373a1bc40e88d90e75f4a70b7d2018fe7288035a.tar.gz
tor-373a1bc40e88d90e75f4a70b7d2018fe7288035a.zip
Impose maximum sizes on parsed objects
An object, you'll recall, is something between -----BEGIN----- and -----END----- tags in a directory document. Some of our code, as doorss has noted in bug 2352, could assert if one of these ever overflowed SIZE_T_CEILING but not INT_MAX. As a solution, I'm setting a maximum size on a single object such that neither of these limits will ever be hit. I'm also fixing the INT_MAX checks, just to be sure.
Diffstat (limited to 'src/or/policies.c')
0 files changed, 0 insertions, 0 deletions