Searched refs:device (Results 1 – 16 of 16) sorted by relevance
| /openssl/crypto/dso/ |
| H A D | dso_win32.c | 191 const char *device; member
237 result->device = start; in win32_splitter()
290 result->device = NULL; in win32_splitter()
313 } else if (file_split->device) { in win32_joiner()
344 } else if (file_split->device) { in win32_joiner()
345 strncpy(&result[offset], file_split->device, file_split->devicelen); in win32_joiner()
416 if (!filespec1_split->node && !filespec1_split->device) { in win32_merger()
419 filespec1_split->device = filespec2_split->device; in win32_merger()
|
| /openssl/crypto/ts/ |
| H A D | ts_conf.c | 152 const char *device) in TS_CONF_set_crypto_device() argument
156 if (device == NULL) in TS_CONF_set_crypto_device()
157 device = NCONF_get_string(conf, section, ENV_CRYPTO_DEVICE); in TS_CONF_set_crypto_device()
159 if (device && !TS_CONF_set_default_engine(device)) { in TS_CONF_set_crypto_device()
|
| /openssl/doc/man3/ |
| H A D | BIO_s_null.pod | 21 device.
|
| H A D | RAND_add.pod | 68 chroot(2) jail without the associated device nodes being available. When
|
| H A D | EVP_aes_128_gcm.pod | 149 intended for encrypting data on a storage device.
|
| H A D | ENGINE_add.pod | 414 scheme. However, if the user is expected to know which ENGINE device he/she
|
| /openssl/ |
| H A D | NOTES-DJGPP.md | 42 device" (`/dev/urandom` or `/dev/random`) that serves this purpose."
|
| H A D | README-ENGINES.md | 57 device) but that should be consistent across *all* OpenSSL-based
120 device, they only need to provide the means to carry such user/admin
122 your helpdesk) to the specific ENGINE implementation (and device), and
|
| H A D | INSTALL.md | 496 Use the first device from the `DEVRANDOM` list which can be opened to read
1972 form of a system call or system device), OpenSSL will use the optimal
|
| H A D | NEWS.md | 1615 * PRNG: query at more locations for a random device, automatic query for
|
| H A D | CHANGES.md | 3838 /dev/random device to become readable before reading from the
3839 /dev/urandom device.
3929 OpenSSL normally uses the /dev/urandom device for seeding its CSPRNG.
3930 Contrary to getrandom(), the /dev/urandom device will not block during
4063 * Modified the random device based seed sources to keep the relevant
4066 the associated device nodes being available. This behaviour can be
|
| /openssl/doc/man7/ |
| H A D | x509.pod | 14 an individual, a device, or anything one can imagine. An X.509 CRL
|
| /openssl/doc/man1/ |
| H A D | openssl-passphrase-options.pod | 50 file, device, or named pipe. Only the first line, up to the newline character,
|
| H A D | openssl-namedisplay-options.pod | 89 If the output device is UTF-8 compatible, then using this option (and
|
| /openssl/include/openssl/ |
| H A D | ts.h | 492 const char *device);
|
| /openssl/crypto/objects/ |
| H A D | objects.txt | 1000 Enterprises 45605 1 : id-kp-wisun-fan-device : Wi-SUN Alliance Field Area Network (FAN)
1366 setAttr-IssCap-Sig 2 : setAttr-SecDevSig : secure device signature
|
Completed in 88 milliseconds
