1. 19 Aug, 2016 2 commits
  2. 18 Aug, 2016 1 commit
  3. 16 Aug, 2016 1 commit
  4. 15 Aug, 2016 3 commits
  5. 11 Aug, 2016 1 commit
  6. 05 Aug, 2016 2 commits
  7. 04 Aug, 2016 4 commits
  8. 03 Aug, 2016 1 commit
  9. 02 Aug, 2016 4 commits
  10. 29 Jul, 2016 1 commit
  11. 28 Jul, 2016 1 commit
  12. 26 Jul, 2016 2 commits
  13. 22 Jul, 2016 4 commits
  14. 20 Jul, 2016 1 commit
  15. 19 Jul, 2016 4 commits
  16. 18 Jul, 2016 1 commit
  17. 16 Jul, 2016 1 commit
  18. 15 Jul, 2016 1 commit
  19. 08 Jul, 2016 1 commit
  20. 06 Jul, 2016 2 commits
  21. 05 Jul, 2016 1 commit
  22. 01 Jul, 2016 1 commit
    • Matt Caswell's avatar
      Avoid an overflow in constructing the ServerKeyExchange message · 77857ddc
      Matt Caswell authored
      
      
      We calculate the size required for the ServerKeyExchange message and then
      call BUF_MEM_grow_clean() on the buffer. However we fail to take account of
      2 bytes required for the signature algorithm and 2 bytes for the signature
      length, i.e. we could overflow by 4 bytes. In reality this won't happen
      because the buffer is pre-allocated to a large size that means it should be
      big enough anyway.
      
      Addresses an OCAP Audit issue.
      
      Reviewed-by: default avatarRich Salz <rsalz@openssl.org>
      77857ddc