1. 03 Apr, 2018 3 commits
  2. 28 Mar, 2018 1 commit
  3. 27 Mar, 2018 7 commits
  4. 26 Mar, 2018 2 commits
  5. 25 Mar, 2018 1 commit
  6. 21 Mar, 2018 4 commits
  7. 20 Mar, 2018 1 commit
  8. 15 Mar, 2018 5 commits
  9. 14 Mar, 2018 1 commit
  10. 12 Mar, 2018 2 commits
  11. 11 Mar, 2018 1 commit
  12. 08 Mar, 2018 1 commit
  13. 07 Mar, 2018 1 commit
  14. 05 Mar, 2018 1 commit
  15. 04 Mar, 2018 1 commit
  16. 03 Mar, 2018 1 commit
  17. 02 Mar, 2018 1 commit
  18. 01 Mar, 2018 1 commit
  19. 26 Feb, 2018 1 commit
    • Dr. Matthias St. Pierre's avatar
      bio_b64.c: prevent base64 filter BIO from decoding out-of-bound data · b3f9b401
      Dr. Matthias St. Pierre authored
      Fixes #5405, #1381
      
      The base64 filter BIO reads its input in chunks of B64_BLOCK_SIZE bytes.
      When processing input in PEM format it can happen in rare cases that
      
      - the trailing PEM marker crosses the boundary of a chunk, and
      - the beginning of the following chunk contains valid base64 encoded data.
      
      This happened in issue #5405, where the PEM marker was split into
      "-----END CER" and "TIFICATE-----" at the end of the first chunk.
      
      The decoding of the first chunk terminated correctly at the '-' character,
      which is treated as an EOF marker, and b64_read() returned. However,
      when called the second time, b64_read() read the next chunk and interpreted
      the string "TIFICATE" as valid base64 encoded data, adding 6 extra bytes
      '4c 81 48 08 04 c4'.
      
      This patch restores the assignment of the error code to 'ctx->cont', which
      was deleted accidentally in commit 5562cfac and which prevents b64_read()
      from reading additional data on subsequent calls...
      b3f9b401
  20. 22 Feb, 2018 2 commits
  21. 21 Feb, 2018 2 commits