4 This document describes installation on all supported operating
5 systems (the Unix/Linux family (which includes Mac OS/X), OpenVMS,
8 To install OpenSSL, you will need:
10 * A make implementation
11 * Perl 5 with core modules (please read NOTES.PERL)
12 * The perl module Text::Template (please read NOTES.PERL)
14 * a development environment in the form of development libraries and C
16 * a supported operating system
18 For additional platform specific requirements, solutions to specific
19 issues and other details, please read one of these:
21 * NOTES.UNIX (any supported Unix like system)
23 * NOTES.WIN (any supported Windows)
24 * NOTES.DJGPP (DOS platform with DJGPP)
25 * NOTES.ANDROID (obviously Android [NDK])
26 * NOTES.VALGRIND (testing with Valgrind)
28 Notational conventions in this document
29 ---------------------------------------
31 Throughout this document, we use the following conventions in command
34 $ command Any line starting with a dollar sign
35 ($) is a command line.
37 { word1 | word2 | word3 } This denotes a mandatory choice, to be
38 replaced with one of the given words.
39 A simple example would be this:
41 $ echo { FOO | BAR | COOKIE }
43 which is to be understood as one of
52 [ word1 | word2 | word3 ] Similar to { word1 | word2 | word3 }
53 except it's optional to give any of
54 those. In addition to the examples
55 above, this would also be valid:
59 {{ target }} This denotes a mandatory word or
60 sequence of words of some sort. A
61 simple example would be this:
65 which is to be understood to use the
66 command 'type' on some file name
67 determined by the user.
69 [[ options ]] Similar to {{ target }}, but is
72 Note that the notation assumes spaces around {, }, [, ], {{, }} and
73 [[, ]]. This is to differentiate from OpenVMS directory
74 specifications, which also use [ and ], but without spaces.
79 If you want to just get on with it, do:
81 on Unix (again, this includes Mac OS/X):
95 on Windows (only pick one of the targets for configuration):
97 $ perl Configure { VC-WIN32 | VC-WIN64A | VC-WIN64I | VC-CE }
102 If any of these steps fails, see section Installation in Detail below.
104 This will build and install OpenSSL in the default location, which is:
106 Unix: normal installation directories under /usr/local
107 OpenVMS: SYS$COMMON:[OPENSSL-'version'...], where 'version' is the
108 OpenSSL version number with underscores instead of periods.
109 Windows: C:\Program Files\OpenSSL or C:\Program Files (x86)\OpenSSL
111 If you want to install it anywhere else, run config like this:
115 $ ./config --prefix=/opt/openssl --openssldir=/usr/local/ssl
119 $ @config --prefix=PROGRAM:[INSTALLS] --openssldir=SYS$MANAGER:[OPENSSL]
121 (Note: if you do add options to the configuration command, please make sure
122 you've read more than just this Quick Start, such as relevant NOTES.* files,
123 the options outline below, as configuration options may change the outcome
124 in otherwise unexpected ways)
127 Configuration Options
128 ---------------------
130 There are several options to ./config (or ./Configure) to customize
131 the build (note that for Windows, the defaults for --prefix and
132 --openssldir depend in what configuration is used and what Windows
133 implementation OpenSSL is built on. More notes on this in NOTES.WIN):
136 Don't build with support for deprecated APIs below the
137 specified version number. For example "--api=1.1.0" will
138 remove support for all APIS that were deprecated in OpenSSL
139 version 1.1.0 or below.
141 --cross-compile-prefix=PREFIX
142 The PREFIX to include in front of commands for your
143 toolchain. It's likely to have to end with dash, e.g.
144 a-b-c- would invoke GNU compiler as a-b-c-gcc, etc.
145 Unfortunately cross-compiling is too case-specific to
146 put together one-size-fits-all instructions. You might
147 have to pass more flags or set up environment variables
148 to actually make it work. Android and iOS cases are
149 discussed in corresponding Configurations/15-*.conf
150 files. But there are cases when this option alone is
151 sufficient. For example to build the mingw64 target on
152 Linux "--cross-compile-prefix=x86_64-w64-mingw32-"
153 works. Naturally provided that mingw packages are
154 installed. Today Debian and Ubuntu users have option to
155 install a number of prepackaged cross-compilers along
156 with corresponding run-time and development packages for
157 "alien" hardware. To give another example
158 "--cross-compile-prefix=mipsel-linux-gnu-" suffices
159 in such case. Needless to mention that you have to
160 invoke ./Configure, not ./config, and pass your target
161 name explicitly. Also, note that --openssldir refers
162 to target's file system, not one you are building on.
165 Build OpenSSL with debugging symbols and zero optimization
169 The name of the directory under the top of the installation
170 directory tree (see the --prefix option) where libraries will
171 be installed. By default this is "lib". Note that on Windows
172 only ".lib" files will be stored in this location. dll files
173 will always be installed to the "bin" directory.
176 Directory for OpenSSL configuration files, and also the
177 default certificate and key store. Defaults are:
180 Windows: C:\Program Files\Common Files\SSL
181 or C:\Program Files (x86)\Common Files\SSL
182 OpenVMS: SYS$COMMON:[OPENSSL-COMMON]
185 The top of the installation directory tree. Defaults are:
188 Windows: C:\Program Files\OpenSSL
189 or C:\Program Files (x86)\OpenSSL
190 OpenVMS: SYS$COMMON:[OPENSSL-'version']
193 Build OpenSSL without debugging symbols. This is the default.
196 This is a developer flag that switches on various compiler
197 options recommended for OpenSSL development. It only works
198 when using gcc or clang as the compiler. If you are
199 developing a patch for OpenSSL then it is recommended that
200 you use this option where possible.
202 --with-zlib-include=DIR
203 The directory for the location of the zlib include file. This
204 option is only necessary if enable-zlib (see below) is used
205 and the include file is not already on the system include
209 On Unix: this is the directory containing the zlib library.
210 If not provided the system library path will be used.
211 On Windows: this is the filename of the zlib library (with or
212 without a path). This flag must be provided if the
213 zlib-dynamic option is not also used. If zlib-dynamic is used
214 then this flag is optional and a default value ("ZLIB1") is
215 used if not provided.
216 On VMS: this is the filename of the zlib library (with or
217 without a path). This flag is optional and if not provided
218 then "GNV$LIBZSHR", "GNV$LIBZSHR32" or "GNV$LIBZSHR64" is
219 used by default depending on the pointer size chosen.
222 --with-rand-seed=seed1[,seed2,...]
223 A comma separated list of seeding methods which will be tried
224 by OpenSSL in order to obtain random input (a.k.a "entropy")
225 for seeding its cryptographically secure random number
226 generator (CSPRNG). The current seeding methods are:
228 os: Use a trusted operating system entropy source.
229 This is the default method if such an entropy
231 getrandom: Use the L<getrandom(2)> or equivalent system
233 devrandom: Use the the first device from the DEVRANDOM list
234 which can be opened to read random bytes. The
235 DEVRANDOM preprocessor constant expands to
236 "/dev/urandom","/dev/random","/dev/srandom" on
237 most unix-ish operating systems.
238 egd: Check for an entropy generating daemon.
239 rdcpu: Use the RDSEED or RDRAND command if provided by
241 librandom: Use librandom (not implemented yet).
242 none: Disable automatic seeding. This is the default
243 on some operating systems where no suitable
244 entropy source exists, or no support for it is
247 For more information, see the section 'Note on random number
248 generation' at the end of this document.
251 Don't build the AFALG engine. This option will be forced if
252 on a platform that does not support AFALG.
255 Build with Kernel TLS support. This option will enable the
256 use of the Kernel TLS data-path, which can improve
257 performance and allow for the use of sendfile and splice
258 system calls on TLS sockets. The Kernel may use TLS
259 accelerators if any are available on the system.
260 This option will be forced off on systems that do not support
261 the Kernel TLS data-path.
264 Build with the Address sanitiser. This is a developer option
265 only. It may not work on all platforms and should never be
266 used in production environments. It will only work when used
267 with gcc or clang and should be used in conjunction with the
271 Do not use assembler code. This should be viewed as
272 debugging/trouble-shooting option rather than production.
273 On some platforms a small amount of assembler code may
274 still be used even with this option.
277 Do not build support for async operations.
280 Don't automatically load all supported ciphers and digests.
281 Typically OpenSSL will make available all of its supported
282 ciphers and digests. For a statically linked application this
283 may be undesirable if small executable size is an objective.
284 This only affects libcrypto. Ciphers and digests will have to
285 be loaded manually using EVP_add_cipher() and
286 EVP_add_digest() if this option is used. This option will
287 force a non-shared build.
290 Don't automatically load all libcrypto/libssl error strings.
291 Typically OpenSSL will automatically load human readable
292 error strings. For a statically linked application this may
293 be undesirable if small executable size is an objective.
296 Don't automatically load the default openssl.cnf file.
297 Typically OpenSSL will automatically load a system config
298 file which configures default ssl options.
301 While testing, generate C++ buildtest files that
302 simply check that the public OpenSSL header files
303 are usable standalone with C++.
305 Enabling this option demands extra care. For any
306 compiler flag given directly as configuration
307 option, you must ensure that it's valid for both
308 the C and the C++ compiler. If not, the C++ build
309 test will most likely break. As an alternative,
310 you can use the language specific variables, CFLAGS
314 Don't build the CAPI engine. This option will be forced if
315 on a platform that does not support CAPI.
318 Don't build support for CMP features
321 Don't build support for CMS features
324 Don't build support for SSL/TLS compression. If this option
325 is left enabled (the default), then compression will only
326 work if the zlib or zlib-dynamic options are also chosen.
329 Build support for debugging memory allocated via
330 OPENSSL_malloc() or OPENSSL_zalloc().
332 enable-crypto-mdebug-backtrace
333 As for crypto-mdebug, but additionally provide backtrace
334 information for allocated memory.
335 TO BE USED WITH CARE: this uses GNU C functionality, and
336 is therefore not usable for non-GNU config targets. If
337 your build complains about the use of '-rdynamic' or the
338 lack of header file execinfo.h, this option is not for you.
339 ALSO NOTE that even though execinfo.h is available on your
340 system (through Gnulib), the functions might just be stubs
344 Don't build support for Certificate Transparency.
347 Don't build with support for any deprecated APIs. This is the
348 same as using "--api" and supplying the latest version
352 Don't build support for datagram based BIOs. Selecting this
353 option will also force the disabling of DTLS.
356 Build the /dev/crypto engine. It is automatically selected
357 on BSD implementations, in which case it can be disabled with
361 Don't build the dynamically loaded engines. This only has an
362 effect in a "shared" build
365 Don't build support for Elliptic Curves.
368 Don't build support for binary Elliptic Curves
370 enable-ec_nistp_64_gcc_128
371 Enable support for optimised implementations of some commonly
372 used NIST elliptic curves.
373 This is only supported on platforms:
374 - with little-endian storage of non-byte types
375 - that tolerate misaligned memory references
376 - where the compiler:
377 - supports the non-standard type __uint128_t
378 - defines the built-in macro __SIZEOF_INT128__
381 Build support for gathering entropy from EGD (Entropy
385 Don't build support for loading engines.
388 Don't compile in any error strings.
390 enable-external-tests
391 Enable building of integration with external test suites.
392 This is a developer option and may not work on all platforms.
393 The only supported external test suite at the current time is
394 the BoringSSL test suite. See the file test/README.external
398 Don't compile in filename and line number information (e.g.
399 for errors and memory allocation).
402 Don't compile the FIPS module
404 enable-fuzz-libfuzzer, enable-fuzz-afl
405 Build with support for fuzzing using either libfuzzer or AFL.
406 These are developer options only. They may not work on all
407 platforms and should never be used in production environments.
408 See the file fuzz/README.md for further details.
411 Don't build support for GOST based ciphersuites. Note that
412 if this feature is enabled then GOST ciphersuites are only
413 available if the GOST algorithms are also available through
414 loading an externally supplied engine.
417 Don't build the legacy provider. Disabling this also disables
418 the legacy algorithms: MD2 (already disabled by default).
421 Don't generate dependencies.
424 Don't build any dynamically loadable engines. This also
425 implies 'no-dynamic-engine'.
428 Don't build support for writing multiple records in one
429 go in libssl (Note: this is a different capability to the
430 pipelining functionality).
433 Don't build support for the NPN TLS extension.
436 Don't build support for OCSP.
440 Don't build the padlock engine.
441 ('no-hw-padlock' is deprecated and should not be used)
444 Don't build with support for Position Independent Code.
446 no-pinshared By default OpenSSL will attempt to stay in memory until the
447 process exits. This is so that libcrypto and libssl can be
448 properly cleaned up automatically via an "atexit()" handler.
449 The handler is registered by libcrypto and cleans up both
450 libraries. On some platforms the atexit() handler will run on
451 unload of libcrypto (if it has been dynamically loaded)
452 rather than at process exit. This option can be used to stop
453 OpenSSL from attempting to stay in memory until the process
454 exits. This could lead to crashes if either libcrypto or
455 libssl have already been unloaded at the point
456 that the atexit handler is invoked, e.g. on a platform which
457 calls atexit() on unload of the library, and libssl is
458 unloaded before libcrypto then a crash is likely to happen.
459 Applications can suppress running of the atexit() handler at
460 run time by using the OPENSSL_INIT_NO_ATEXIT option to
461 OPENSSL_init_crypto(). See the man page for it for further
465 Don't use POSIX IO capabilities.
468 Don't build support for Pre-Shared Key based ciphersuites.
471 Don't use hardware RDRAND capabilities.
474 Don't build support for RFC3779 ("X.509 Extensions for IP
475 Addresses and AS Identifiers")
478 Build support for SCTP
481 Do not create shared libraries, only static ones. See "Note
482 on shared libraries" below.
485 Don't build support for socket BIOs
488 Don't build support for SRP or SRP based ciphersuites.
491 Don't build SRTP support
494 Exclude SSE2 code paths from 32-bit x86 assembly modules.
495 Normally SSE2 extension is detected at run-time, but the
496 decision whether or not the machine code will be executed
497 is taken solely on CPU capability vector. This means that
498 if you happen to run OS kernel which does not support SSE2
499 extension on Intel P4 processor, then your application
500 might be exposed to "illegal instruction" exception.
501 There might be a way to enable support in kernel, e.g.
502 FreeBSD kernel can be compiled with CPU_ENABLE_SSE, and
503 there is a way to disengage SSE2 code paths upon application
504 start-up, but if you aim for wider "audience" running
505 such kernel, consider no-sse2. Both the 386 and
506 no-asm options imply no-sse2.
509 Build with the SSL Trace capabilities (adds the "-trace"
510 option to s_client and s_server).
513 Don't build the statically linked engines. This only
514 has an impact when not built "shared".
517 Don't use anything from the C header file "stdio.h" that
518 makes use of the "FILE" type. Only libcrypto and libssl can
519 be built in this way. Using this option will suppress
520 building the command line applications. Additionally since
521 the OpenSSL tests also use the command line applications the
522 tests will also be skipped.
525 Don't build test programs or run any test.
528 Don't try to build with support for multi-threaded
532 Build with support for multi-threaded applications. Most
533 platforms will enable this by default. However if on a
534 platform where this is not the case then this will usually
535 require additional system-dependent options! See "Note on
536 multi-threading" below.
539 Build with support for the integrated tracing api. See manual pages
540 OSSL_trace_set_channel(3) and OSSL_trace_enabled(3) for details.
543 Don't build Time Stamping Authority support.
546 Build with the Undefined Behaviour sanitiser. This is a
547 developer option only. It may not work on all platforms and
548 should never be used in production environments. It will only
549 work when used with gcc or clang and should be used in
550 conjunction with the "-DPEDANTIC" option (or the
551 --strict-warnings option).
554 Don't build with the "UI" capability (i.e. the set of
555 features enabling text based prompts).
558 Enable additional unit test APIs. This should not typically
559 be used in production deployments.
561 enable-weak-ssl-ciphers
562 Build support for SSL/TLS ciphers that are considered "weak"
563 (e.g. RC4 based ciphersuites).
566 Build with support for zlib compression/decompression.
569 Like "zlib", but has OpenSSL load the zlib library
570 dynamically when needed. This is only supported on systems
571 where loading of shared libraries is supported.
574 In 32-bit x86 builds, when generating assembly modules,
575 use the 80386 instruction set only (the default x86 code
576 is more efficient, but requires at least a 486). Note:
577 This doesn't affect code generated by compiler, you're
578 likely to complement configuration command line with
579 suitable compiler-specific option.
582 Don't build support for negotiating the specified SSL/TLS
583 protocol (one of ssl, ssl3, tls, tls1, tls1_1, tls1_2,
584 tls1_3, dtls, dtls1 or dtls1_2). If "no-tls" is selected then
585 all of tls1, tls1_1, tls1_2 and tls1_3 are disabled.
586 Similarly "no-dtls" will disable dtls1 and dtls1_2. The
587 "no-ssl" option is synonymous with "no-ssl3". Note this only
588 affects version negotiation. OpenSSL will still provide the
589 methods for applications to explicitly select the individual
593 As for no-<prot> but in addition do not build the methods for
594 applications to explicitly select individual protocol
595 versions. Note that there is no "no-tls1_3-method" option
596 because there is no application method for TLSv1.3. Using
597 individual protocol methods directly is deprecated.
598 Applications should use TLS_method() instead.
601 Build with support for the specified algorithm, where <alg>
602 is one of: md2 or rc5.
605 Build without support for the specified algorithm, where
606 <alg> is one of: aria, bf, blake2, camellia, cast, chacha,
607 cmac, des, dh, dsa, ecdh, ecdsa, idea, md4, mdc2, ocb,
608 poly1305, rc2, rc4, rmd160, scrypt, seed, siphash, siv, sm2,
609 sm3, sm4 or whirlpool. The "ripemd" algorithm is deprecated
610 and if used is synonymous with rmd160.
612 -Dxxx, -Ixxx, -Wp, -lxxx, -Lxxx, -Wl, -rpath, -R, -framework, -static
613 These system specific options will be recognised and
614 passed through to the compiler to allow you to define
615 preprocessor symbols, specify additional libraries, library
616 directories or other compiler options. It might be worth
617 noting that some compilers generate code specifically for
618 processor the compiler currently executes on. This is not
619 necessarily what you might have in mind, since it might be
620 unsuitable for execution on other, typically older,
621 processor. Consult your compiler documentation.
623 Take note of the VAR=value documentation below and how
624 these flags interact with those variables.
627 Additional options that are not otherwise recognised are
628 passed through as they are to the compiler as well. Again,
629 consult your compiler documentation.
631 Take note of the VAR=value documentation below and how
632 these flags interact with those variables.
635 Assignment of environment variable for Configure. These
636 work just like normal environment variable assignments,
637 but are supported on all platforms and are confined to
638 the configuration scripts only. These assignments override
639 the corresponding value in the inherited environment, if
642 The following variables are used as "make variables" and
643 can be used as an alternative to giving preprocessor,
644 compiler and linker options directly as configuration.
645 The following variables are supported:
647 AR The static library archiver.
648 ARFLAGS Flags for the static library archiver.
649 AS The assembler compiler.
650 ASFLAGS Flags for the assembler compiler.
652 CFLAGS Flags for the C compiler.
653 CXX The C++ compiler.
654 CXXFLAGS Flags for the C++ compiler.
655 CPP The C/C++ preprocessor.
656 CPPFLAGS Flags for the C/C++ preprocessor.
657 CPPDEFINES List of CPP macro definitions, separated
658 by a platform specific character (':' or
659 space for Unix, ';' for Windows, ',' for
660 VMS). This can be used instead of using
661 -D (or what corresponds to that on your
662 compiler) in CPPFLAGS.
663 CPPINCLUDES List of CPP inclusion directories, separated
664 the same way as for CPPDEFINES. This can
665 be used instead of -I (or what corresponds
666 to that on your compiler) in CPPFLAGS.
667 HASHBANGPERL Perl invocation to be inserted after '#!'
668 in public perl scripts (only relevant on
670 LD The program linker (not used on Unix, $(CC)
672 LDFLAGS Flags for the shared library, DSO and
674 LDLIBS Extra libraries to use when linking.
675 Takes the form of a space separated list
676 of library specifications on Unix and
677 Windows, and as a comma separated list of
679 RANLIB The library archive indexer.
680 RC The Windows resource compiler.
681 RCFLAGS Flags for the Windows resource compiler.
682 RM The command to remove files and directories.
684 These cannot be mixed with compiling / linking flags given
685 on the command line. In other words, something like this
688 ./config -DFOO CPPFLAGS=-DBAR -DCOOKIE
690 Backward compatibility note:
692 To be compatible with older configuration scripts, the
693 environment variables are ignored if compiling / linking
694 flags are given on the command line, except for these:
696 AR, CC, CXX, CROSS_COMPILE, HASHBANGPERL, PERL, RANLIB, RC
699 For example, the following command will not see -DBAR:
701 CPPFLAGS=-DBAR ./config -DCOOKIE
703 However, the following will see both set variables:
705 CC=gcc CROSS_COMPILE=x86_64-w64-mingw32- \
708 If CC is set, it is advisable to also set CXX to ensure
709 both C and C++ compilers are in the same "family". This
710 becomes relevant with 'enable-external-tests' and
711 'enable-buildtest-c++'.
715 Reconfigure from earlier data. This fetches the previous
716 command line options and environment from data saved in
717 "configdata.pm", and runs the configuration process again,
718 using these options and environment.
719 Note: NO other option is permitted together with "reconf".
720 This means that you also MUST use "./Configure" (or
721 what corresponds to that on non-Unix platforms) directly
722 to invoke this option.
723 Note: The original configuration saves away values for ALL
724 environment variables that were used, and if they weren't
725 defined, they are still saved away with information that
726 they weren't originally defined. This information takes
727 precedence over environment variables that are defined
730 Displaying configuration data
731 -----------------------------
733 The configuration script itself will say very little, and finishes by
734 creating "configdata.pm". This perl module can be loaded by other scripts
735 to find all the configuration data, and it can also be used as a script to
736 display all sorts of configuration data in a human readable form.
738 For more information, please do:
740 $ ./configdata.pm --help # Unix
744 $ perl configdata.pm --help # Windows and VMS
746 Installation in Detail
747 ----------------------
749 1a. Configure OpenSSL for your operation system automatically:
751 NOTE: This is not available on Windows.
753 $ ./config [[ options ]] # Unix
757 $ @config [[ options ]] ! OpenVMS
759 For the remainder of this text, the Unix form will be used in all
760 examples, please use the appropriate form for your platform.
762 This guesses at your operating system (and compiler, if necessary) and
763 configures OpenSSL based on this guess. Run ./config -t to see
764 if it guessed correctly. If you want to use a different compiler, you
765 are cross-compiling for another platform, or the ./config guess was
766 wrong for other reasons, go to step 1b. Otherwise go to step 2.
768 On some systems, you can include debugging information as follows:
770 $ ./config -d [[ options ]]
772 1b. Configure OpenSSL for your operating system manually
774 OpenSSL knows about a range of different operating system, hardware and
775 compiler combinations. To see the ones it knows about, run
781 $ perl Configure # All other platforms
783 For the remainder of this text, the Unix form will be used in all
784 examples, please use the appropriate form for your platform.
786 Pick a suitable name from the list that matches your system. For most
787 operating systems there is a choice between using "cc" or "gcc". When
788 you have identified your system (and if necessary compiler) use this name
789 as the argument to Configure. For example, a "linux-elf" user would
792 $ ./Configure linux-elf [[ options ]]
794 If your system isn't listed, you will have to create a configuration
795 file named Configurations/{{ something }}.conf and add the correct
796 configuration for your system. See the available configs as examples
797 and read Configurations/README and Configurations/README.design for
800 The generic configurations "cc" or "gcc" should usually work on 32 bit
803 Configure creates a build file ("Makefile" on Unix, "makefile" on Windows
804 and "descrip.mms" on OpenVMS) from a suitable template in Configurations,
805 and defines various macros in include/openssl/opensslconf.h (generated from
806 include/openssl/opensslconf.h.in).
808 1c. Configure OpenSSL for building outside of the source tree.
810 OpenSSL can be configured to build in a build directory separate from
811 the directory with the source code. It's done by placing yourself in
812 some other directory and invoking the configuration commands from
817 $ mkdir /var/tmp/openssl-build
818 $ cd /var/tmp/openssl-build
819 $ /PATH/TO/OPENSSL/SOURCE/config [[ options ]]
823 $ /PATH/TO/OPENSSL/SOURCE/Configure {{ target }} [[ options ]]
827 $ set default sys$login:
828 $ create/dir [.tmp.openssl-build]
829 $ set default [.tmp.openssl-build]
830 $ @[PATH.TO.OPENSSL.SOURCE]config [[ options ]]
834 $ @[PATH.TO.OPENSSL.SOURCE]Configure {{ target }} [[ options ]]
839 $ mkdir \temp-openssl
841 $ perl d:\PATH\TO\OPENSSL\SOURCE\Configure {{ target }} [[ options ]]
843 Paths can be relative just as well as absolute. Configure will
844 do its best to translate them to relative paths whenever possible.
846 2. Build OpenSSL by running:
849 $ mms ! (or mmk) OpenVMS
852 This will build the OpenSSL libraries (libcrypto.a and libssl.a on
853 Unix, corresponding on other platforms) and the OpenSSL binary
854 ("openssl"). The libraries will be built in the top-level directory,
855 and the binary will be in the "apps" subdirectory.
859 If the build fails, look at the output. There may be reasons
860 for the failure that aren't problems in OpenSSL itself (like
861 missing standard headers).
863 If the build succeeded previously, but fails after a source or
864 configuration change, it might be helpful to clean the build tree
865 before attempting another build. Use this command:
868 $ mms clean ! (or mmk) OpenVMS
869 $ nmake clean # Windows
871 Assembler error messages can sometimes be sidestepped by using the
872 "no-asm" configuration option.
874 Compiling parts of OpenSSL with gcc and others with the system
875 compiler will result in unresolved symbols on some systems.
877 If you are still having problems you can get help by sending an email
878 to the openssl-users email list (see
879 https://www.openssl.org/community/mailinglists.html for details). If
880 it is a bug with OpenSSL itself, please open an issue on GitHub, at
881 https://github.com/openssl/openssl/issues. Please review the existing
882 ones first; maybe the bug was already reported or has already been
885 3. After a successful build, the libraries should be tested. Run:
889 $ nmake test # Windows
891 NOTE: you MUST run the tests from an unprivileged account (or
892 disable your privileges temporarily if your platform allows it).
894 If some tests fail, look at the output. There may be reasons for
895 the failure that isn't a problem in OpenSSL itself (like a
896 malfunction with Perl). You may want increased verbosity, that
897 can be accomplished like this:
899 $ make VERBOSE=1 test # Unix
901 $ mms /macro=(VERBOSE=1) test ! OpenVMS
903 $ nmake VERBOSE=1 test # Windows
905 If you want to run just one or a few specific tests, you can use
906 the make variable TESTS to specify them, like this:
908 $ make TESTS='test_rsa test_dsa' test # Unix
909 $ mms/macro="TESTS=test_rsa test_dsa" test ! OpenVMS
910 $ nmake TESTS='test_rsa test_dsa' test # Windows
912 And of course, you can combine (Unix example shown):
914 $ make VERBOSE=1 TESTS='test_rsa test_dsa' test
916 You can find the list of available tests like this:
918 $ make list-tests # Unix
919 $ mms list-tests ! OpenVMS
920 $ nmake list-tests # Windows
922 Have a look at the manual for the perl module Test::Harness to
923 see what other HARNESS_* variables there are.
925 If you find a problem with OpenSSL itself, try removing any
926 compiler optimization flags from the CFLAGS line in Makefile and
927 run "make clean; make" or corresponding.
929 To report a bug please open an issue on GitHub, at
930 https://github.com/openssl/openssl/issues.
932 For more details on how the make variables TESTS can be used,
933 see section TESTS in Detail below.
935 4. If everything tests ok, install OpenSSL with
937 $ make install # Unix
938 $ mms install ! OpenVMS
939 $ nmake install # Windows
941 This will install all the software components in this directory
942 tree under PREFIX (the directory given with --prefix or its
947 bin/ Contains the openssl binary and a few other
950 Contains the header files needed if you want
951 to build your own programs that use libcrypto
953 lib Contains the OpenSSL library files.
954 lib/engines Contains the OpenSSL dynamically loadable engines.
956 share/man/man1 Contains the OpenSSL command line man-pages.
957 share/man/man3 Contains the OpenSSL library calls man-pages.
958 share/man/man5 Contains the OpenSSL configuration format man-pages.
959 share/man/man7 Contains the OpenSSL other misc man-pages.
961 share/doc/openssl/html/man1
962 share/doc/openssl/html/man3
963 share/doc/openssl/html/man5
964 share/doc/openssl/html/man7
965 Contains the HTML rendition of the man-pages.
967 OpenVMS ('arch' is replaced with the architecture name, "Alpha"
968 or "ia64", 'sover' is replaced with the shared library version
969 (0101 for 1.1), and 'pz' is replaced with the pointer size
970 OpenSSL was built with):
972 [.EXE.'arch'] Contains the openssl binary.
973 [.EXE] Contains a few utility scripts.
975 Contains the header files needed if you want
976 to build your own programs that use libcrypto
978 [.LIB.'arch'] Contains the OpenSSL library files.
979 [.ENGINES'sover''pz'.'arch']
980 Contains the OpenSSL dynamically loadable engines.
981 [.SYS$STARTUP] Contains startup, login and shutdown scripts.
982 These define appropriate logical names and
984 [.SYSTEST] Contains the installation verification procedure.
985 [.HTML] Contains the HTML rendition of the manual pages.
988 Additionally, install will add the following directories under
989 OPENSSLDIR (the directory given with --openssldir or its default)
992 certs Initially empty, this is the default location
993 for certificate files.
994 private Initially empty, this is the default location
995 for private key files.
996 misc Various scripts.
998 Package builders who want to configure the library for standard
999 locations, but have the package installed somewhere else so that
1000 it can easily be packaged, can use
1002 $ make DESTDIR=/tmp/package-root install # Unix
1003 $ mms/macro="DESTDIR=TMP:[PACKAGE-ROOT]" install ! OpenVMS
1005 The specified destination directory will be prepended to all
1006 installation target paths.
1008 Compatibility issues with previous OpenSSL versions:
1010 * COMPILING existing applications
1012 Starting with version 1.1.0, OpenSSL hides a number of structures
1013 that were previously open. This includes all internal libssl
1014 structures and a number of EVP types. Accessor functions have
1015 been added to allow controlled access to the structures' data.
1017 This means that some software needs to be rewritten to adapt to
1018 the new ways of doing things. This often amounts to allocating
1019 an instance of a structure explicitly where you could previously
1020 allocate them on the stack as automatic variables, and using the
1021 provided accessor functions where you would previously access a
1022 structure's field directly.
1024 Some APIs have changed as well. However, older APIs have been
1025 preserved when possible.
1027 Environment Variables
1028 ---------------------
1030 A number of environment variables can be used to provide additional control
1031 over the build process. Typically these should be defined prior to running
1032 config or Configure. Not all environment variables are relevant to all
1036 The name of the ar executable to use.
1039 Use a different build file name than the platform default
1040 ("Makefile" on Unix-like platforms, "makefile" on native Windows,
1041 "descrip.mms" on OpenVMS). This requires that there is a
1042 corresponding build file template. See Configurations/README
1043 for further information.
1046 The compiler to use. Configure will attempt to pick a default
1047 compiler for your platform but this choice can be overridden
1048 using this variable. Set it to the compiler executable you wish
1049 to use, e.g. "gcc" or "clang".
1052 This environment variable has the same meaning as for the
1053 "--cross-compile-prefix" Configure flag described above. If both
1054 are set then the Configure flag takes precedence.
1057 The name of the nm executable to use.
1059 OPENSSL_LOCAL_CONFIG_DIR
1060 OpenSSL comes with a database of information about how it
1061 should be built on different platforms as well as build file
1062 templates for those platforms. The database is comprised of
1063 ".conf" files in the Configurations directory. The build
1064 file templates reside there as well as ".tmpl" files. See the
1065 file Configurations/README for further information about the
1066 format of ".conf" files as well as information on the ".tmpl"
1068 In addition to the standard ".conf" and ".tmpl" files, it is
1069 possible to create your own ".conf" and ".tmpl" files and store
1070 them locally, outside the OpenSSL source tree. This environment
1071 variable can be set to the directory where these files are held
1072 and will be considered by Configure before it looks in the
1073 standard directories.
1076 The name of the Perl executable to use when building OpenSSL.
1077 This variable is used in config script only. Configure on the
1078 other hand imposes the interpreter by which it itself was
1079 executed on the whole build procedure.
1082 The command string for the Perl executable to insert in the
1083 #! line of perl scripts that will be publically installed.
1084 Default: /usr/bin/env perl
1085 Note: the value of this variable is added to the same scripts
1086 on all platforms, but it's only relevant on Unix-like platforms.
1089 The name of the rc executable to use. The default will be as
1090 defined for the target platform in the ".conf" file. If not
1091 defined then "windres" will be used. The WINDRES environment
1092 variable is synonymous to this. If both are defined then RC
1096 The name of the ranlib executable to use.
1104 The Configure script generates a Makefile in a format relevant to the specific
1105 platform. The Makefiles provide a number of targets that can be used. Not all
1106 targets may be available on all platforms. Only the most common targets are
1107 described here. Examine the Makefiles themselves for the full list.
1110 The default target to build all the software components.
1113 Remove all build artefacts and return the directory to a "clean"
1117 Rebuild the dependencies in the Makefiles. This is a legacy
1118 option that no longer needs to be used since OpenSSL 1.1.0.
1121 Install all OpenSSL components.
1124 Only install the OpenSSL software components.
1127 Only install the OpenSSL documentation components.
1130 Only install the OpenSSL man pages (Unix only).
1133 Only install the OpenSSL html documentation.
1136 Prints a list of all the self test names.
1139 Build and run the OpenSSL self tests.
1142 Uninstall all OpenSSL components.
1146 Re-run the configuration process, as exactly as the last time
1150 This is a developer option. If you are developing a patch for
1151 OpenSSL you may need to use this if you want to update
1152 automatically generated files; add new error codes or add new
1153 (or change the visibility of) public API functions. (Unix only).
1158 The make variable TESTS supports a versatile set of space separated tokens
1159 with which you can specify a set of tests to be performed. With a "current
1160 set of tests" in mind, initially being empty, here are the possible tokens:
1162 alltests The current set of tests becomes the whole set of available
1163 tests (as listed when you do 'make list-tests' or similar).
1164 xxx Adds the test 'xxx' to the current set of tests.
1165 -xxx Removes 'xxx' from the current set of tests. If this is the
1166 first token in the list, the current set of tests is first
1167 assigned the whole set of available tests, effectively making
1168 this token equivalent to TESTS="alltests -xxx".
1169 nn Adds the test group 'nn' (which is a number) to the current
1171 -nn Removes the test group 'nn' from the current set of tests.
1172 If this is the first token in the list, the current set of
1173 tests is first assigned the whole set of available tests,
1174 effectively making this token equivalent to
1175 TESTS="alltests -xxx".
1177 Also, all tokens except for "alltests" may have wildcards, such as *.
1178 (on Unix and Windows, BSD style wildcards are supported, while on VMS,
1179 it's VMS style wildcards)
1181 Example: All tests except for the fuzz tests:
1183 $ make TESTS=-test_fuzz test
1185 or (if you want to be explicit)
1187 $ make TESTS='alltests -test_fuzz' test
1189 Example: All tests that have a name starting with "test_ssl" but not those
1190 starting with "test_ssl_":
1192 $ make TESTS='test_ssl* -test_ssl_*' test
1194 Example: Only test group 10:
1198 Example: All tests except the slow group (group 99):
1202 Example: All tests in test groups 80 to 99 except for tests in group 90:
1204 $ make TESTS='[89]? -90'
1206 To stochastically verify that the algorithm that produces uniformly distributed
1207 random numbers is operating correctly (with a false positive rate of 0.01%):
1209 $ ./util/shlib_wrap.sh test/bntest -stochastic
1211 Note on multi-threading
1212 -----------------------
1214 For some systems, the OpenSSL Configure script knows what compiler options
1215 are needed to generate a library that is suitable for multi-threaded
1216 applications. On these systems, support for multi-threading is enabled
1217 by default; use the "no-threads" option to disable (this should never be
1220 On other systems, to enable support for multi-threading, you will have
1221 to specify at least two options: "threads", and a system-dependent option.
1222 (The latter is "-D_REENTRANT" on various systems.) The default in this
1223 case, obviously, is not to include support for multi-threading (but
1224 you can still use "no-threads" to suppress an annoying warning message
1225 from the Configure script.)
1227 OpenSSL provides built-in support for two threading models: pthreads (found on
1228 most UNIX/Linux systems), and Windows threads. No other threading models are
1229 supported. If your platform does not provide pthreads or Windows threads then
1230 you should Configure with the "no-threads" option.
1232 Notes on shared libraries
1233 -------------------------
1235 For most systems the OpenSSL Configure script knows what is needed to
1236 build shared libraries for libcrypto and libssl. On these systems
1237 the shared libraries will be created by default. This can be suppressed and
1238 only static libraries created by using the "no-shared" option. On systems
1239 where OpenSSL does not know how to build shared libraries the "no-shared"
1240 option will be forced and only static libraries will be created.
1242 Shared libraries are named a little differently on different platforms.
1243 One way or another, they all have the major OpenSSL version number as
1244 part of the file name, i.e. for OpenSSL 1.1.x, 1.1 is somehow part of
1247 On most POSIX platforms, shared libraries are named libcrypto.so.1.1
1250 on Cygwin, shared libraries are named cygcrypto-1.1.dll and cygssl-1.1.dll
1251 with import libraries libcrypto.dll.a and libssl.dll.a.
1253 On Windows build with MSVC or using MingW, shared libraries are named
1254 libcrypto-1_1.dll and libssl-1_1.dll for 32-bit Windows, libcrypto-1_1-x64.dll
1255 and libssl-1_1-x64.dll for 64-bit x86_64 Windows, and libcrypto-1_1-ia64.dll
1256 and libssl-1_1-ia64.dll for IA64 Windows. With MSVC, the import libraries
1257 are named libcrypto.lib and libssl.lib, while with MingW, they are named
1258 libcrypto.dll.a and libssl.dll.a.
1260 On VMS, shareable images (VMS speak for shared libraries) are named
1261 ossl$libcrypto0101_shr.exe and ossl$libssl0101_shr.exe. However, when
1262 OpenSSL is specifically built for 32-bit pointers, the shareable images
1263 are named ossl$libcrypto0101_shr32.exe and ossl$libssl0101_shr32.exe
1264 instead, and when built for 64-bit pointers, they are named
1265 ossl$libcrypto0101_shr64.exe and ossl$libssl0101_shr64.exe.
1267 Note on random number generation
1268 --------------------------------
1270 Availability of cryptographically secure random numbers is required for
1271 secret key generation. OpenSSL provides several options to seed the
1272 internal CSPRNG. If not properly seeded, the internal CSPRNG will refuse
1273 to deliver random bytes and a "PRNG not seeded error" will occur.
1275 The seeding method can be configured using the --with-rand-seed option,
1276 which can be used to specify a comma separated list of seed methods.
1277 However in most cases OpenSSL will choose a suitable default method,
1278 so it is not necessary to explicitly provide this option. Note also
1279 that not all methods are available on all platforms.
1281 I) On operating systems which provide a suitable randomness source (in
1282 form of a system call or system device), OpenSSL will use the optimal
1283 available method to seed the CSPRNG from the operating system's
1284 randomness sources. This corresponds to the option --with-rand-seed=os.
1286 II) On systems without such a suitable randomness source, automatic seeding
1287 and reseeding is disabled (--with-rand-seed=none) and it may be necessary
1288 to install additional support software to obtain a random seed and reseed
1289 the CSPRNG manually. Please check out the manual pages for RAND_add(),
1290 RAND_bytes(), RAND_egd(), and the FAQ for more information.
projects / openssl.git / blob