Name Date Size #Lines LOC

..03-Nov-2024-

.ctags.d/H19-Jun-2024-

.github/H23-Oct-2024-

Configurations/H18-Dec-2024-

VMS/H19-Jun-2024-

apps/H11-Dec-2024-

cloudflare-quiche/H19-Jun-2024-

crypto/H20-Dec-2024-

demos/H19-Jun-2024-

dev/H19-Jun-2024-

doc/H19-Nov-2024-

engines/H10-Oct-2024-

exporters/H25-Jun-2024-

external/perl/H24-Feb-2020-

fuzz/H05-Sep-2024-

gost-engine/H23-May-2020-

include/H24-Feb-2020-

krb5/H24-Feb-2020-

ms/H19-Jun-2024-

oqs-provider/H09-Mar-2022-

os-dep/H19-Jun-2024-

pkcs11-provider/H21-Oct-2024-

providers/H21-Oct-2024-

pyca-cryptography/H24-Feb-2020-

python-ecdsa/H05-Jan-2022-

ssl/H10-Dec-2024-

test/H20-Dec-2024-

tlsfuzzer/H05-Jan-2022-

tlslite-ng/H05-Jan-2022-

tools/H19-Jun-2024-

util/H18-Dec-2024-

wycheproof/H23-May-2021-

.git-blame-ignore-revsH A D19-Jun-202482 32

.gitattributesH A D19-Jun-2024693 1816

.gitignoreH A D22-Nov-20245.7 KiB307281

.gitmodulesH A D21-Oct-20241.1 KiB3835

ACKNOWLEDGEMENTS.mdH A D19-Jun-2024159 74

AUTHORS.mdH A D02-Feb-2021990 5246

CHANGES.mdH A D17-Dec-2024776.7 KiB21,15814,695

CODE-OF-CONDUCT.mdH A D18-Aug-2022169 74

CONTRIBUTING.mdH A D07-Aug-20244.5 KiB10579

ConfigureH A D21-Oct-2024138.3 KiB3,7502,782

HACKING.mdH A D19-Jun-20241.2 KiB3425

INSTALL.mdH A D21-Oct-202468.7 KiB2,0451,397

LICENSE.txtH A D05-Jul-20209.9 KiB178150

NEWS.mdH A D04-Nov-202487.9 KiB2,0321,585

NOTES-ANDROID.mdH A D19-Jun-20244.5 KiB9172

NOTES-ANSI.mdH A D19-Jun-2024835 3421

NOTES-DJGPP.mdH A D12-Feb-20212.1 KiB4736

NOTES-NONSTOP.mdH A D17-Sep-202410.2 KiB255189

NOTES-PERL.mdH A D19-Jun-20244.9 KiB12895

NOTES-POSIX.mdH A D19-Jun-2024748 2115

NOTES-UNIX.mdH A D19-Jun-20245.6 KiB11693

NOTES-VALGRIND.mdH A D19-Jun-20242.8 KiB7352

NOTES-VMS.mdH A D19-Jun-20244.7 KiB13393

NOTES-WINDOWS.mdH A D09-Jul-202410.4 KiB284199

README-ENGINES.mdH A D19-Jun-202415.3 KiB318264

README-FIPS.mdH A D09-Oct-20248.1 KiB199148

README-PROVIDERS.mdH A D19-Jun-20245.4 KiB146111

README-QUIC.mdH A D19-Jun-20243.7 KiB8161

README.mdH A D10-Dec-20248.1 KiB263190

SUPPORT.mdH A D08-Dec-20213.8 KiB9469

VERSION.datH A D12-Sep-202492 87

build.infoH A D27-Aug-20245.7 KiB140126

configH A D28-Jun-2020378 112

config.comH A D16-Jul-20202.5 KiB9490

configdata.pm.inH A D29-Nov-202416.4 KiB488375

README-ENGINES.md

