1. 03 Jul, 2017 1 commit
    • Make sure to always include "common.h" first · 0c7f49dd
      Next to including several files, our "common.h" header also declares
      various macros which are then used throughout the project. As such, we
      have to make sure to always include this file first in all
      implementation files. Otherwise, we might encounter problems or even
      silent behavioural differences due to macros or defines not being
      defined as they should be. So in fact, our header and implementation
      files should make sure to always include "common.h" first.
      
      This commit does so by establishing a common include pattern. Header
      files inside of "src" will now always include "common.h" as its first
      other file, separated by a newline from all the other includes to make
      it stand out as special. There are two cases for the implementation
      files. If they do have a matching header file, they will always include
      this one first, leading to "common.h" being transitively included as
      first file. If they do not have a matching header file, they instead
      include "common.h" as first file themselves.
      
      This fixes the outlined problems and will become our standard practice
      for header and source files inside of the "src/" from now on.
      Patrick Steinhardt committed
  2. 29 Dec, 2016 1 commit
  3. 19 Apr, 2016 1 commit
  4. 18 Feb, 2016 1 commit
  5. 29 May, 2015 1 commit
    • git__tolower: a tolower() that isn't dumb · 75a4636f
      Some brain damaged tolower() implementations appear to want to
      take the locale into account, and this may require taking some
      insanely aggressive lock on the locale and slowing down what should
      be the most trivial of trivial calls for people who just want to
      downcase ASCII.
      Edward Thomson committed
  6. 10 Dec, 2014 2 commits
  7. 02 Nov, 2014 1 commit
  8. 24 Sep, 2014 1 commit
  9. 16 Sep, 2014 2 commits
    • net: remove support for outright ignoring certificates · 41698f22
      This option make it easy to ignore anything about the server we're
      connecting to, which is bad security practice. This was necessary as we
      didn't use to expose detailed information about the certificate, but now
      that we do, we should get rid of this.
      
      If the user wants to ignore everything, they can still provide a
      callback which ignores all the information passed.
      Carlos Martín Nieto committed
    • Provide a callback for certificate validation · 9b940586
      If the certificate validation fails (or always in the case of ssh),
      let the user decide whether to allow the connection.
      
      The data structure passed to the user is the native certificate
      information from the underlying implementation, namely OpenSSL or
      WinHTTP.
      Carlos Martín Nieto committed
  10. 06 Jul, 2014 1 commit
  11. 03 Jul, 2014 1 commit
  12. 12 Jun, 2014 2 commits
  13. 11 Jun, 2014 2 commits
  14. 13 May, 2014 1 commit
  15. 26 Apr, 2014 3 commits
  16. 18 Nov, 2013 1 commit
  17. 13 Nov, 2013 1 commit
  18. 12 Nov, 2013 1 commit
  19. 05 Nov, 2013 3 commits
  20. 04 Nov, 2013 2 commits
  21. 02 Nov, 2013 1 commit
  22. 01 Nov, 2013 1 commit
  23. 31 Oct, 2013 2 commits
  24. 02 Oct, 2013 1 commit
  25. 26 Sep, 2013 3 commits
  26. 24 Sep, 2013 2 commits
  27. 24 Aug, 2013 1 commit