summaryrefslogtreecommitdiff
path: root/doc/state-contents.txt
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2012-03-30 10:34:05 -0400
committerNick Mathewson <nickm@torproject.org>2012-03-30 10:34:05 -0400
commit56e0959d2ab9cae45d39c5b9d72b1bb1b8ad03b7 (patch)
treeac7c4cb7ece2df9fea2307f8690741c939e00559 /doc/state-contents.txt
parent88caa552cc3742189124c297e7cf65ac5e5ef332 (diff)
downloadtor-56e0959d2ab9cae45d39c5b9d72b1bb1b8ad03b7.tar.gz
tor-56e0959d2ab9cae45d39c5b9d72b1bb1b8ad03b7.zip
Have tor_parse_*long functions check for negative bases
One of our unit tests checks that they behave correctly (giving an error) when the base is negative. But there isn't a guarantee that strtol and friends actually handle negative bases correctly. Found by Coverity Scan; fix for CID 504.
Diffstat (limited to 'doc/state-contents.txt')
0 files changed, 0 insertions, 0 deletions