Searched refs:native (Results 1 – 20 of 20) sorted by relevance
/openssl/crypto/asn1/ |
H A D | a_mbstr.c | 281 const int native = value > INT_MAX ? INT_MAX : ossl_fromascii(value); in type_str() local 283 if ((types & B_ASN1_NUMERICSTRING) && !(ossl_isdigit(native) in type_str() 284 || native == ' ')) in type_str() 286 if ((types & B_ASN1_PRINTABLESTRING) && !ossl_isasn1print(native)) in type_str() 288 if ((types & B_ASN1_IA5STRING) && !ossl_isascii(native)) in type_str()
|
/openssl/doc/man7/ |
H A D | provider-object.pod | 5 provider-object - A specification for a provider-native object abstraction 16 The provider-native object abstraction is a set of L<OSSL_PARAM(3)> keys and 17 values that can be used to pass provider-native objects to OpenSSL library 21 The intention is that certain provider-native operations can pass any sort 92 A provider-native object abstraction is an L<OSSL_PARAM(3)> with a selection 122 The object data is suitable as provider-native B<EVP_PKEY> key data. The 130 Since there's no provider-native X.509 object, OpenSSL libraries that 139 Since there's no provider-native X.509 CRL object, OpenSSL libraries that 167 When a provider-native object abstraction is used, it I<must> contain object
|
H A D | provider-encoder.pod | 49 The ENCODER operation is a generic method to encode a provider-native 62 be provider-native and thereby passed via I<obj_raw>), and another one 225 A provider-native object may be associated with a foreign provider, and may 233 given with I<selection> to create a provider-native object that can be 241 OSSL_FUNC_encoder_encode() should take a provider-native object (in
|
H A D | provider-decoder.pod | 48 The DECODER operation is a generic method to create a provider-native 62 that decodes DER to a provider-native object. 65 a provider-native object referenced by an object reference. To import 214 When a provider-native object is created by a decoder it would be unsuitable
|
H A D | provider-storemgmt.pod | 45 to the OpenSSL library in provider-native object abstraction form (see 118 When a provider-native object is created by a store manager it would be unsuitable
|
/openssl/ |
H A D | NOTES-WINDOWS.md | 4 - [Native builds using Visual C++](#native-builds-using-visual-c) 6 #native-builds-using-embarcadero-cbuilder) 7 - [Native builds using MinGW](#native-builds-using-mingw) 8 - [Linking native applications](#linking-native-applications) 14 To build a native OpenSSL you can either use: 31 The native builds using Visual C++ have a `VC-*` prefix. 176 MinGW offers an alternative way to build native OpenSSL, by cross compilation. 183 The resulting OpenSSL does not rely on MSYS2 to run and is fully native. 228 Linking native applications 231 This section applies to all native builds.
|
H A D | NOTES-DJGPP.md | 6 If you wish to compile on native DOS with 8+3 filenames, you will
|
H A D | INSTALL.md | 249 for native binaries, or 1618 ("Makefile" on Unix-like platforms, "makefile" on native Windows,
|
H A D | CHANGES.md | 13500 * Target "mingw" now allows native Windows code to be generated in 17522 * Added native name translation to the existing DSO code 17525 into a canonical native form. Eg. "blah" converted to 19953 * Add support for native Solaris shared libraries. Configure
|
/openssl/doc/internal/man7/ |
H A D | EVP_PKEY.pod | 43 =item provider-native origin 73 Internal provider native keys are also possible to be modified, if the 95 For provider native origin keys, this doesn't require any help from 123 "provider native origin".> 130 For a provider native origin, this requires that the associated 175 For provider native origin keys, that's done by retrieving the key 188 native origin. Instead, we have the operation cache as described above, that 192 Similarly an B<EVP_PKEY> with a provider native origin, will I<never> be
|
/openssl/doc/man3/ |
H A D | EVP_PKEY_gettable_params.pod | 44 obtain an integer value that does not fit into a native C B<int> type will cause 46 value that is negative or does not fit into a native C B<size_t> type using
|
H A D | OSSL_DECODER_CTX.pod | 183 A provider-native object abstraction produced by the decoder. Further 184 information on the provider-native object abstraction can be found in
|
H A D | OSSL_PARAM.pod | 162 length, organized in native form, i.e. most significant byte first on 168 The parameter data is a floating point value in native form. 290 native endianness, and set I<return_size> to the same value as
|
H A D | OSSL_PARAM_allocate_from_text.pod | 79 On systems where the native character encoding is EBCDIC, the bytes in
|
H A D | OSSL_ENCODER_CTX.pod | 151 provider-native object that can be used as first input of an encoding chain,
|
H A D | BN_bn2bin.pod | 74 in native format, i.e. most significant byte first on big-endian platforms,
|
/openssl/doc/internal/man3/ |
H A D | evp_pkey_export_to_provider.pod | 38 provider-native internal key.
|
/openssl/doc/designs/quic-design/ |
H A D | dgram-api.md | 81 stateless and not requiire locking. Therefore the OS-native iovec structures
|
/openssl/Configurations/ |
H A D | README.md | 409 only used when supported. For example, native Windows build doesn't
|
H A D | descrip.mms.tmpl | 17 # Split the native path
|
Completed in 155 milliseconds