1. 12 12月, 2019 1 次提交
  2. 20 11月, 2019 1 次提交
  3. 08 11月, 2019 1 次提交
  4. 06 12月, 2018 1 次提交
  5. 13 2月, 2018 1 次提交
  6. 01 2月, 2018 1 次提交
  7. 08 12月, 2017 1 次提交
  8. 18 10月, 2017 1 次提交
  9. 25 8月, 2017 3 次提交
  10. 17 7月, 2017 2 次提交
  11. 03 7月, 2017 1 次提交
  12. 13 6月, 2017 1 次提交
  13. 31 5月, 2017 1 次提交
  14. 29 3月, 2017 1 次提交
  15. 28 3月, 2017 1 次提交
  16. 03 3月, 2017 1 次提交
  17. 21 1月, 2017 1 次提交
  18. 15 10月, 2016 1 次提交
  19. 15 9月, 2016 2 次提交
  20. 14 9月, 2016 1 次提交
  21. 01 8月, 2016 1 次提交
  22. 20 7月, 2016 2 次提交
  23. 15 7月, 2016 1 次提交
  24. 18 5月, 2016 1 次提交
  25. 27 4月, 2016 1 次提交
  26. 31 3月, 2016 2 次提交
  27. 17 12月, 2015 1 次提交
    • R
      Rename some BUF_xxx to OPENSSL_xxx · 7644a9ae
      Rich Salz 提交于
      Rename BUF_{strdup,strlcat,strlcpy,memdup,strndup,strnlen}
      to OPENSSL_{strdup,strlcat,strlcpy,memdup,strndup,strnlen}
      Add #define's for the old names.
      Add CRYPTO_{memdup,strndup}, called by OPENSSL_{memdup,strndup} macros.
      Reviewed-by: NTim Hudson <tjh@openssl.org>
      7644a9ae
  28. 08 12月, 2015 2 次提交
  29. 13 10月, 2015 1 次提交
    • M
      Centralise loading default apps config file · a0a82324
      Matt Caswell 提交于
      Loading the config file after processing command line options can
      cause problems, e.g. where an engine provides new ciphers/digests
      these are not then recoginised on the command line. Move the
      default config file loading to before the command line option
      processing. Whilst we're doing this we might as well centralise
      this instead of doing it individually for each application. Finally
      if we do it before the OpenSSL_add_ssl_algorithms() call then
      ciphersuites provided by an engine (e.g. GOST) can be available to
      the apps.
      
      RT#4085
      RT#4086
      Reviewed-by: NRichard Levitte <levitte@openssl.org>
      a0a82324
  30. 06 9月, 2015 1 次提交
    • R
      Change the way apps open their input and output files · bdd58d98
      Richard Levitte 提交于
      The different apps had the liberty to decide whether they would open their
      input and output files in binary mode or not, which could be confusing if
      two different apps were handling the same type of file in different ways.
      
      The solution is to centralise the decision of low level file organisation,
      and that the apps would use a selection of formats to state the intent of
      the file.
      Reviewed-by: NTim Hudson <tjh@openssl.org>
      bdd58d98
  31. 16 6月, 2015 1 次提交
    • R
      RT2547: Tighten perms on generated privkey files · 3b061a00
      Rich Salz 提交于
      When generating a private key, try to make the output file be readable
      only by the owner.  Put it in CHANGES file since it might be noticeable.
      
      Add "int private" flag to apps that write private keys, and check that it's
      set whenever we do write a private key.  Checked via assert so that this
      bug (security-related) gets fixed.  Thanks to Viktor for help in tracing
      the code-paths where private keys are written.
      Reviewed-by: NViktor Dukhovni <viktor@openssl.org>
      3b061a00
  32. 10 6月, 2015 1 次提交
  33. 03 6月, 2015 1 次提交
    • R
      Standardize handling of #ifdef'd options. · 9c3bcfa0
      Rich Salz 提交于
      Here are the "rules" for handling flags that depend on #ifdef:
      
      - Do not ifdef the enum.  Only ifdef the OPTIONS table.  All ifdef'd
        entries appear at the end; by convention "engine" is last.  This
        ensures that at run-time, the flag will never be recognized/allowed.
        The next two bullets entries are for silencing compiler warnings:
      - In the while/switch parsing statement, use #ifdef for the body to
        disable it; leave the "case OPT_xxx:" and "break" statements outside
        the ifdef/ifndef.  See ciphers.c for example.
      - If there are multiple options controlled by a single guard, OPT_FOO,
        OPT_BAR, etc., put a an #ifdef around the set, and then do "#else"
        and a series of case labels and a break. See OPENSSL_NO_AES in cms.c
        for example.
      Reviewed-by: NMatt Caswell <matt@openssl.org>
      9c3bcfa0