1. 10 Mar, 2018 2 commits
  2. 09 Mar, 2018 7 commits
  3. 04 Mar, 2018 1 commit
  4. 03 Mar, 2018 1 commit
  5. 18 Feb, 2018 2 commits
  6. 11 Feb, 2018 1 commit
  7. 06 Feb, 2018 4 commits
  8. 24 Jan, 2018 1 commit
  9. 20 Jan, 2018 1 commit
  10. 18 Jan, 2018 2 commits
  11. 24 Dec, 2017 1 commit
    • Patrick Griffis's avatar
      Rename app-id to io.github.Hexchat · 7d7be832
      Patrick Griffis authored
      RDNS syntax is recommended for applications and this matches the
      existing flatpak. Note that the dbus service and icons still need
      renaming though the former is an API breakage.
      
      Closes #2104
      Closes #2103
      7d7be832
  12. 24 Nov, 2017 1 commit
  13. 19 Nov, 2017 3 commits
  14. 18 Nov, 2017 1 commit
  15. 25 Oct, 2017 1 commit
  16. 17 Oct, 2017 1 commit
    • Joseph Bisch's avatar
      Fix oob read in ctcp_check · a3db4e57
      Joseph Bisch authored
      word[4] can be too short, leading to the addition of ctcp_offset
      putting us out of bounds. This results in an oob read in ctcp_check.
      a3db4e57
  17. 16 Oct, 2017 1 commit
  18. 11 Oct, 2017 2 commits
  19. 07 Oct, 2017 1 commit
    • Patrick Griffis's avatar
      Improve CTCP notice handling · 4188f26a
      Patrick Griffis authored
      Cutting off all text after \001 can result in users hiding text
      so lets only bother handling it if it is a valid CTCP message
      (starting and ending with \001).
      4188f26a
  20. 02 Oct, 2017 1 commit
  21. 22 Sep, 2017 1 commit
    • Joseph Bisch's avatar
      Fix rfc_ncasecmp handling of n reaching 0 · 0c494a9c
      Joseph Bisch authored
      If n becomes 0 at the same time that the end of either s1 or s2 are
      reached, the next iteration of the while loop wouldn't happen, so we
      wouldn't correctly return 0.
      0c494a9c
  22. 20 Sep, 2017 1 commit
  23. 19 Sep, 2017 2 commits
    • Joseph Bisch's avatar
      Fix rfc_{n,}casecmp functions (#2058) · 4a09ce6f
      Joseph Bisch authored
      rfc_casecmp was broken because reaching terminator for str1 was used as
      a terminal condition and str2 may be shorter than str1, resulting in an
      oob read condition for str2.
      
      rfc_ncasecmp was broken because it checked if n characters were checked
      or if BOTH pointers reached their terminator, however the strings may
      be different lengths and also less than n characters in length, meaning
      that they don't both reach their terminators at the same time,
      resulting in an oob read condition.
      4a09ce6f
    • Joseph Bisch's avatar
      Fix oob read caused by ptr[0] being NULL in inbound_notice · f4a592c4
      Joseph Bisch authored
      If ptr[0] is NULL, then strchr may return a pointer to the NULL
      terminator for serv->nick_prefixes, making the if statement true, which
      then leads to the pointer increment leaving ptr oob. Now we check to
      ensure ptr[0] != NULL.
      
      From the Linux manpages for strchr:
      The terminating null byte is considered part of the string, so that if c is
             specified as '\0', these functions return a pointer to the terminator.
      f4a592c4
  24. 17 Sep, 2017 1 commit