1. 06 Nov, 2013 3 commits
  2. 03 Nov, 2013 1 commit
  3. 02 Nov, 2013 1 commit
  4. 01 Nov, 2013 6 commits
    • Robin Seggelmann's avatar
      DTLS/SCTP struct authchunks Bug · b8140811
      Robin Seggelmann authored
      PR: 2809
      
      DTLS/SCTP requires DATA and FORWARD-TSN chunks to be protected with
      SCTP-AUTH.  It is checked if this has been activated successfully for
      the local and remote peer. Due to a bug, however, the
      gauth_number_of_chunks field of the authchunks struct is missing on
      FreeBSD, and was therefore not considered in the OpenSSL implementation.
      This patch sets the corresponding pointer for the check correctly
      whether or not this bug is present.
      (cherry picked from commit f596e3c491035fe80db5fc0c3ff6b647662b0003)
      b8140811
    • Robin Seggelmann's avatar
      DTLS/SCTP Finished Auth Bug · b9ef52b0
      Robin Seggelmann authored
      PR: 2808
      
      With DTLS/SCTP the SCTP extension SCTP-AUTH is used to protect DATA and
      FORWARD-TSN chunks. The key for this extension is derived from the
      master secret and changed with the next ChangeCipherSpec, whenever a new
      key has been negotiated. The following Finished then already uses the
      new key.  Unfortunately, the ChangeCipherSpec and Finished are part of
      the same flight as the ClientKeyExchange, which is necessary for the
      computation of the new secret. Hence, these messages are sent
      immediately following each other, leaving the server very little time to
      compute the new secret and pass it to SCTP before the finished arrives.
      So the Finished is likely to be discarded by SCTP and a retransmission
      becomes necessary. To prevent this issue, the Finished of the client is
      still sent with the old key.
      (cherry picked from commit 9fb523ad)
      b9ef52b0
    • Piotr Sikora's avatar
      Fix SSL_OP_SINGLE_ECDH_USE · 29b490a4
      Piotr Sikora authored
      Don't require a public key in tls1_set_ec_id if compression status is
      not needed. This fixes a bug where SSL_OP_SINGLE_ECDH_USE wouldn't work.
      (cherry picked from commit 5ff68e8f6dac3b0d8997b8bc379f9111c2bab74f)
      29b490a4
    • Dr. Stephen Henson's avatar
      Add -ecdh_single option. · a9bc1af9
      Dr. Stephen Henson authored
      Add -ecdh_single option to set SSL_OP_SINGLE_ECDH_USE on the command line.
      (cherry picked from commit f14a4a861d2d221ed565a75441a218f85b8db530)
      a9bc1af9
    • Dr. Stephen Henson's avatar
      Fix warning. · 96e16bdd
      Dr. Stephen Henson authored
      96e16bdd
    • Dr. Stephen Henson's avatar
      Fix warning. · 3f9b187b
      Dr. Stephen Henson authored
      3f9b187b
  5. 31 Oct, 2013 5 commits
  6. 28 Oct, 2013 1 commit
  7. 25 Oct, 2013 1 commit
  8. 22 Oct, 2013 5 commits
    • Lubomir Rintel's avatar
      POD: Fix list termination · ed77017b
      Lubomir Rintel authored
      This fixes problems in POD list formatting: extra or missing =back
      sequences.
      
      doc/ssl/SSL_CTX_set1_curves.pod around line 90: =back without =over
      doc/ssl/SSL_CTX_set1_verify_cert_store.pod around line 73: =back without =over
      doc/ssl/SSL_CTX_add1_chain_cert.pod around line 82: =back without =over
      doc/crypto/evp.pod around line 40: '=item' outside of any '=over'
      crypto/des/des.pod around line 184: You forgot a '=back' before '=head1'
      
      PR#3147
      ed77017b
    • Lubomir Rintel's avatar
      POD: Fix item numbering · c8919dde
      Lubomir Rintel authored
      Newer pod2man considers =item [1-9] part of a numbered list, while =item
      0 starts an unnumbered list. Add a zero effect formatting mark to override
      this.
      
      doc/apps/smime.pod around line 315: Expected text after =item, not a
      number
      ...
      
      PR#3146
      c8919dde
    • Dr. Stephen Henson's avatar
      Update test server details. · 5fdeb58c
      Dr. Stephen Henson authored
      5fdeb58c
    • Dr. Stephen Henson's avatar
      c557f921
    • Dr. Stephen Henson's avatar
      Fix argument processing. · abf840e4
      Dr. Stephen Henson authored
      abf840e4
  9. 21 Oct, 2013 5 commits
    • Dr. Stephen Henson's avatar
      Constification. · 27f3b65f
      Dr. Stephen Henson authored
      27f3b65f
    • Dr. Stephen Henson's avatar
      Update demos/bio/README · ea131a06
      Dr. Stephen Henson authored
      ea131a06
    • Ben Laurie's avatar
      Remove unused variable. · 9f944107
      Ben Laurie authored
      9f944107
    • Nick Mathewson's avatar
      2927791d
    • Nick Mathewson's avatar
      Do not include a timestamp in the Client/ServerHello Random field. · 2016265d
      Nick Mathewson authored
      Instead, send random bytes, unless SSL_SEND_{CLIENT,SERVER}RANDOM_MODE
      is set.
      
      This is a forward-port of commits:
        4af793036f6ef4f0a1078e5d7155426a98d50e37
        f4c93b46edb51da71f09eda99e83eaf193a33c08
        3da721dac9382c48812c8eba455528fd59af2eef
        2583270191a8b27eed303c03ece1da97b9b69fd3
      
      While the gmt_unix_time record was added in an ostensible attempt to
      mitigate the dangers of a bad RNG, its presence leaks the host's view
      of the current time in the clear.  This minor leak can help
      fingerprint TLS instances across networks and protocols... and what's
      worse, it's doubtful thet the gmt_unix_time record does any good at
      all for its intended purpose, since:
      
          * It's quite possible to open two TLS connections in one second.
      
          * If the PRNG output is prone to repeat itself, ephemeral
            handshakes (and who knows what else besides) are broken.
      2016265d
  10. 20 Oct, 2013 9 commits
  11. 15 Oct, 2013 3 commits