1. 31 10月, 2017 1 次提交
  2. 16 10月, 2017 1 次提交
    • M
      Don't do version neg on an HRR · a2b97bdf
      Matt Caswell 提交于
      Previously if a client received an HRR then we would do version negotiation
      immediately - because we know we are going to get TLSv1.3. However this
      causes a problem when we emit the 2nd ClientHello because we start changing
      a whole load of stuff to ommit things that aren't relevant for < TLSv1.3.
      The spec requires that the 2nd ClientHello is the same except for changes
      required from the HRR. Therefore the simplest thing to do is to defer the
      version negotiation until we receive the ServerHello.
      
      Fixes #4292
      Reviewed-by: NTim Hudson <tjh@openssl.org>
      Reviewed-by: NBen Kaduk <kaduk@mit.edu>
      (Merged from https://github.com/openssl/openssl/pull/4527)
      a2b97bdf
  3. 12 10月, 2017 1 次提交
  4. 23 9月, 2017 1 次提交
    • D
      Guard against DoS in name constraints handling. · 8545051c
      David Benjamin 提交于
      This guards against the name constraints check consuming large amounts
      of CPU time when certificates in the presented chain contain an
      excessive number of names (specifically subject email names or subject
      alternative DNS names) and/or name constraints.
      
      Name constraints checking compares the names presented in a certificate
      against the name constraints included in a certificate higher up in the
      chain using two nested for loops.
      
      Move the name constraints check so that it happens after signature
      verification so peers cannot exploit this using a chain with invalid
      signatures. Also impose a hard limit on the number of name constraints
      check loop iterations to further mitigate the issue.
      
      Thanks to NCC for finding this issue. Fix written by Martin Kreichgauer.
      Reviewed-by: NRich Salz <rsalz@openssl.org>
      Reviewed-by: NAndy Polyakov <appro@openssl.org>
      (Merged from https://github.com/openssl/openssl/pull/4393)
      8545051c
  5. 04 9月, 2017 1 次提交
  6. 03 9月, 2017 1 次提交
  7. 31 8月, 2017 1 次提交
  8. 30 8月, 2017 1 次提交
  9. 25 8月, 2017 1 次提交
  10. 22 8月, 2017 2 次提交
  11. 17 8月, 2017 1 次提交
  12. 15 8月, 2017 2 次提交
  13. 12 8月, 2017 1 次提交
  14. 10 8月, 2017 1 次提交
  15. 09 8月, 2017 1 次提交
  16. 08 8月, 2017 2 次提交
  17. 04 8月, 2017 2 次提交
  18. 03 8月, 2017 2 次提交
  19. 29 7月, 2017 1 次提交
  20. 28 7月, 2017 2 次提交
  21. 27 7月, 2017 1 次提交
  22. 26 7月, 2017 2 次提交
  23. 24 7月, 2017 1 次提交
  24. 21 7月, 2017 1 次提交
  25. 19 7月, 2017 2 次提交
  26. 16 7月, 2017 3 次提交
  27. 13 7月, 2017 1 次提交
  28. 07 7月, 2017 2 次提交
  29. 29 6月, 2017 1 次提交