1. 11 2月, 2021 1 次提交
  2. 29 9月, 2019 2 次提交
    • D
      Fix header file include guard names · ae4186b0
      Dr. Matthias St. Pierre 提交于
      Make the include guards consistent by renaming them systematically according
      to the naming conventions below
      
      For the public header files (in the 'include/openssl' directory), the guard
      names try to match the path specified in the include directives, with
      all letters converted to upper case and '/' and '.' replaced by '_'. For the
      private header files files, an extra 'OSSL_' is added as prefix.
      Reviewed-by: NRichard Levitte <levitte@openssl.org>
      (Merged from https://github.com/openssl/openssl/pull/9333)
      ae4186b0
    • D
      Reorganize private crypto header files · 25f2138b
      Dr. Matthias St. Pierre 提交于
      Currently, there are two different directories which contain internal
      header files of libcrypto which are meant to be shared internally:
      
      While header files in 'include/internal' are intended to be shared
      between libcrypto and libssl, the files in 'crypto/include/internal'
      are intended to be shared inside libcrypto only.
      
      To make things complicated, the include search path is set up in such
      a way that the directive #include "internal/file.h" could refer to
      a file in either of these two directoroes. This makes it necessary
      in some cases to add a '_int.h' suffix to some files to resolve this
      ambiguity:
      
        #include "internal/file.h"      # located in 'include/internal'
        #include "internal/file_int.h"  # located in 'crypto/include/internal'
      
      This commit moves the private crypto headers from
      
        'crypto/include/internal'  to  'include/crypto'
      
      As a result, the include directives become unambiguous
      
        #include "internal/file.h"       # located in 'include/internal'
        #include "crypto/file.h"         # located in 'include/crypto'
      
      hence the superfluous '_int.h' suffixes can be stripped.
      
      The files 'store_int.h' and 'store.h' need to be treated specially;
      they are joined into a single file.
      Reviewed-by: NRichard Levitte <levitte@openssl.org>
      (Merged from https://github.com/openssl/openssl/pull/9333)
      25f2138b
  3. 06 12月, 2018 1 次提交
  4. 20 4月, 2016 1 次提交
  5. 24 2月, 2016 1 次提交
    • D
      RT4339: Fix handling of <internal/bn_conf.h> · 78c83078
      David Woodhouse 提交于
      The entire contents of <internal/bn_conf.h> are unwanted in the UEFI
      build because we have to do it differently there. To support building
      for both 32-bit and 64-bit platforms without re-running the OpenSSL
      Configure script, the EDK2 environment defines THIRTY_TWO_BIT or
      SIXTY_FOUR_BIT for itself according to the target platform.
      
      The current setup is broken, though. It checks for OPENSSL_SYS_UEFI but
      before it's actually defined, since opensslconf.h hasn't yet been
      included.
      
      Let's fix that by including opensslconf.h. And also let's move the
      bn_conf.h doesn't even need to *exist* in the UEFI build environment.
      
      This is also GH PR736.
      Signed-off-by: NRich Salz <rsalz@openssl.org>
      Reviewed-by: NTim Hudson <tjh@openssl.org>
      78c83078
  6. 26 1月, 2016 1 次提交
    • R
      Generate warning text · 9ab6fc59
      Richard Levitte 提交于
      Now that we're using templates, we should warn people not to edit the
      resulting file.  We do it through util/dofile.pl, which is enhanced
      with an option to tell what file it was called from.  We also change
      the calls so the template files are on the command line instead of
      being redirected through standard input.  That way, we can display
      something like this (example taken from include/openssl/opensslconf.h):
      
          /* WARNING: do not edit! */
          /* Generated by Configure from include/openssl/opensslconf.h.in */
      Reviewed-by: NRich Salz <rsalz@openssl.org>
      9ab6fc59
  7. 25 1月, 2016 1 次提交
  8. 05 9月, 2015 1 次提交
  9. 17 9月, 2006 1 次提交
  10. 04 6月, 1999 1 次提交
  11. 30 1月, 1999 1 次提交
  12. 24 1月, 1999 1 次提交
  13. 17 1月, 1999 1 次提交
    • D
      Time to blow up the source tree :-) This is the beginning of support for · f6aed2cd
      Dr. Stephen Henson 提交于
      GeneralizedTime. At several points PKIX specifies that GeneralizedTime can be
      used but OpenSSL doesn't currently support it. This patch adds several files
      and a bunch of functions.
      
      Of interest is the ASN1_TIME structure and its related functions. At several
      points certificates, CRLs et al specify that a time can be expressed as a
      choice of UTCTime and GeneralizedTime. Currently OpenSSL interprets this
      (wrongly) as UTCTime because GeneralizedTime isn't supported. The ASN1_TIME
      stuff provides this functionality.
      
      Still todo is to trace which cert and CRL points need an ASN1_TIME and modify
      the utilities appropriately and of course fix all the bugs.
      
      Note new OpenSSL copyright in the new file a_time.c. I didn't put it in
      a_gentm.c because it is a minimally modified form a_utctm.c .
      
      Since this adds new files and error codes you will need to do a 'make errors'
      at the top level to add the new codes.
      f6aed2cd