Skip to content
  1. Mar 19, 2014
    • Gaël PORTAY's avatar
      polarssl: fix possible handshake timeout issue in multi. · 47f8e99e
      Gaël PORTAY authored
      Because of the socket is unblocking, PolarSSL does need call to getsock to
      get the action to perform in multi environment.
      
      In some cases, it might happen we have not received yet all data to perform
      the handshake. ssh_handshake returns POLARSSL_ERR_NET_WANT_READ, the state
      is updated but because of the getsock has not the proper #define macro to,
      the library never prevents to select socket for input thus the socket will
      never be awaken when last data is available. Thus it leads to timeout.
      47f8e99e
  2. Mar 18, 2014
  3. Mar 17, 2014
  4. Mar 15, 2014
  5. Mar 14, 2014
  6. Mar 11, 2014
  7. Mar 10, 2014
  8. Mar 09, 2014
  9. Mar 08, 2014
  10. Mar 06, 2014
  11. Mar 05, 2014
    • Daniel Stenberg's avatar
      remote_port: allow connect to port 0 · 219a0fbe
      Daniel Stenberg authored
      Port number zero is perfectly allowed to connect to. I moved to storing
      the remote port number in an int so that -1 means undefined and 0-65535
      can be used for legitimate port numbers.
      219a0fbe
  12. Mar 03, 2014
  13. Mar 02, 2014