1Engines
2=======
3
4Deprecation Note
5----------------
6
7The ENGINE API was introduced in OpenSSL version 0.9.6 as a low level
8interface for adding alternative implementations of cryptographic
9primitives, most notably for integrating hardware crypto devices.
10
11The ENGINE interface has its limitations and it has been superseded
12by the [PROVIDER API](README-PROVIDERS.md), it is deprecated in OpenSSL
13version 3.0. The following documentation is retained as an aid for
14users who need to maintain or support existing ENGINE implementations.
15Support for new hardware devices or new algorithms should be added
16via providers, and existing engines should be converted to providers
17as soon as possible.
18
19Built-in ENGINE implementations
20-------------------------------
21
22There are currently built-in ENGINE implementations for the following
23crypto devices:
24
25- Microsoft CryptoAPI
26- VIA Padlock
27- nCipher CHIL
28
29In addition, dynamic binding to external ENGINE implementations is now
30provided by a special ENGINE called "dynamic". See the "DYNAMIC ENGINE"
31section below for details.
32
33At this stage, a number of things are still needed and are being worked on:
34
351. Integration of EVP support.
362. Configuration support.
373. Documentation!
38
39Integration of EVP support
40--------------------------
41
42With respect to EVP, this relates to support for ciphers and digests in
43the ENGINE model so that alternative implementations of existing
44algorithms/modes (or previously unimplemented ones) can be provided by
45ENGINE implementations.
46
47Configuration support
48---------------------
49
50Configuration support currently exists in the ENGINE API itself, in the
51form of "control commands". These allow an application to expose to the
52user/admin the set of commands and parameter types a given ENGINE
53implementation supports, and for an application to directly feed string
54based input to those ENGINEs, in the form of name-value pairs. This is an
55extensible way for ENGINEs to define their own "configuration" mechanisms
56that are specific to a given ENGINE (eg. for a particular hardware
57device) but that should be consistent across *all* OpenSSL-based
58applications when they use that ENGINE. Work is in progress (or at least
59in planning) for supporting these control commands from the CONF (or
60NCONF) code so that applications using OpenSSL's existing configuration
61file format can have ENGINE settings specified in much the same way.
62Presently however, applications must use the ENGINE API itself to provide
63such functionality. To see first hand the types of commands available
64with the various compiled-in ENGINEs (see further down for dynamic
65ENGINEs), use the "engine" openssl utility with full verbosity, i.e.:
66
67    openssl engine -vvvv
68
69Documentation
70-------------
71
72Documentation? Volunteers welcome! The source code is reasonably well
73self-documenting, but some summaries and usage instructions are needed -
74moreover, they are needed in the same POD format the existing OpenSSL
75documentation is provided in. Any complete or incomplete contributions
76would help make this happen.
77
78STABILITY & BUG-REPORTS
79=======================
80
81What already exists is fairly stable as far as it has been tested, but
82the test base has been a bit small most of the time. For the most part,
83the vendors of the devices these ENGINEs support have contributed to the
84development and/or testing of the implementations, and *usually* (with no
85guarantees) have experience in using the ENGINE support to drive their
86devices from common OpenSSL-based applications. Bugs and/or inexplicable
87behaviour in using a specific ENGINE implementation should be sent to the
88author of that implementation (if it is mentioned in the corresponding C
89file), and in the case of implementations for commercial hardware
90devices, also through whatever vendor support channels are available. If
91none of this is possible, or the problem seems to be something about the
92ENGINE API itself (ie. not necessarily specific to a particular ENGINE
93implementation) then you should mail complete details to the relevant
94OpenSSL mailing list. For a definition of "complete details", refer to
95the OpenSSL "README" file. As for which list to send it to:
96
97- openssl-users: if you are *using* the ENGINE abstraction, either in an
98  pre-compiled application or in your own application code.
99
100- openssl-dev: if you are discussing problems with OpenSSL source code.
101
102USAGE
103=====
104
105The default "openssl" ENGINE is always chosen when performing crypto
106operations unless you specify otherwise. You must actively tell the
107openssl utility commands to use anything else through a new command line
108switch called "-engine". Also, if you want to use the ENGINE support in
109your own code to do something similar, you must likewise explicitly
110select the ENGINE implementation you want.
111
112Depending on the type of hardware, system, and configuration, "settings"
113may need to be applied to an ENGINE for it to function as expected/hoped.
114The recommended way of doing this is for the application to support
115ENGINE "control commands" so that each ENGINE implementation can provide
116whatever configuration primitives it might require and the application
117can allow the user/admin (and thus the hardware vendor's support desk
118also) to provide any such input directly to the ENGINE implementation.
119This way, applications do not need to know anything specific to any
120device, they only need to provide the means to carry such user/admin
121input through to the ENGINE in question. Ie. this connects *you* (and
122your helpdesk) to the specific ENGINE implementation (and device), and
123allows application authors to not get buried in hassle supporting
124arbitrary devices they know (and care) nothing about.
125
126A new "openssl" utility, "openssl engine", has been added in that allows
127for testing and examination of ENGINE implementations. Basic usage
128instructions are available by specifying the "-?" command line switch.
129
130DYNAMIC ENGINES
131===============
132
133The new "dynamic" ENGINE provides a low-overhead way to support ENGINE
134implementations that aren't pre-compiled and linked into OpenSSL-based
135applications. This could be because existing compiled-in implementations
136have known problems and you wish to use a newer version with an existing
137application. It could equally be because the application (or OpenSSL
138library) you are using simply doesn't have support for the ENGINE you
139wish to use, and the ENGINE provider (eg. hardware vendor) is providing
140you with a self-contained implementation in the form of a shared-library.
141The other use-case for "dynamic" is with applications that wish to
142maintain the smallest foot-print possible and so do not link in various
143ENGINE implementations from OpenSSL, but instead leaves you to provide
144them, if you want them, in the form of "dynamic"-loadable
145shared-libraries. It should be possible for hardware vendors to provide
146their own shared-libraries to support arbitrary hardware to work with
147applications based on OpenSSL 0.9.7 or later. If you're using an
148application based on 0.9.7 (or later) and the support you desire is only
149announced for versions later than the one you need, ask the vendor to
150backport their ENGINE to the version you need.
151
152How does "dynamic" work?
153------------------------
154
155The dynamic ENGINE has a special flag in its implementation such that
156every time application code asks for the 'dynamic' ENGINE, it in fact
157gets its own copy of it. As such, multi-threaded code (or code that
158multiplexes multiple uses of 'dynamic' in a single application in any
159way at all) does not get confused by 'dynamic' being used to do many
160independent things. Other ENGINEs typically don't do this so there is
161only ever 1 ENGINE structure of its type (and reference counts are used
162to keep order). The dynamic ENGINE itself provides absolutely no
163cryptographic functionality, and any attempt to "initialise" the ENGINE
164automatically fails. All it does provide are a few "control commands"
165that can be used to control how it will load an external ENGINE
166implementation from a shared-library. To see these control commands,
167use the command-line;
168
169    openssl engine -vvvv dynamic
170
171The "SO_PATH" control command should be used to identify the
172shared-library that contains the ENGINE implementation, and "NO_VCHECK"
173might possibly be useful if there is a minor version conflict and you
174(or a vendor helpdesk) is convinced you can safely ignore it.
175"ID" is probably only needed if a shared-library implements
176multiple ENGINEs, but if you know the engine id you expect to be using,
177it doesn't hurt to specify it (and this provides a sanity check if
178nothing else). "LIST_ADD" is only required if you actually wish the
179loaded ENGINE to be discoverable by application code later on using the
180ENGINE's "id". For most applications, this isn't necessary - but some
181application authors may have nifty reasons for using it. The "LOAD"
182command is the only one that takes no parameters and is the command
183that uses the settings from any previous commands to actually *load*
184the shared-library ENGINE implementation. If this command succeeds, the
185(copy of the) 'dynamic' ENGINE will magically morph into the ENGINE
186that has been loaded from the shared-library. As such, any control
187commands supported by the loaded ENGINE could then be executed as per
188normal. For instance, if ENGINE "foo" is implemented in the shared-library
189"libfoo.so" and it supports some special control command "CMD_FOO", the
190following code would load and use it (NB: obviously this code has no
191error checking);
192
193    ENGINE *e = ENGINE_by_id("dynamic");
194    ENGINE_ctrl_cmd_string(e, "SO_PATH", "/lib/libfoo.so", 0);
195    ENGINE_ctrl_cmd_string(e, "ID", "foo", 0);
196    ENGINE_ctrl_cmd_string(e, "LOAD", NULL, 0);
197    ENGINE_ctrl_cmd_string(e, "CMD_FOO", "some input data", 0);
198
199For testing, the "openssl engine" utility can be useful for this sort
200of thing. For example the above code excerpt would achieve much the
201same result as;
202
203    openssl engine dynamic \
204              -pre SO_PATH:/lib/libfoo.so \
205              -pre ID:foo \
206              -pre LOAD \
207              -pre "CMD_FOO:some input data"
208
209Or to simply see the list of commands supported by the "foo" ENGINE;
210
211    openssl engine -vvvv dynamic \
212              -pre SO_PATH:/lib/libfoo.so \
213              -pre ID:foo \
214              -pre LOAD
215
216Applications that support the ENGINE API and more specifically, the
217"control commands" mechanism, will provide some way for you to pass
218such commands through to ENGINEs. As such, you would select "dynamic"
219as the ENGINE to use, and the parameters/commands you pass would
220control the *actual* ENGINE used. Each command is actually a name-value
221pair and the value can sometimes be omitted (eg. the "LOAD" command).
222Whilst the syntax demonstrated in "openssl engine" uses a colon to
223separate the command name from the value, applications may provide
224their own syntax for making that separation (eg. a win32 registry
225key-value pair may be used by some applications). The reason for the
226"-pre" syntax in the "openssl engine" utility is that some commands
227might be issued to an ENGINE *after* it has been initialised for use.
228Eg. if an ENGINE implementation requires a smart-card to be inserted
229during initialisation (or a PIN to be typed, or whatever), there may be
230a control command you can issue afterwards to "forget" the smart-card
231so that additional initialisation is no longer possible. In
232applications such as web-servers, where potentially volatile code may
233run on the same host system, this may provide some arguable security
234value. In such a case, the command would be passed to the ENGINE after
235it has been initialised for use, and so the "-post" switch would be
236used instead. Applications may provide a different syntax for
237supporting this distinction, and some may simply not provide it at all
238("-pre" is almost always what you're after, in reality).
239
240How do I build a "dynamic" ENGINE?
241----------------------------------
242
243This question is trickier - currently OpenSSL bundles various ENGINE
244implementations that are statically built in, and any application that
245calls the "ENGINE_load_builtin_engines()" function will automatically
246have all such ENGINEs available (and occupying memory). Applications
247that don't call that function have no ENGINEs available like that and
248would have to use "dynamic" to load any such ENGINE - but on the other
249hand such applications would only have the memory footprint of any
250ENGINEs explicitly loaded using user/admin provided control commands.
251The main advantage of not statically linking ENGINEs and only using
252"dynamic" for hardware support is that any installation using no
253"external" ENGINE suffers no unnecessary memory footprint from unused
254ENGINEs. Likewise, installations that do require an ENGINE incur the
255overheads from only *that* ENGINE once it has been loaded.
256
257Sounds good? Maybe, but currently building an ENGINE implementation as
258a shared-library that can be loaded by "dynamic" isn't automated in
259OpenSSL's build process. It can be done manually quite easily however.
260Such a shared-library can either be built with any OpenSSL code it
261needs statically linked in, or it can link dynamically against OpenSSL
262if OpenSSL itself is built as a shared library. The instructions are
263the same in each case, but in the former (statically linked any
264dependencies on OpenSSL) you must ensure OpenSSL is built with
265position-independent code ("PIC"). The default OpenSSL compilation may
266already specify the relevant flags to do this, but you should consult
267with your compiler documentation if you are in any doubt.
268
269This example will show building the "atalla" ENGINE in the
270crypto/engine/ directory as a shared-library for use via the "dynamic"
271ENGINE.
272
2731.  "cd" to the crypto/engine/ directory of a pre-compiled OpenSSL
274    source tree.
275
2762.  Recompile at least one source file so you can see all the compiler
277    flags (and syntax) being used to build normally. Eg;
278
279        touch hw_atalla.c ; make
280
281    will rebuild "hw_atalla.o" using all such flags.
282
2833.  Manually enter the same compilation line to compile the
284    "hw_atalla.c" file but with the following two changes;
285
286    - add "-DENGINE_DYNAMIC_SUPPORT" to the command line switches,
287    - change the output file from "hw_atalla.o" to something new,
288      eg. "tmp_atalla.o"
289
2904.  Link "tmp_atalla.o" into a shared-library using the top-level
291    OpenSSL libraries to resolve any dependencies. The syntax for doing
292    this depends heavily on your system/compiler and is a nightmare
293    known well to anyone who has worked with shared-library portability
294    before. 'gcc' on Linux, for example, would use the following syntax;
295
296        gcc -shared -o dyn_atalla.so tmp_atalla.o -L../.. -lcrypto
297
2985.  Test your shared library using "openssl engine" as explained in the
299    previous section. Eg. from the top-level directory, you might try
300
301        apps/openssl engine -vvvv dynamic \
302              -pre SO_PATH:./crypto/engine/dyn_atalla.so -pre LOAD
303
304If the shared-library loads successfully, you will see both "-pre"
305commands marked as "SUCCESS" and the list of control commands
306displayed (because of "-vvvv") will be the control commands for the
307*atalla* ENGINE (ie. *not* the 'dynamic' ENGINE). You can also add
308the "-t" switch to the utility if you want it to try and initialise
309the atalla ENGINE for use to test any possible hardware/driver issues.
310
311PROBLEMS
312========
313
314It seems like the ENGINE part doesn't work too well with CryptoSwift on Win32.
315A quick test done right before the release showed that trying "openssl speed
316-engine cswift" generated errors. If the DSO gets enabled, an attempt is made
317to write at memory address 0x00000002.
318

README-FIPS.md

1OpenSSL FIPS support
2====================
3
4This release of OpenSSL includes a cryptographic module that can be
5FIPS validated. The module is implemented as an OpenSSL provider.
6A provider is essentially a dynamically loadable module which implements
7cryptographic algorithms, see the [README-PROVIDERS](README-PROVIDERS.md) file
8for further details.
9
10A cryptographic module is only FIPS validated after it has gone through the complex
11FIPS 140 validation process. As this process takes a very long time, it is not
12possible to validate every minor release of OpenSSL.
13If you need a FIPS validated module then you must ONLY generate a FIPS provider
14using OpenSSL versions that have valid FIPS certificates. A FIPS certificate
15contains a link to a Security Policy, and you MUST follow the instructions
16in the Security Policy in order to be FIPS compliant.
17See <https://www.openssl.org/source/> for information related to OpenSSL
18FIPS certificates and Security Policies.
19
20Newer OpenSSL Releases that include security or bug fixes can be used to build
21all other components (such as the core API's, TLS and the default, base and
22legacy providers) without any restrictions, but the FIPS provider must be built
23as specified in the Security Policy (normally with a different version of the
24source code).
25
26The OpenSSL FIPS provider is a shared library called `fips.so` (on Unix), or
27resp. `fips.dll` (on Windows). The FIPS provider does not get built and
28installed automatically. To enable it, you need to configure OpenSSL using
29the `enable-fips` option.
30
31Installing the FIPS provider
32============================
33
34In order to be FIPS compliant you must only use FIPS validated source code.
35Refer to <https://www.openssl.org/source/> for information related to
36which versions are FIPS validated. The instructions given below build OpenSSL
37just using the FIPS validated source code.
38
39If you want to use a validated FIPS provider, but also want to use the latest
40OpenSSL release to build everything else, then refer to the next section.
41
42The following is only a guide.
43Please read the Security Policy for up to date installation instructions.
44
45If the FIPS provider is enabled, it gets installed automatically during the
46normal installation process. Simply follow the normal procedure (configure,
47make, make test, make install) as described in the [INSTALL](INSTALL.md) file.
48
49For example, on Unix the final command
50
51    $ make install
52
53effectively executes the following install targets
54
55    $ make install_sw
56    $ make install_ssldirs
57    $ make install_docs
58    $ make install_fips     # for `enable-fips` only
59
60The `install_fips` make target can also be invoked explicitly to install
61the FIPS provider independently, without installing the rest of OpenSSL.
62
63The Installation of the FIPS provider consists of two steps. In the first step,
64the shared library is copied to its installed location, which by default is
65
66    /usr/local/lib/ossl-modules/fips.so                  on Unix, and
67    C:\Program Files\OpenSSL\lib\ossl-modules\fips.dll   on Windows.
68
69In the second step, the `openssl fipsinstall` command is executed, which completes
70the installation by doing the following two things:
71
72- Runs the FIPS module self tests
73- Generates the so-called FIPS module configuration file containing information
74  about the module such as the module checksum (and for OpenSSL 3.0 the
75  self test status).
76
77The FIPS module must have the self tests run, and the FIPS module config file
78output generated on every machine that it is to be used on. For OpenSSL 3.0,
79you must not copy the FIPS module config file output data from one machine to another.
80
81On Unix, the `openssl fipsinstall` command will be invoked as follows by default:
82
83    $ openssl fipsinstall -out /usr/local/ssl/fipsmodule.cnf -module /usr/local/lib/ossl-modules/fips.so
84
85If you configured OpenSSL to be installed to a different location, the paths will
86vary accordingly. In the rare case that you need to install the fipsmodule.cnf
87to a non-standard location, you can execute the `openssl fipsinstall` command manually.
88
89Installing the FIPS provider and using it with the latest release
90=================================================================
91
92This normally requires you to download 2 copies of the OpenSSL source code.
93
94Download and build a validated FIPS provider
95--------------------------------------------
96
97Refer to <https://www.openssl.org/source/> for information related to
98which versions are FIPS validated. For this example we use OpenSSL 3.0.0.
99
100    $ wget https://www.openssl.org/source/openssl-3.0.0.tar.gz
101    $ tar -xf openssl-3.0.0.tar.gz
102    $ cd openssl-3.0.0
103    $ ./Configure enable-fips
104    $ make
105    $ cd ..
106
107Download and build the latest release of OpenSSL
108------------------------------------------------
109
110We use OpenSSL 3.1.0 here, (but you could also use the latest 3.0.X)
111
112    $ wget https://www.openssl.org/source/openssl-3.1.0.tar.gz
113    $ tar -xf openssl-3.1.0.tar.gz
114    $ cd openssl-3.1.0
115    $ ./Configure enable-fips
116    $ make
117
118Use the OpenSSL FIPS provider for testing
119-----------------------------------------
120
121We do this by replacing the artifact for the OpenSSL 3.1.0 FIPS provider.
122Note that the OpenSSL 3.1.0 FIPS provider has not been validated
123so it must not be used for FIPS purposes.
124
125    $ cp ../openssl-3.0.0/providers/fips.so providers/.
126    $ cp ../openssl-3.0.0/providers/fipsmodule.cnf providers/.
127    // Note that for OpenSSL 3.0 that the `fipsmodule.cnf` file should not
128    // be copied across multiple machines if it contains an entry for
129    // `install-status`. (Otherwise the self tests would be skipped).
130
131    // Validate the output of the following to make sure we are using the
132    // OpenSSL 3.0.0 FIPS provider
133    $ ./util/wrap.pl -fips apps/openssl list -provider-path providers \
134    -provider fips -providers
135
136    // Now run the current tests using the OpenSSL 3.0 FIPS provider.
137    $ make tests
138
139Copy the FIPS provider artifacts (`fips.so` & `fipsmodule.cnf`) to known locations
140-------------------------------------------------------------------------------------
141
142    $ cd ../openssl-3.0.0
143    $ sudo make install_fips
144
145Check that the correct FIPS provider is being used
146--------------------------------------------------
147
148    $./util/wrap.pl -fips apps/openssl list -provider-path providers \
149    -provider fips -providers
150
151    // This should produce the following output
152    Providers:
153      base
154        name: OpenSSL Base Provider
155        version: 3.1.0
156        status: active
157      fips
158        name: OpenSSL FIPS Provider
159        version: 3.0.0
160        status: active
161
162Using the FIPS Module in applications
163=====================================
164
165Documentation about using the FIPS module is available on the [fips_module(7)]
166manual page.
167
168 [fips_module(7)]: https://www.openssl.org/docs/manmaster/man7/fips_module.html
169
170Entropy Source
171==============
172
173The FIPS provider typically relies on an external entropy source,
174specified during OpenSSL build configuration (default: `os`).  However, by
175enabling the `enable-fips-jitter` option during configuration, an internal
176jitter entropy source will be used instead.  Note that this will cause
177the FIPS provider to operate in a non-compliant mode unless an entropy
178assessment [ESV] and validation through the [CMVP] are additionally conducted.
179
180Note that the `enable-fips-jitter` option is only available in OpenSSL
181versions 3.5 and later.
182
183 [CMVP]: https://csrc.nist.gov/projects/cryptographic-module-validation-program
184 [ESV]: https://csrc.nist.gov/Projects/cryptographic-module-validation-program/entropy-validations
185
1863rd-Party Vendor Builds
187=====================================
188
189Some Vendors choose to patch/modify/build their own FIPS provider,
190test it with a Security Laboratory and submit it under their own CMVP
191certificate, instead of using OpenSSL Project submissions. When doing
192so, FIPS provider should uniquely identify its own name and version
193number. The build infrastructure allows to customize FIPS provider
194build information via changes to strings in `VERSION.dat`.
195
196Setting "PRE_RELEASE_TAG" (dashed suffix), "BUILD_METADATA" (plus
197suffix), and "FIPS_VENDOR" allow to control reported FIPS provider
198name and build version as required for CMVP submission.
199

README-PROVIDERS.md

1Providers
2=========
3
4 - [Standard Providers](#standard-providers)
5    - [The Default Provider](#the-default-provider)
6    - [The Legacy Provider](#the-legacy-provider)
7    - [The FIPS Provider](#the-fips-provider)
8    - [The Base Provider](#the-base-provider)
9    - [The Null Provider](#the-null-provider)
10 - [Loading Providers](#loading-providers)
11
12Standard Providers
13==================
14
15Providers are containers for algorithm implementations. Whenever a cryptographic
16algorithm is used via the high level APIs a provider is selected. It is that
17provider implementation that actually does the required work. There are five
18providers distributed with OpenSSL. In the future, we expect third parties to
19distribute their own providers which can be added to OpenSSL dynamically.
20Documentation about writing providers is available on the [provider(7)]
21manual page.
22
23 [provider(7)]: https://www.openssl.org/docs/manmaster/man7/provider.html
24
25The Default Provider
26--------------------
27
28The default provider collects together all of the standard built-in OpenSSL
29algorithm implementations. If an application doesn't specify anything else
30explicitly (e.g. in the application or via config), then this is the provider
31that will be used. It is loaded automatically the first time that we try to
32get an algorithm from a provider if no other provider has been loaded yet.
33If another provider has already been loaded then it won't be loaded
34automatically. Therefore, if you want to use it in conjunction with other
35providers, then you must load it explicitly.
36
37This is a "built-in" provider, which means that it is compiled and linked
38into the libcrypto library and does not exist as a separate standalone module.
39
40The Legacy Provider
41-------------------
42
43The legacy provider is a collection of legacy algorithms that are either no
44longer in common use or considered insecure and strongly discouraged from use.
45However, some applications may need to use these algorithms for backwards
46compatibility reasons. This provider is **not** loaded by default.
47This may mean that some applications upgrading from earlier versions of OpenSSL
48may find that some algorithms are no longer available unless they load the
49legacy provider explicitly.
50
51Algorithms in the legacy provider include MD2, MD4, MDC2, RMD160, CAST5,
52BF (Blowfish), IDEA, SEED, RC2, RC4, RC5 and DES (but not 3DES).
53
54The FIPS Provider
55-----------------
56
57The FIPS provider contains a sub-set of the algorithm implementations available
58from the default provider, consisting of algorithms conforming to FIPS standards.
59It is intended that this provider will be FIPS140-2 validated.
60
61In some cases, there may be minor behavioural differences between algorithm
62implementations in this provider compared to the equivalent algorithm in the
63default provider. This is typically in order to conform to FIPS standards.
64
65The Base Provider
66-----------------
67
68The base provider contains a small sub-set of non-cryptographic algorithms
69available in the default provider. For example, it contains algorithms to
70serialize and deserialize keys to files. If you do not load the default
71provider then you should always load this one instead (in particular, if
72you are using the FIPS provider).
73
74The Null Provider
75-----------------
76
77The null provider is "built-in" to libcrypto and contains no algorithm
78implementations. In order to guarantee that the default provider is not
79automatically loaded, the null provider can be loaded instead.
80
81This can be useful if you are using non-default library contexts and want
82to ensure that the default library context is never used unintentionally.
83
84Loading Providers
85=================
86
87Providers to be loaded can be specified in the OpenSSL config file.
88See the [config(5)] manual page for information about how to configure
89providers via the config file, and how to automatically activate them.
90
91 [config(5)]: https://www.openssl.org/docs/manmaster/man5/config.html
92
93The following is a minimal config file example to load and activate both
94the legacy and the default provider in the default library context.
95
96    openssl_conf = openssl_init
97
98    [openssl_init]
99    providers = provider_sect
100
101    [provider_sect]
102    default = default_sect
103    legacy = legacy_sect
104
105    [default_sect]
106    activate = 1
107
108    [legacy_sect]
109    activate = 1
110
111It is also possible to load providers programmatically. For example you can
112load the legacy provider into the default library context as shown below.
113Note that once you have explicitly loaded a provider into the library context
114the default provider will no longer be automatically loaded. Therefore you will
115often also want to explicitly load the default provider, as is done here:
116
117    #include <stdio.h>
118    #include <stdlib.h>
119
120    #include <openssl/provider.h>
121
122    int main(void)
123    {
124        OSSL_PROVIDER *legacy;
125        OSSL_PROVIDER *deflt;
126
127        /* Load Multiple providers into the default (NULL) library context */
128        legacy = OSSL_PROVIDER_load(NULL, "legacy");
129        if (legacy == NULL) {
130            printf("Failed to load Legacy provider\n");
131            exit(EXIT_FAILURE);
132        }
133        deflt = OSSL_PROVIDER_load(NULL, "default");
134        if (deflt == NULL) {
135            printf("Failed to load Default provider\n");
136            OSSL_PROVIDER_unload(legacy);
137            exit(EXIT_FAILURE);
138        }
139
140        /* Rest of application */
141
142        OSSL_PROVIDER_unload(legacy);
143        OSSL_PROVIDER_unload(deflt);
144        exit(EXIT_SUCCESS);
145    }
146

README-QUIC.md

1Using OpenSSL with QUIC
2=======================
3
4From OpenSSL 3.2, OpenSSL features support for making QUIC connections as a
5client.
6
7Users interested in using the new QUIC functionality are encouraged to look at
8some of the following resources:
9
10- The new [OpenSSL Guide], which provides introductory guides on the use of TLS,
11  QUIC, and other OpenSSL functionality.
12- The [OpenSSL Guide] incorporates various code samples. The complete source
13  for these can be [found in the source tree under `demos/guide`](./demos/guide/).
14- The [openssl-quic(7) manual page], which provides a basic reference overview
15  of QUIC functionality and how use of QUIC differs from use of TLS with regard
16  to our API.
17- The [Demo-Driven Design (DDD)][DDD] demos, which demonstrate the use of QUIC
18  using simple examples. These can be [found in the source tree under
19  `doc/designs/ddd`].
20- The [demo found in `demos/http3`], which provides an HTTP/3 client example
21  using the nghttp3 HTTP/3 library.
22
23FAQ
24---
25
26### Why would I want to use QUIC, and what functionality does QUIC offer relative to TLS or DTLS?
27
28QUIC is a state-of-the-art secure transport protocol carried over UDP. It can
29serve many of the use cases of SSL/TLS as well as those of DTLS.
30
31QUIC delivers a number of advantages such as support for multiple streams of
32communication; it is the basis for HTTP/3 [RFC 9114]; fast connection
33initiation; and connection migration (enabling a connection to survive IP
34address changes). For a more complete description of what QUIC is and its
35advantages see the [QUIC Introduction] in the [OpenSSL Guide].
36
37For a comprehensive overview of OpenSSL's QUIC implementation, see the
38[openssl-quic(7) manual page].
39
40### How can I use HTTP/3 with OpenSSL?
41
42There are many HTTP/3 implementations in C available. The use of one such HTTP/3
43library with OpenSSL QUIC is demonstrated via the [demo found in `demos/http3`].
44
45### How can I use OpenSSL QUIC in my own application for a different protocol?
46
47The [OpenSSL Guide] provides introductory examples for how to make use of
48OpenSSL QUIC.
49
50The [openssl-quic(7) manual page] and the [Demo-Driven Design (DDD)][DDD] demos
51may also be helpful to illustrate the changes needed if you are trying to adapt
52an existing application.
53
54### How can I test QUIC using `openssl s_client`?
55
56There is basic support for single-stream QUIC using `openssl s_client`:
57
58```shell
59$ openssl s_client -quic -alpn myalpn -connect host:port
60```
61
62In the above example replace `host` with the hostname of the server (e.g.
63`www.example.com`) and `port` with the port for the server (e.g. `443`). Replace
64`myalpn` with the Application Layer Protocol to use (e.g.`h3` represents
65HTTP/3). IANA maintains a standard list of [ALPN ids] that can be used.
66
67This example connects to a QUIC server and opens a single bidirectional stream.
68Data can be passed via stdin/stdout as usual. This allows test usage of QUIC
69using simple TCP/TLS-like usage. Note that OpenSSL has no direct support for
70HTTP/3 so connecting to an HTTP/3 server should be possible but sending an
71HTTP/3 request or receiving any response data is not.
72
73[openssl-quic(7) manual page]: https://www.openssl.org/docs/manmaster/man7/openssl-quic.html
74[OpenSSL Guide]: https://www.openssl.org/docs/manmaster/man7/ossl-guide-introduction.html
75[DDD]: https://github.com/openssl/openssl/tree/master/doc/designs/ddd
76[found in the source tree under `doc/designs/ddd`]: ./doc/designs/ddd/
77[demo found in `demos/http3`]: ./demos/http3/
78[QUIC Introduction]: https://www.openssl.org/docs/manmaster/man7/ossl-guide-quic-introduction.html
79[RFC 9114]: https://tools.ietf.org/html/rfc9114
80[ALPN ids]: https://www.iana.org/assignments/tls-extensiontype-values/tls-extensiontype-values.xhtml#alpn-protocol-ids
81

README.md

1Welcome to the OpenSSL Project
2==============================
3
4[![openssl logo]][www.openssl.org]
5
6[![github actions ci badge]][github actions ci]
7![Nightly OS Zoo ci badge](https://github.com/openssl/openssl/actions/workflows/os-zoo.yml/badge.svg)
8![Provider Compatibility](https://github.com/openssl/openssl/actions/workflows/provider-compatibility.yml/badge.svg)
9![Quic Interop](https://github.com/openssl/openssl/actions/workflows/run_quic_interop.yml/badge.svg)
10![Daily checks](https://github.com/openssl/openssl/actions/workflows/run-checker-daily.yml/badge.svg)
11
12OpenSSL is a robust, commercial-grade, full-featured Open Source Toolkit
13for the TLS (formerly SSL), DTLS and QUIC (currently client side only)
14protocols.
15
16The protocol implementations are based on a full-strength general purpose
17cryptographic library, which can also be used stand-alone. Also included is a
18cryptographic module validated to conform with FIPS standards.
19
20OpenSSL is descended from the SSLeay library developed by Eric A. Young
21and Tim J. Hudson.
22
23The official Home Page of the OpenSSL Project is [www.openssl.org].
24
25Table of Contents
26=================
27
28 - [Overview](#overview)
29 - [Download](#download)
30 - [Build and Install](#build-and-install)
31 - [Documentation](#documentation)
32 - [License](#license)
33 - [Support](#support)
34 - [Contributing](#contributing)
35 - [Legalities](#legalities)
36
37Overview
38========
39
40The OpenSSL toolkit includes:
41
42- **libssl**
43  an implementation of all TLS protocol versions up to TLSv1.3 ([RFC 8446]),
44  DTLS protocol versions up to DTLSv1.2 ([RFC 6347]) and
45  the QUIC (currently client side only) version 1 protocol ([RFC 9000]).
46
47- **libcrypto**
48  a full-strength general purpose cryptographic library. It constitutes the
49  basis of the TLS implementation, but can also be used independently.
50
51- **openssl**
52  the OpenSSL command line tool, a swiss army knife for cryptographic tasks,
53  testing and analyzing. It can be used for
54  - creation of key parameters
55  - creation of X.509 certificates, CSRs and CRLs
56  - calculation of message digests
57  - encryption and decryption
58  - SSL/TLS/DTLS and client and server tests
59  - QUIC client tests
60  - handling of S/MIME signed or encrypted mail
61  - and more...
62
63Download
64========
65
66For Production Use
67------------------
68
69Source code tarballs of the official releases can be downloaded from
70[openssl-library.org/source/](https://openssl-library.org/source/).
71The OpenSSL project does not distribute the toolkit in binary form.
72
73However, for a large variety of operating systems precompiled versions
74of the OpenSSL toolkit are available. In particular, on Linux and other
75Unix operating systems, it is normally recommended to link against the
76precompiled shared libraries provided by the distributor or vendor.
77
78We also maintain a list of third parties that produce OpenSSL binaries for
79various Operating Systems (including Windows) on the [Binaries] page on our
80wiki.
81
82For Testing and Development
83---------------------------
84
85Although testing and development could in theory also be done using
86the source tarballs, having a local copy of the git repository with
87the entire project history gives you much more insight into the
88code base.
89
90The main OpenSSL Git repository is private.
91There is a public GitHub mirror of it at [github.com/openssl/openssl],
92which is updated automatically from the former on every commit.
93
94A local copy of the Git repository can be obtained by cloning it from
95the GitHub mirror using
96
97    git clone https://github.com/openssl/openssl.git
98
99If you intend to contribute to OpenSSL, either to fix bugs or contribute
100new features, you need to fork the GitHub mirror and clone your public fork
101instead.
102
103    git clone https://github.com/yourname/openssl.git
104
105This is necessary because all development of OpenSSL nowadays is done via
106GitHub pull requests. For more details, see [Contributing](#contributing).
107
108Build and Install
109=================
110
111After obtaining the Source, have a look at the [INSTALL](INSTALL.md) file for
112detailed instructions about building and installing OpenSSL. For some
113platforms, the installation instructions are amended by a platform specific
114document.
115
116 * [Notes for UNIX-like platforms](NOTES-UNIX.md)
117 * [Notes for Android platforms](NOTES-ANDROID.md)
118 * [Notes for Windows platforms](NOTES-WINDOWS.md)
119 * [Notes for the DOS platform with DJGPP](NOTES-DJGPP.md)
120 * [Notes for the OpenVMS platform](NOTES-VMS.md)
121 * [Notes on Perl](NOTES-PERL.md)
122 * [Notes on Valgrind](NOTES-VALGRIND.md)
123
124Specific notes on upgrading to OpenSSL 3.x from previous versions can be found
125in the [ossl-guide-migration(7ossl)] manual page.
126
127Documentation
128=============
129
130README Files
131------------
132
133There are some README.md files in the top level of the source distribution
134containing additional information on specific topics.
135
136 * [Information about the OpenSSL QUIC protocol implementation](README-QUIC.md)
137 * [Information about the OpenSSL Provider architecture](README-PROVIDERS.md)
138 * [Information about using the OpenSSL FIPS validated module](README-FIPS.md)
139 * [Information about the legacy OpenSSL Engine architecture](README-ENGINES.md)
140
141The OpenSSL Guide
142-----------------
143
144There are some tutorial and introductory pages on some important OpenSSL topics
145within the [OpenSSL Guide].
146
147Manual Pages
148------------
149
150The manual pages for the master branch and all current stable releases are
151available online.
152
153- [OpenSSL master](https://www.openssl.org/docs/manmaster)
154- [OpenSSL 3.0](https://www.openssl.org/docs/man3.0)
155- [OpenSSL 3.1](https://www.openssl.org/docs/man3.1)
156- [OpenSSL 3.2](https://www.openssl.org/docs/man3.2)
157
158Demos
159-----
160
161There are numerous source code demos for using various OpenSSL capabilities in the
162[demos subfolder](./demos).
163
164Wiki
165----
166
167There is a Wiki at [wiki.openssl.org] which is currently not very active.
168It contains a lot of useful information, not all of which is up-to-date.
169
170License
171=======
172
173OpenSSL is licensed under the Apache License 2.0, which means that
174you are free to get and use it for commercial and non-commercial
175purposes as long as you fulfill its conditions.
176
177See the [LICENSE.txt](LICENSE.txt) file for more details.
178
179Support
180=======
181
182There are various ways to get in touch. The correct channel depends on
183your requirement. See the [SUPPORT](SUPPORT.md) file for more details.
184
185Contributing
186============
187
188If you are interested and willing to contribute to the OpenSSL project,
189please take a look at the [CONTRIBUTING](CONTRIBUTING.md) file.
190
191Legalities
192==========
193
194A number of nations restrict the use or export of cryptography. If you are
195potentially subject to such restrictions, you should seek legal advice before
196attempting to develop or distribute cryptographic code.
197
198Copyright
199=========
200
201Copyright (c) 1998-2024 The OpenSSL Project Authors
202
203Copyright (c) 1995-1998 Eric A. Young, Tim J. Hudson
204
205All rights reserved.
206
207<!-- Links  -->
208
209[www.openssl.org]:
210    <https://www.openssl.org>
211    "OpenSSL Homepage"
212
213[github.com/openssl/openssl]:
214    <https://github.com/openssl/openssl>
215    "OpenSSL GitHub Mirror"
216
217[wiki.openssl.org]:
218    <https://wiki.openssl.org>
219    "OpenSSL Wiki"
220
221[ossl-guide-migration(7ossl)]:
222    <https://www.openssl.org/docs/manmaster/man7/ossl-guide-migration.html>
223    "OpenSSL Migration Guide"
224
225[RFC 8446]:
226     <https://tools.ietf.org/html/rfc8446>
227
228[RFC 6347]:
229     <https://tools.ietf.org/html/rfc6347>
230
231[RFC 9000]:
232     <https://tools.ietf.org/html/rfc9000>
233
234[Binaries]:
235    <https://wiki.openssl.org/index.php/Binaries>
236    "List of third party OpenSSL binaries"
237
238[OpenSSL Guide]:
239    <https://www.openssl.org/docs/manmaster/man7/ossl-guide-introduction.html>
240    "An introduction to OpenSSL"
241
242<!-- Logos and Badges -->
243
244[openssl logo]:
245    doc/images/openssl.svg
246    "OpenSSL Logo"
247
248[github actions ci badge]:
249    <https://github.com/openssl/openssl/workflows/GitHub%20CI/badge.svg>
250    "GitHub Actions CI Status"
251
252[github actions ci]:
253    <https://github.com/openssl/openssl/actions?query=workflow%3A%22GitHub+CI%22>
254    "GitHub Actions CI"
255
256[appveyor badge]:
257    <https://ci.appveyor.com/api/projects/status/8e10o7xfrg73v98f/branch/master?svg=true>
258    "AppVeyor Build Status"
259
260[appveyor jobs]:
261    <https://ci.appveyor.com/project/openssl/openssl/branch/master>
262    "AppVeyor Jobs"
263