1. 11 Jan, 2016 1 commit
  2. 07 Apr, 2015 1 commit
  3. 06 Apr, 2015 1 commit
    • Ross Lagerwall's avatar
      tls: Add support for copying session data · 95d300ea
      Ross Lagerwall authored
      Add support for copying session data between client connections.
      This is needed for implementing FTP over SSL. Most servers use a separate
      session for each control connection and enforce sharing of each control
      connection's session between the related data connection.
      Copying session data between two connections is needed for two reasons:
      1) The data connection runs on a separate port and so has a different
      server_identity which means it would not normally share the session with
      the control connection using the session caching currently implemented.
      2) It is typical to have multiple control connections, each of which
      uses a different session with the same server_identity, so only one of
      these sessions gets stored in the cache. If a data connection is opened,
      (ignoring the port issue) it may try and reuse the wrong control
      connection's session, and fail.
      This operation is conceptually the same as OpenSSL's SSL_copy_session_id
  4. 12 Mar, 2015 1 commit
  5. 22 Nov, 2014 1 commit
    • Dan Winship's avatar
      GTlsClientConnection: loosen the semantics of "use-ssl3" · 7f5c862e
      Dan Winship authored
      If SSL 3.0 has been disabled (at the host, application, or library
      level), then the "use-ssl3" property becomes a "fail-immediately"
      Despite the name, the point of the property wasn't really specifically
      to use SSL 3.0; it was to allow fallback when talking to broken
      servers that do SSL/TLS negotiation incorrectly and break when they
      see unexpectedly-high version numbers. So if we can't fall back to SSL
      3.0, then the "use-ssl3" property should fall back to TLS 1.0 instead
      (since there are hosts that will reject a TLS 1.2 handshake, but
      accept a TLS 1.0 one).
      glib-networking is being updated to implement that behavior, so update
      the documentation here.
  6. 23 May, 2014 1 commit
  7. 20 Feb, 2014 1 commit
  8. 31 Jan, 2014 1 commit
  9. 11 Jan, 2012 1 commit
  10. 11 Aug, 2011 1 commit
  11. 20 Jun, 2011 1 commit
  12. 05 May, 2011 1 commit
  13. 05 Jan, 2011 2 commits
  14. 07 Dec, 2010 3 commits
  15. 26 Nov, 2010 1 commit