Skip to content
  1. May 11, 2018
    • Matt Caswell's avatar
      Set the ossl_shim to auto retry if not running asynchronously · c3114a77
      Matt Caswell authored
      In certain circumstances in the DTLS code we have to drop a record (e.g. if
      it is a stale retransmit). We then have to move on to try and read the next
      record. Some applications using blocking sockets (e.g. s_server/s_client
      will hang if there isn't actually any data to be read from the socket yet).
      Others can tolerate this. Therefore SSL_read()/SSL_write() can sometimes
      return SSL_ERROR_WANT_READ/SSL_ERROR_WANT_WRITE even when using blocking
      sockets. Applications can use the mode SSL_MODE_AUTO_RETRY, to switch this
      behaviour off so that we never return unless we have read the data we
      wanted to.
      
      Commit ad962252
      
       fixed a DTLS problem where we always retried even if
      SSL_MODE_AUTO_RETRY was not set. However that fix caused the Boring
      ossl_shim to fail in some tests because it was relying on the previous
      (buggy) behaviour. The ossl_shim should be set into SSL_MODE_AUTO_RETRY if
      it is not operating asynchronously to avoid this problem.
      
      [extended tests]
      
      Reviewed-by: default avatarRich Salz <rsalz@openssl.org>
      (Merged from https://github.com/openssl/openssl/pull/6216)
      c3114a77
  2. May 10, 2018
  3. May 09, 2018
  4. May 08, 2018
  5. May 07, 2018
  6. May 05, 2018
  7. May 04, 2018
  8. May 03, 2018
  9. May 02, 2018