1. 11 3月, 2021 1 次提交
  2. 09 9月, 2020 1 次提交
  3. 17 3月, 2020 1 次提交
  4. 06 3月, 2020 1 次提交
  5. 27 2月, 2020 1 次提交
  6. 27 1月, 2020 1 次提交
    • R
      OpenSSL::Test: bring back the relative paths · c8943eb0
      Richard Levitte 提交于
      Because there was a bug in File::Spec::Unix' abs2rel when it was given
      relative paths as both PATH and BASE arguments, the directories we
      deal with were made to be all absolute.  Unfortunately, this meant
      getting paths in our verbose test output which are difficult to use
      anywhere else (such as a separate test build made for comparison), due
      to the constant need to edit all the paths all the time.
      
      We're therefore getting back the relative paths, by doing an extra
      abs2rel() in __srctop_file, __srctop_dir, __bldtop_file and
      __bldtop_dir, with a 'Cwd::getcwd' call as BASE argument.
      
      Fixes #10628
      Reviewed-by: NMatt Caswell <matt@openssl.org>
      Reviewed-by: NMatthias St. Pierre <Matthias.St.Pierre@ncp-e.com>
      (Merged from https://github.com/openssl/openssl/pull/10913)
      
      (cherry picked from commit 612539e8a678c6099131dfd0e5e4b85fa774eb1a)
      c8943eb0
  7. 16 12月, 2019 1 次提交
  8. 15 12月, 2019 1 次提交
  9. 12 12月, 2019 1 次提交
  10. 17 11月, 2019 1 次提交
  11. 08 11月, 2019 1 次提交
  12. 15 10月, 2019 2 次提交
  13. 28 9月, 2019 2 次提交
    • D
      Add util/fix-includes script · ea21f6f8
      Dr. Matthias St. Pierre 提交于
      This script contains all adjustments to header files which were made
      during the reorganization of the header files. It is meant as an aid
      for other contributors which encounter preprocessor #include errors
      after rebasing over this pull request. Simply running
      
        util/fix-includes
      
      from the root of the source directory should hopefully fix the problem.
      
      Note: such #include errors are expected only for pull requests which
      add a lot of new code, in particular new compilation modules.
      Reviewed-by: NRichard Levitte <levitte@openssl.org>
      (Merged from https://github.com/openssl/openssl/pull/9681)
      ea21f6f8
    • D
      Fix header file include guard names · fbbfd128
      Dr. Matthias St. Pierre 提交于
      Make the include guards consistent by renaming them systematically according
      to the naming conventions below
      
      The public header files (in the 'include/openssl' directory) are not changed
      in 1.1.1, because it is a stable release.
      
      For the private header files files, the guard names try to match the path
      specified in the include directives, with all letters converted to upper case
      and '/' and '.' replaced by '_'. An extra 'OSSL_' is added as prefix.
      Reviewed-by: NRichard Levitte <levitte@openssl.org>
      (Merged from https://github.com/openssl/openssl/pull/9681)
      fbbfd128
  14. 10 9月, 2019 1 次提交
  15. 06 9月, 2019 1 次提交
  16. 19 8月, 2019 1 次提交
  17. 01 8月, 2019 2 次提交
  18. 24 7月, 2019 1 次提交
  19. 03 7月, 2019 1 次提交
    • M
      Adding Test.pm with workaround for Perl abs2rel bug · 374cab63
      Martin Peylo 提交于
      If SRCTOP != BLDTOP, and SRCTOP is given in relative form, e.g.
      "./config ../openssl", then a bug in Perl's abs2rel may trigger that directory-
      rewriting in __cwd results in wrong entries in %directories under certain
      circumstances, e.g. when a test executes run(app(["openssl"]) after indir.
      
      There should not be any need to go to a higher directory from BLDDIR or SRCDIR,
      so it should be OK to use them in their absolute form, also resolving all
      possible symlinks, right from the start.
      
      Following the File::Spec::Functions bug description (reported to perl.org):
      
      When abs2rel gets a path argument with ..s that are crossing over the ..s
      trailing the base argument, the result is wrong.
      
      Example
      PATH: /home/goal/test/..
      BASE: /home/goal/test/../../base
      Good result: ../goal
      Bad  result: ../..
      
      Bug verified with File::Spec versions
      - 3.6301
      - 3.74 (latest)
      Reviewed-by: NMatt Caswell <matt@openssl.org>
      Reviewed-by: NRichard Levitte <levitte@openssl.org>
      (Merged from https://github.com/openssl/openssl/pull/7031)
      
      (cherry picked from commit 7a2027240e1d01f7f5b209998d1de36af221b34b)
      374cab63
  20. 02 7月, 2019 1 次提交
  21. 01 7月, 2019 1 次提交
  22. 30 5月, 2019 1 次提交
  23. 28 5月, 2019 1 次提交
  24. 27 5月, 2019 1 次提交
  25. 23 5月, 2019 1 次提交
  26. 15 4月, 2019 3 次提交
  27. 21 3月, 2019 1 次提交
  28. 26 2月, 2019 1 次提交
  29. 05 2月, 2019 2 次提交
  30. 08 1月, 2019 1 次提交
    • V
      More configurable crypto and ssl library initialization · 25eb9299
      Viktor Dukhovni 提交于
      1.  In addition to overriding the default application name,
          one can now also override the configuration file name
          and flags passed to CONF_modules_load_file().
      
      2.  By default we still keep going when configuration file
          processing fails.  But, applications that want to be
          strict about initialization errors can now make explicit
          flag choices via non-null OPENSSL_INIT_SETTINGS that omit
          the CONF_MFLAGS_IGNORE_RETURN_CODES flag (which had so far
          been both undocumented and unused).
      
      3.  In OPENSSL_init_ssl() do not request OPENSSL_INIT_LOAD_CONFIG
          if the options already include OPENSSL_INIT_NO_LOAD_CONFIG.
      
      4.  Don't set up atexit() handlers when called with opts equal to
          OPENSSL_INIT_BASE_ONLY (this flag should only be used alone).
      Reviewed-by: NBernd Edlinger <bernd.edlinger@hotmail.de>
      Reviewed-by: NMatt Caswell <matt@openssl.org>
      (Merged from https://github.com/openssl/openssl/pull/7969)
      25eb9299
  31. 07 1月, 2019 1 次提交
  32. 25 11月, 2018 2 次提交
  33. 23 11月, 2018 1 次提交
    • R
      Change tarball making procedure · 48c813ef
      Richard Levitte 提交于
      Since recently, OpenSSL tarballs are produced with 'make tar' rather
      than 'make dist', as the latter has turned out to be more troublesome
      than useful.
      
      The next step to look at is why we would need to configure at all to
      produce a Makefile just to produce a tarball.  After all, the tarball
      should now only contain source files that are present even without
      configuring.
      
      Furthermore, the current method for producing tarballs is a bit
      complex, and can be greatly simplified with the right tools.  Since we
      have everything versioned with git, we might as well use the tool that
      comes with it.
      
      Added: util/mktar.sh, a simple script to produce OpenSSL tarballs.  It
      takes the options --name to modify the prefix of the distribution, and
      --tarfile tp modify the tarball file name specifically.
      
      This also adds a few entries in .gitattributes to specify files that
      should never end up in a distribution tarball.
      Reviewed-by: NMatt Caswell <matt@openssl.org>
      (Merged from https://github.com/openssl/openssl/pull/7692)
      
      (cherry picked from commit 8c209eeef426ded66ce99048f535f35d08b88462)
      48c813ef