This project is mirrored from https://github.com/rbsec/sslscan.git. Pull mirroring updated .
  1. 12 May, 2022 1 commit
  2. 10 Apr, 2022 1 commit
  3. 05 Apr, 2022 1 commit
  4. 03 Apr, 2022 2 commits
  5. 31 Mar, 2022 1 commit
  6. 06 Mar, 2022 1 commit
  7. 05 Mar, 2022 4 commits
  8. 23 Feb, 2022 2 commits
  9. 16 Dec, 2021 2 commits
  10. 08 Sep, 2021 1 commit
  11. 28 Aug, 2021 1 commit
  12. 29 May, 2021 2 commits
  13. 11 May, 2021 1 commit
  14. 09 May, 2021 1 commit
    • Alex Vazquez's avatar
      Try TLS 1.2 sigalgs, even if TLS 1.3 accepts bogus ones · 876afd90
      Alex Vazquez authored
      Currently, when scanning with `--show-sigs`, it says this:
      
      ```
        Server Signature Algorithm(s):
      TLSv1.3  Server accepts all signature algorithms.
      ```
      
      I think it's reasonable for sslscan to try again with TLS 1.2. With this change, that's exactly what it does:
      
      ```
        Server Signature Algorithm(s):
      TLSv1.3  Server accepts all signature algorithms.
      TLSv1.2  Server accepts all signature algorithms.
      ```
      876afd90
  15. 27 Apr, 2021 2 commits
  16. 15 Apr, 2021 1 commit
  17. 11 Apr, 2021 1 commit
  18. 24 Mar, 2021 2 commits
  19. 06 Mar, 2021 1 commit
  20. 19 Feb, 2021 5 commits
  21. 18 Feb, 2021 2 commits
  22. 10 Feb, 2021 1 commit
  23. 09 Dec, 2020 1 commit
  24. 08 Dec, 2020 1 commit
  25. 01 Nov, 2020 1 commit
  26. 31 Oct, 2020 1 commit