| /freebsd/targets/pseudo/userland/secure/ |
| H A D | Makefile.depend | 5 secure/lib/libcrypto/engines/lib4758cca \
6 secure/lib/libcrypto/engines/libaep \
7 secure/lib/libcrypto/engines/libatalla \
8 secure/lib/libcrypto/engines/libcapi \
9 secure/lib/libcrypto/engines/libchil \
10 secure/lib/libcrypto/engines/libcswift \
11 secure/lib/libcrypto/engines/libgost \
12 secure/lib/libcrypto/engines/libnuron \
13 secure/lib/libcrypto/engines/libsureware \
14 secure/lib/libcrypto/engines/libubsec \
|
| /freebsd/crypto/openssl/Configurations/ |
| H A D | README-design.md | 54 `libcrypto`, an module `engines/ossltest` and their sources and
121 # engines/build.info
132 This is the `build.info` file in `engines/`, telling us that two modules
133 called `engines/dasync` and `engines/ossltest` shall be built, that
134 `dasync`'s source is `engines/e_dasync.c` and `ossltest`'s source is
135 `engines/e_ossltest.c` and that the include directory `include/` may
158 MODULES=engines/dasync
159 SOURCE[engines/dasync]=engines/e_dasync.c
160 DEPEND[engines/dasync]=libcrypto
161 INCLUDE[engines/dasync]=include
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/fsi/ |
| H A D | fsi.txt | 5 engines within those slaves. However, we have a facility to match devicetree
6 nodes to probed engines. This allows for fsi engines to expose non-probeable
16 represent the FSI slaves and their slave engines. As a basic outline:
41 adding subordinate device tree nodes as children of FSI engines.
79 Each slave provides an address-space, under which the engines are accessible.
91 FSI engines (devices)
94 Engines are identified by their address under the slaves' address spaces. We
116 additional engines, but they don't necessarily need to be describe in the
|
| /freebsd/crypto/openssl/ |
| H A D | README-ENGINES.md | 1 Engines chapter
16 via providers, and existing engines should be converted to providers
54 based input to those ENGINEs, in the form of name-value pairs. This is an
55 extensible way for ENGINEs to define their own "configuration" mechanisms
64 with the various compiled-in ENGINEs (see further down for dynamic
65 ENGINEs), use the "engine" openssl utility with full verbosity, i.e.:
83 the vendors of the devices these ENGINEs support have contributed to the
130 DYNAMIC ENGINES
160 independent things. Other ENGINEs typically don't do this so there is
176 multiple ENGINEs, but if you know the engine id you expect to be using,
[all …]
|
| /freebsd/crypto/openssl/crypto/engine/ |
| H A D | README.md | 1 Notes on engines of 2001-09-24
52 hooking in ENGINEs is that multiple ENGINEs may implement the same ciphers. The
96 ENGINE code will return NULL because no ENGINEs will have had any cipher
123 if ENGINEs implement *all* possible algorithms, an application using only
131 mostly to avoid a lot of "init()"-thrashing on ENGINEs (that may have to load
137 pointers to ENGINEs that implement that particular 'nid'. Each "pile" uses some
141 that an application could have support for 10 ENGINEs statically linked
143 ENGINEs support. If each of those ENGINEs has a "des_cbc" implementation, we
145 each of those 10 ENGINEs. Instead, the first such request will try to do that
153 ENGINE_set_table_flags(), in which case the only ENGINEs that tb_cipher.c will
[all …]
|
| /freebsd/crypto/openssl/engines/ |
| H A D | build.info | 39 GENERATE[padlock.ld]=../util/engines.num
49 GENERATE[capi.ld]=../util/engines.num
59 GENERATE[afalg.ld]=../util/engines.num
69 GENERATE[devcrypto.ld]=../util/engines.num
80 GENERATE[loader_attic.ld]=../util/engines.num
90 GENERATE[dasync.ld]=../util/engines.num
98 GENERATE[ossltest.ld]=../util/engines.num
|
| /freebsd/crypto/openssl/doc/man1/ |
| H A D | openssl-engine.pod.in | 6 openssl-engine - load and query engines
25 This command has been deprecated. Providers should be used instead of engines.
29 Engines may be specified before and after all other command-line flags.
63 Command-line configuration of engines.
92 DIR_ADD: Adds a directory from which ENGINEs can be loaded
110 The path to the engines directory.
|
| H A D | openssl-list.pod.in | 41 -}[B<-engines>]
178 =item B<-engines>
182 Display a list of loaded engines.
235 The B<-engines>, B<-digest-commands>, and B<-cipher-commands> options
|
| /freebsd/crypto/openssl/VMS/ |
| H A D | openssl_startup.com.in | 18 $ ! OSSL$ENGINESnnn Where the engines modules are located
29 $ ! or that depend on engines.
34 $ ! OSSL$ENGINES Alias for OSSL$ENGINESnnn
100 $ DEF OSSL$ENGINES'sv''pz' OSSL$INSTROOT:[ENGINES'sv''pz'.'arch']
114 $ DEF OSSL$ENGINES'pz' OSSL$ENGINES'sv''pz'
|
| /freebsd/crypto/openssl/test/ |
| H A D | enginetest.c | 77 TEST_info("Engines:"); in test_engines()
82 TEST_info("Engines:"); in test_engines()
89 TEST_info("Engines:"); in test_engines()
95 TEST_info("Engines:"); in test_engines()
100 TEST_info("Engines:"); in test_engines()
105 TEST_info("Engines:"); in test_engines()
120 TEST_info("Engines:"); in test_engines()
125 TEST_info("Engines:"); in test_engines()
131 * file to be loaded and don't otherwise load any built in engines, in test_engines()
141 TEST_info("Engines:"); in test_engines()
|
| /freebsd/secure/lib/libcrypto/man/man3/ |
| H A D | ENGINE_add.3 | 330 Due to the modular nature of the \s-1ENGINE API,\s0 pointers to ENGINEs need to be
344 implementations. Indeed it's quite possible that most ENGINEs will not
345 initialise at all in typical environments, as ENGINEs are typically used to
358 This basic type of reference is used for instantiating new ENGINEs,
360 ENGINEs, reading information about an \s-1ENGINE,\s0 etc. Essentially a structural
422 algorithms and modes, and ENGINEs can support arbitrarily many of them.
438 this question it must iterate across all the registered ENGINEs in the
461 \&\*(L"visible\*(R" ENGINEs from which it has to operate \- at start-up, this list is
469 The fact that ENGINEs are made visible to OpenSSL (and thus are linked into
485 if any ENGINEs are loaded, even if not registered or used, it was necessary to
[all …]
|
| /freebsd/crypto/openssl/doc/man3/ |
| H A D | ENGINE_add.pod | 190 Due to the modular nature of the ENGINE API, pointers to ENGINEs need to be
204 implementations. Indeed it's quite possible that most ENGINEs will not
205 initialise at all in typical environments, as ENGINEs are typically used to
218 This basic type of reference is used for instantiating new ENGINEs,
220 ENGINEs, reading information about an ENGINE, etc. Essentially a structural
284 algorithms and modes, and ENGINEs can support arbitrarily many of them.
300 this question it must iterate across all the registered ENGINEs in the
324 "visible" ENGINEs from which it has to operate - at start-up, this list is
332 The fact that ENGINEs are made visible to OpenSSL (and thus are linked into
348 if any ENGINEs are loaded, even if not registered or used, it was necessary to
[all …]
|
| H A D | OPENSSL_config.pod | 45 advisable. For example, to load dynamic ENGINEs from shared libraries (DSOs).
47 very few can load and use dynamic ENGINEs. Equally in future more sophisticated
48 ENGINEs will require certain control operations to customize them. If an
|
| /freebsd/secure/usr.bin/openssl/man/ |
| H A D | openssl-engine.1 | 140 openssl\-engine \- load and query engines
157 This command has been deprecated. Providers should be used instead of engines.
161 Engines may be specified before and after all other command-line flags.
189 Command-line configuration of engines.
216 \& DIR_ADD: Adds a directory from which ENGINEs can be loaded
234 The path to the engines directory.
|
| H A D | openssl-list.1 | 169 [\fB\-engines\fR]
279 .IP "\fB\-engines\fR" 4
280 .IX Item "-engines"
283 Display a list of loaded engines.
334 The \fB\-engines\fR, \fB\-digest\-commands\fR, and \fB\-cipher\-commands\fR options
|
| /freebsd/secure/lib/libcrypto/engines/ |
| H A D | Makefile.inc | 1 SHLIBDIR= ${LIBDIR}/engines-3
5 CFLAGS+= -I${LCRYPTO_SRC}/engines
20 .PATH: ${LCRYPTO_SRC}/engines
|
| /freebsd/crypto/openssl/apps/ |
| H A D | engine.c | 46 {"tt", OPT_TT, '-', "Display error trace for unavailable engines"},
302 STACK_OF(OPENSSL_CSTRING) *engines = sk_OPENSSL_CSTRING_new_null(); in engine_main()
312 if (engines == NULL || pre_cmds == NULL || post_cmds == NULL) in engine_main()
319 sk_OPENSSL_CSTRING_push(engines, argv1); in engine_main()
375 sk_OPENSSL_CSTRING_push(engines, *argv); in engine_main()
378 if (sk_OPENSSL_CSTRING_num(engines) == 0) { in engine_main()
380 sk_OPENSSL_CSTRING_push(engines, ENGINE_get_id(e)); in engine_main()
385 for (i = 0; i < sk_OPENSSL_CSTRING_num(engines); i++) { in engine_main()
386 const char *id = sk_OPENSSL_CSTRING_value(engines, i); in engine_main()
490 sk_OPENSSL_CSTRING_free(engines); in engine_main()
|
| /freebsd/sys/contrib/device-tree/Bindings/crypto/ |
| H A D | aspeed,ast2600-acry.yaml | 7 title: ASPEED ACRY ECDSA/RSA Hardware Accelerator Engines
13 The ACRY ECDSA/RSA engines is designed to accelerate the throughput
15 divided into two independent engines - ECC Engine and RSA Engine.
|
| H A D | mv_cesa.txt | 1 Marvell Cryptographic Engines And Security Accelerator
15 - clocks: reference to the crypto engines clocks. This property is only
|
| H A D | aspeed,ast2500-hace.yaml | 7 title: ASPEED HACE hash and crypto Hardware Accelerator Engines
15 divided into two independently engines - Hash Engine and Crypto Engine.
|
| /freebsd/secure/lib/libcrypto/man/man7/ |
| H A D | migration_guide.7 | 247 \fIEngines and \*(L"\s-1METHOD\*(R"\s0 APIs\fR
248 .IX Subsection "Engines and METHOD APIs"
251 support engines, including the \s-1ENGINE API\s0 and any function that creates or
258 \&\s-1FIPS\s0 module, as detailed below. Authors and maintainers of external engines are
259 strongly encouraged to refactor their code transforming engines into providers
262 \fISupport of legacy engines\fR
263 .IX Subsection "Support of legacy engines"
265 If openssl is not built without engine support or deprecated \s-1API\s0 support, engines
268 New algorithms provided via engines will still work.
274 To ensure the future compatibility, the engines should be turned to providers.
[all …]
|
| /freebsd/share/man/man4/ |
| H A D | nctgpio.4 | 25 Nuvoton NCT5104D (PC-Engines APU)
27 Nuvoton NCT5104D (PC-Engines APU3)
|
| /freebsd/crypto/openssl/doc/man5/ |
| H A D | config.pod | 187 engines = engines
202 [engines]
354 The name B<engines> in the initialization section names the section
368 specified in the list of engines. If present, it must be first.
371 [engines]
406 [engines]
529 The path to the engines directory.
|
| /freebsd/crypto/openssl/include/openssl/ |
| H A D | engine.h | 62 * initialise registered ENGINEs if they are not already initialised.
71 * This flag is for ENGINEs that wish to handle the various 'CMD'-related
79 * This flag is for ENGINEs who return new duplicate structures when found
84 * a new structure. Normally, ENGINEs don't declare this flag so
99 * ENGINEs can support their own command types, and these flags are used in
131 * ENGINEs relying on these commands should compile conditional support for
142 * command numbers are shared between all engines, even if some don't make
143 * sense to some engines. In such a case, they do nothing but return the
370 /*- Manage registration of ENGINEs per "table". For each type, there are 3
465 * run-time to control behaviour of specific engines. As such, it shouldn't
[all …]
|
| /freebsd/secure/lib/libcrypto/man/man5/ |
| H A D | config.5 | 330 \& engines = engines
345 \& [engines]
497 The name \fBengines\fR in the initialization section names the section
508 specified in the list of engines. If present, it must be first.
512 \& [engines]
544 \& [engines]
662 The path to the engines directory.
|