1. 26 Apr, 2017 1 commit
    • socket_stream: continue to next addrinfo on socket creation failure · 954e06a8
      When connecting to a remote via socket stream, we first use getaddrinfo
      to obtain the possible connection methods followed by creating and
      connecting the socket. But when creating the socket, we error out as
      soon as we get an invalid socket instead of trying out other address
      hints returned by addrinfo.
      
      Fix this by continuing on invalid socket instead of returning an error.
      This fixes connection establishment with musl libc.
      Patrick Steinhardt committed
  2. 29 Dec, 2016 1 commit
  3. 10 Dec, 2014 4 commits
    • gitno: remove code which is no longer needed · 1b75c29e
      Most of the network-facing facilities have been copied to the socket and
      openssl streams. No code now uses these functions directly anymore, so
      we can now remove them.
      Carlos Martín Nieto committed
    • Add an OpenSSL IO stream · 468d7b11
      This unfortunately isn't as stackable as could be possible, as it
      hard-codes the socket stream. This is because the method of using a
      custom openssl BIO is not clear, and we do not need this for now. We can
      still bring this in if and as we need it.
      Carlos Martín Nieto committed
    • Introduce stackable IO streams · dd4ff2c9
      We currently have gitno for talking over TCP, but this needs to know
      about both plaintext and OpenSSL connections and the code has gotten
      somewhat messy with ifdefs determining which version of the function
      should be called.
      
      In order to clean this up and abstract away the details of sending over
      the different types of streams, we can instead use an interface and
      stack stream implementations.
      
      We may not be able to use the stackability with all streams, but we
      are definitely be able to use the abstraction which is currently spread
      between different bits of gitno.
      Carlos Martín Nieto committed