1. 28 Jan, 2017 5 commits
  2. 25 Jan, 2017 2 commits
  3. 19 Jan, 2017 4 commits
  4. 18 Jan, 2017 3 commits
  5. 16 Jan, 2017 1 commit
    • Nikias Bassen's avatar
      bplist: Disallow key nodes with non-string node types · 7a28a14c
      Nikias Bassen authored
      As reported in #86, the binary plist parser would force the type of the
      key node to be of type PLIST_KEY while the node might be of a different
      i.e. non-string type. A following plist_free() might then call free() on
      an invalid pointer; e.g. if the node is of type integer, its value would
      be considered a pointer, and free() would cause an error.
      We prevent this issue by disallowing non-string key nodes during parsing.
      7a28a14c
  6. 11 Jan, 2017 1 commit
  7. 03 Jan, 2017 3 commits
  8. 02 Jan, 2017 3 commits
  9. 01 Jan, 2017 6 commits
  10. 27 Dec, 2016 2 commits
  11. 21 Dec, 2016 3 commits
  12. 14 Dec, 2016 4 commits
  13. 28 Nov, 2016 1 commit
    • Nikias Bassen's avatar
      xplist: Fix parsing of adjacent nodes without whitespace between them · 5e8fb617
      Nikias Bassen authored
      The context position counter was increased after encountering a closing
      node, e.g. '</dict>' or after a closing '</key>' node. When a node followed
      it directly without any whitespace inbetween, e.g. </dict><key>, parsing
      would fail since the parser would look at 'key>' instead of '<key>' for the
      next node to be parsed.
      5e8fb617
  14. 27 Nov, 2016 1 commit
  15. 18 Nov, 2016 1 commit