1. 18 Apr, 2018 6 commits
  2. 17 Apr, 2018 20 commits
  3. 16 Apr, 2018 4 commits
  4. 15 Apr, 2018 2 commits
  5. 14 Apr, 2018 3 commits
  6. 13 Apr, 2018 5 commits
    • Richard Levitte's avatar
      make update · 560096f8
      Richard Levitte authored
      
      
      Reviewed-by: default avatarMatt Caswell <matt@openssl.org>
      (Merged from https://github.com/openssl/openssl/pull/5948)
      560096f8
    • Dr. Matthias St. Pierre's avatar
      DRBG: implement a get_nonce() callback · 5bc6bcf8
      Dr. Matthias St. Pierre authored
      
      
      Fixes #5849
      
      In pull request #5503 a fallback was added which adds a random nonce of
      security_strength/2 bits if no nonce callback is provided. This change raised
      the entropy requirements form 256 to 384 bit, which can cause problems on some
      platforms (e.g. VMS, see issue #5849).
      
      The requirements for the nonce are given in section 8.6.7 of NIST SP 800-90Ar1:
      
        A nonce may be required in the construction of a seed during instantiation
        in order to provide a security cushion to block certain attacks.
        The nonce shall be either:
      
        a) A value with at least (security_strength/2) bits of entropy, or
      
        b) A value that is expected to repeat no more often than a
           (security_strength/2)-bit random string would be expected to repeat.
      
        Each nonce shall be unique to the cryptographic module in which instantiation
        is performed, but need not be secret. When used, the nonce shall be considered
        to be a critical security parameter.
      
      This commit implements a nonce of type b) in order to lower the entropy
      requirements during instantiation back to 256 bits.
      
      The formulation "shall be unique to the cryptographic module" above implies
      that the nonce needs to be unique among (with high probability) among all
      DRBG instances in "space" and "time". We try to achieve this goal by creating a
      nonce of the following form
      
          nonce = app-specific-data || high-resolution-utc-timestamp || counter
      
      Where || denotes concatenation. The application specific data can be something
      like the process or group id of the application. A utc timestamp is used because
      it increases monotonically, provided the system time is synchronized. This approach
      may not be perfect yet for a FIPS evaluation, but it should be good enough for the
      moment.
      
      This commit also harmonizes the implementation of the get_nonce() and the
      get_additional_data() callbacks and moves the platform specific parts from
      rand_lib.c into rand_unix.c, rand_win.c, and rand_vms.c.
      
      Reviewed-by: default avatarRichard Levitte <levitte@openssl.org>
      (Merged from https://github.com/openssl/openssl/pull/5920)
      5bc6bcf8
    • Bernd Edlinger's avatar
      Rework partial packet handling once more · 0e3ecaec
      Bernd Edlinger authored
      Address the concern that commit c53c2fec
      
       raised differently.
      
      The original direction of the traffic is encoded in bit 0
      of the flight number.
      
      Reviewed-by: default avatarAndy Polyakov <appro@openssl.org>
      Reviewed-by: default avatarRichard Levitte <levitte@openssl.org>
      Reviewed-by: default avatarRich Salz <rsalz@openssl.org>
      (Merged from https://github.com/openssl/openssl/pull/5923)
      0e3ecaec
    • Richard Levitte's avatar
      test/recipes/test_genrsa.t : don't fail because of size limit changes · 1b9f41a0
      Richard Levitte authored
      
      
      There is a test to check that 'genrsa' doesn't accept absurdly low
      number of bits.  Apart from that, this test is designed to check the
      working functionality of 'openssl genrsa', so instead of having a hard
      coded lower limit on the size key, let's figure out what it is.
      
      Partially fixes #5751
      
      Reviewed-by: default avatarPaul Dale <paul.dale@oracle.com>
      (Merged from https://github.com/openssl/openssl/pull/5754)
      
      (cherry picked from commit ec46830f)
      1b9f41a0
    • Richard Levitte's avatar
      Split the scrypt and RSA-PSS into man3 and man7 pages · a8ca496d
      Richard Levitte authored
      
      
      The scrypt and RSA-PSS documents were a mixture of section 3 and
      section 7 material.  With pre-1.1.1 OpenSSL, this is understandable,
      since we had a different directory layout.  With 1.1.1, we've moved to
      the typical man-page directory layout, and the documents need to be
      updated accordingly.
      
      Also, the scrypt document contained a description of
      EVP_PKEY_CTX_set1_pbe_pass(), which is a generic function rather than
      an scrypt specific function, and therefore should be documented
      separately.
      
      Fixes #5802
      
      Reviewed-by: default avatarMatt Caswell <matt@openssl.org>
      (Merged from https://github.com/openssl/openssl/pull/5942)
      a8ca496d