Skip to content
代码片段 群组 项目
该项目从 https://github.com/intel/tinycbor 镜像。 拉取镜像更新于
  1. 8月 05, 2016
  2. 7月 31, 2016
  3. 7月 22, 2016
  4. 7月 21, 2016
  5. 7月 11, 2016
  6. 7月 09, 2016
  7. 7月 08, 2016
  8. 6月 08, 2016
  9. 6月 07, 2016
    • Thiago Macieira's avatar
      Fix warnings printed by the Microsoft compiler at -W3 · 1d00c48a
      Thiago Macieira 创作于
      
       src\cbor.h(268): warning C4244: '=': conversion from 'const uint16_t' to 'uint8_t', possible loss of data
       src\cbor.h(422): warning C4244: 'initializing': conversion from 'uint64_t' to 'uint32_t', possible loss of data
       src\cborencoder.c(134): warning C4334: '<<': result of 32-bit shift implicitly converted to 64 bits (was 64-bit shift intended?)
       src\cbortojson.c(410): warning C4244: '=': conversion from 'uint64_t' to 'double', possible loss of data
      
      Signed-off-by: default avatarThiago Macieira <thiago.macieira@intel.com>
      1d00c48a
  10. 4月 13, 2016
  11. 3月 18, 2016
  12. 2月 26, 2016
  13. 1月 04, 2016
  14. 10月 30, 2015
    • Thiago Macieira's avatar
      Fix a parsing issue caused by pointer wraparounds · 63abed98
      Thiago Macieira 创作于
      
      If the size of the string was a suitable value, the "ptr + total" check
      could overflow and we wouldn't know because the sum would most likely be
      smaller than value->parser->end. We would then proceed to allocate a
      silly amount of memory.
      
      I never caught this in my own testing because, on Linux, the heap
      usually starts in the low 4 GB of the address space, so adding
      0xffffffff000000000 would not cause an overflow. However, on OS X, the
      heap starts above 4 GB, so the pointer does wrap around.
      
      So test specifically for the pointer wraparound cases, plus the case of
      sizes larger than the address space in 32-bit systems.
      
      Signed-off-by: default avatarThiago Macieira <thiago.macieira@intel.com>
      63abed98
加载中