1. 29 Dec, 2016 1 commit
  2. 03 Mar, 2016 1 commit
    • ssh: initialize libssh2 · 22f3d3aa
      We should have been doing this, but it initializes itself upon first
      use, which works as long as nobody's doing concurrent network
      operations. Initialize it on our init to make sure it's not getting
      initialized concurrently.
      Carlos Martín Nieto committed
  3. 28 Dec, 2015 1 commit
  4. 26 Dec, 2015 1 commit
  5. 22 Dec, 2015 1 commit
  6. 14 Aug, 2015 1 commit
  7. 03 Aug, 2015 1 commit
  8. 10 Jul, 2015 1 commit
  9. 09 Jun, 2015 1 commit
  10. 02 Jun, 2015 1 commit
  11. 27 May, 2015 2 commits
  12. 20 May, 2015 2 commits
  13. 18 Mar, 2015 1 commit
  14. 10 Dec, 2014 1 commit
  15. 27 Oct, 2014 2 commits
  16. 22 Sep, 2014 1 commit
  17. 16 Sep, 2014 8 commits
  18. 04 Sep, 2014 1 commit
    • ssh: store error message immediately after a failed agent call · 2dc399a8
      When the call to the agent fails, we must retrieve the error message
      just after the function call, as other calls may overwrite it.
      
      As the agent authentication is the only one which has a teardown and
      there does not seem to be a way to get the error message from a stored
      error number, this tries to introduce some small changes to store the
      error from the agent.
      
      Clearing the error at the beginning of the loop lets us know whether the
      agent has already set the libgit2 error message and we should skip it,
      or if we should set it.
      Carlos Martín Nieto committed
  19. 05 Aug, 2014 1 commit
  20. 16 Jul, 2014 1 commit
  21. 07 Jul, 2014 1 commit
  22. 03 Jul, 2014 1 commit
  23. 02 Jul, 2014 1 commit
    • ssh: libssh2_channel_write() behaves like send() · 0963716b
      When the stream writing function was written, it assume that
      libssh2_channel_write() would always write all of the data to the
      wire. This is only true for the first 32k of data, which it tries to
      fit into one ssh packet.
      
      Since it can perform short writes, call it in a loop like we do for
      send(), advancing the buffer offset.
      Carlos Martín Nieto committed
  24. 26 Jun, 2014 2 commits
    • ssh: make sure to ask for a username and use the same one · ccb85c8f
      In order to know which authentication methods are supported/allowed by
      the ssh server, we need to send a NONE auth request, which needs a
      username associated with it.
      
      Most ssh server implementations do not allow switching the username
      between authentication attempts, which means we cannot use a dummy
      username and then switch. There are two ways around this.
      
      The first is to use a different connection, which an earlier commit
      implements, but this increases how long it takes to get set up, and
      without knowing the right username, we cannot guarantee that the
      list we get in response is the right one.
      
      The second is what's implemented here: if there is no username specified
      in the url, ask for it first. We can then ask for the list of auth
      methods and use the user's credentials in the same connection.
      Carlos Martín Nieto committed
    • ssh: request credentials again on authentication failure · d7f962f4
      Instead of completely giving up on the first failure, ask for
      credentials as long as we fail to authenticate.
      Carlos Martín Nieto committed
  25. 17 Jun, 2014 2 commits
  26. 22 Apr, 2014 1 commit
  27. 18 Apr, 2014 2 commits