1. 08 Nov, 2020 1 commit
  2. 29 Oct, 2020 1 commit
  3. 28 Oct, 2020 1 commit
  4. 26 Oct, 2020 3 commits
  5. 24 Oct, 2020 1 commit
  6. 23 Oct, 2020 1 commit
  7. 22 Oct, 2020 1 commit
  8. 20 Oct, 2020 1 commit
  9. 18 Oct, 2020 1 commit
  10. 17 Oct, 2020 3 commits
  11. 15 Oct, 2020 1 commit
  12. 14 Oct, 2020 1 commit
  13. 13 Oct, 2020 1 commit
  14. 12 Oct, 2020 3 commits
  15. 10 Oct, 2020 1 commit
  16. 08 Oct, 2020 1 commit
  17. 07 Oct, 2020 2 commits
    • Friedrich W. H. Kossebau's avatar
      Store & fetch channel key as UTF-8 consistently · 5ec9ea36
      Friedrich W. H. Kossebau authored
      While it seems not specified by protocol if the key should match
      the channel encoding, Konversation's "showkey" command handler
      assumes UTF-8 by implicitly using fromUtf8 decoding due to the
      QString(QByteArray) constructor.
      Also does current code of Cipher::setKey already assume some codec
      compatible to 7-bit when checking the first 4 bytes for "ecb:" or "cbc:".
      
      Explicitly converting fromUtf8 and always using toUtf8 at least improves
      consistency in the current code.
      5ec9ea36
    • Friedrich W. H. Kossebau's avatar
      Remove unneeded and potentially encoding switching re-encoding of key · 815d80ac
      Friedrich W. H. Kossebau authored
      getKeyForRecipient() returns the raw QByteArray, which got assigned
      to the QString cipherKey by operator=(const QByteArray&), which uses
      fromUtf8().
      Converting the key back to QByteArray using toLocal8Bit() will result
      in a changed and thus broken key on systems not using UTF-8.
      There is no need for conversion to and from QString at all though.
      815d80ac
  18. 05 Oct, 2020 1 commit
    • Friedrich W. H. Kossebau's avatar
      Fix content of line with incomplete encoding · 73e566fa
      Friedrich W. H. Kossebau authored
      newline is a QString. Assigning the return type of codec->fromUnicode()
      which is a QByteArray invokes the fromUtf8 conversion. Which is the wrong
      encoding, as the returned QByteArray does not hold the string in UTF-8
      but the very encoding of the used coded.
      73e566fa
  19. 01 Oct, 2020 3 commits
  20. 30 Sep, 2020 1 commit
  21. 29 Sep, 2020 2 commits
  22. 28 Sep, 2020 2 commits
  23. 27 Sep, 2020 1 commit
  24. 23 Sep, 2020 1 commit
    • Friedrich W. H. Kossebau's avatar
      Fix loading of nick icon theme to deal with multiple copies · e5a3c134
      Friedrich W. H. Kossebau authored
      The old code first collected any PNG files found in all the subdirs
      matching the given theme name. In case of multiple installations, like
      once globally and once user-locally, that results in the respective
      multiple numbers of PNG files listed, breaking assumptions later in the
      code and actually triggering some safety checks, resulting in no nick
      iconss loaded at all.
      e5a3c134
  25. 22 Sep, 2020 4 commits
  26. 21 Sep, 2020 1 commit