1. 24 Apr, 2013 1 commit
  2. 20 Apr, 2013 1 commit
  3. 13 Apr, 2013 2 commits
  4. 12 Apr, 2013 1 commit
  5. 11 Apr, 2013 1 commit
  6. 09 Apr, 2013 1 commit
  7. 08 Apr, 2013 4 commits
  8. 05 Apr, 2013 1 commit
  9. 31 Mar, 2013 1 commit
  10. 27 Mar, 2013 2 commits
  11. 23 Mar, 2013 1 commit
  12. 19 Mar, 2013 1 commit
  13. 12 Mar, 2013 2 commits
  14. 09 Mar, 2013 1 commit
  15. 08 Mar, 2013 1 commit
  16. 07 Mar, 2013 3 commits
  17. 06 Mar, 2013 1 commit
  18. 16 Feb, 2013 1 commit
  19. 10 Feb, 2013 2 commits
  20. 07 Feb, 2013 1 commit
  21. 06 Feb, 2013 2 commits
  22. 05 Feb, 2013 2 commits
  23. 28 Jan, 2013 1 commit
  24. 18 Jan, 2013 2 commits
  25. 17 Jan, 2013 1 commit
  26. 15 Jan, 2013 1 commit
  27. 11 Jan, 2013 1 commit
    • Kamil Dudka's avatar
      nss: clear session cache if a client cert from file is used · b36f1d26
      Kamil Dudka authored
      This commit fixes a regression introduced in 052a08ff.
      
      NSS caches certs/keys returned by the SSL_GetClientAuthDataHook callback
      and if we connect second time to the same server, the cached cert/key
      pair is used.  If we use multiple client certificates for different
      paths on the same server, we need to clear the session cache to force
      NSS to call the hook again.  The commit 052a08ff prevented the session
      cache from being cleared if a client certificate from file was used.
      
      The condition is now fixed to cover both cases: consssl->client_nickname
      is not NULL if a client certificate from the NSS database is used and
      connssl->obj_clicert is not NULL if a client certificate from file is
      used.
      
      Review by: Kai Engert
      b36f1d26
  28. 27 Dec, 2012 1 commit