| /freebsd-12.1/crypto/openssl/doc/man3/ |
| H A D | EVP_SealInit.pod | 5 EVP_SealInit, EVP_SealUpdate, EVP_SealFinal - EVP envelope encryption 21 encryption. They generate a random key and IV (if required) then 22 "envelope" it by using public key encryption. Data can then be 25 EVP_SealInit() initializes a cipher context B<ctx> for encryption 65 Envelope encryption is the usual method of using public key encryption 66 on large amounts of data, this is because public key encryption is slow 67 but symmetric encryption is fast. So symmetric encryption is used for 68 bulk encryption and the small random symmetric key used is transferred 69 using public key encryption.
|
| H A D | PKCS12_create.pod | 24 B<nid_key> and B<nid_cert> are the encryption algorithms that should be used 26 GCM, CCM, XTS, and OCB are unsupported. B<iter> is the encryption algorithm 35 These defaults are: 40 bit RC2 encryption for certificates, triple DES 36 encryption for private keys, a key iteration count of PKCS12_DEFAULT_ITER 46 it can be used for signing and encryption. This option was useful for old 49 encryption. 59 B<nid_key> or B<nid_cert> can be set to -1 indicating that no encryption
|
| H A D | BF_encrypt.pod | 6 BF_cfb64_encrypt, BF_ofb64_encrypt, BF_options - Blowfish encryption 37 considered good for strong encryption. Blowfish can be used in the same 42 Blowfish consists of a key setup phase and the actual encryption or decryption 48 BF_ecb_encrypt() is the basic Blowfish encryption and decryption function. 50 putting the result in B<out>. B<enc> decides if encryption (B<BF_ENCRYPT>) 72 putting the result in B<out>. B<enc> decides if encryption (BF_ENCRYPT) or 78 putting the result in B<out>. B<enc> decides if encryption (B<BF_ENCRYPT>) 88 encryption. They encrypt/decrypt the first 64 bits of the vector pointed by
|
| H A D | RC4_set_key.pod | 5 RC4_set_key, RC4 - RC4 encryption 23 (16 byte) keys are used for strong encryption, but shorter insecure 26 RC4 consists of a key setup phase and the actual encryption or 38 calls as encryption.
|
| H A D | DES_random_key.pod | 13 DES_fcrypt, DES_crypt - DES encryption 97 This library contains a fast implementation of the DES encryption 100 There are two phases to the use of DES encryption. The first is the 102 actual encryption. A DES key is of type I<DES_cblock>. This type 105 the key; it is used to speed the encryption process. 152 I<ks2> and I<ks3> are the same, it is equivalent to just encryption 156 encryption by using I<ks1> for the final encryption. 169 I<outw> to 'whiten' the encryption. I<inw> and I<outw> are secret 190 a complete DES ECB encryption per I<numbits>, this function is only 209 a complete DES ECB encryption per I<numbits>, this function is only [all …]
|
| H A D | EVP_bf_cbc.pod | 24 The Blowfish encryption algorithm for EVP. 36 Blowfish encryption algorithm in CBC, CFB, ECB and OFB modes respectively.
|
| H A D | EVP_cast5_cbc.pod | 24 The CAST encryption algorithm for EVP. 36 CAST encryption algorithm in CBC, ECB, CFB and OFB modes respectively.
|
| H A D | EVP_idea_cbc.pod | 24 The IDEA encryption algorithm for EVP. 34 The IDEA encryption algorithm in CBC, CFB, ECB and OFB modes respectively.
|
| H A D | PEM_read_bio_PrivateKey.pod | 179 PKCS#5 v2.0 password based encryption algorithms. The B<cipher> argument 180 specifies the encryption algorithm to use: unlike some other PEM routines the 181 encryption is applied at the PKCS#8 level and not in the PEM headers. If 182 B<cipher> is NULL then no encryption is used and a PKCS#8 PrivateKeyInfo 187 it uses PKCS#5 v1.5 or PKCS#12 encryption algorithms instead. The algorithm 267 which specifies the encryption algorithm to use, encryption is done 329 These old B<PrivateKey> routines use a non standard technique for encryption. 342 contains two comma separated values: the encryption algorithm name as 347 The encryption key is derived using EVP_BytesToKey(). The cipher's 424 triple DES encryption, the pass phrase is prompted for: [all …]
|
| H A D | EVP_seed_cbc.pod | 24 The SEED encryption algorithm for EVP. 36 The SEED encryption algorithm in CBC, CFB, ECB and OFB modes respectively.
|
| H A D | BIO_f_cipher.pod | 29 BIO_flush() on an encryption BIO that is being written through is 34 and IV B<iv>. B<enc> should be set to 1 for encryption and zero for 37 When reading from an encryption BIO the final block is automatically
|
| H A D | OpenSSL_add_all_algorithms.pod | 32 OpenSSL_add_all_ciphers() adds all encryption algorithms to the table including 33 password based encryption algorithms.
|
| H A D | EVP_rc2_cbc.pod | 28 The RC2 encryption algorithm for EVP. 38 RC2 encryption algorithm in CBC, CFB, ECB and OFB modes respectively. This is a
|
| H A D | EVP_aes.pod | 65 The AES encryption algorithm for EVP. 100 Authenticated encryption with AES in CBC mode using SHA-1 as HMAC, with keys of 110 Authenticated encryption with AES in CBC mode using SHA256 (SHA-2, 256-bits) as
|
| H A D | EVP_rc5_32_12_16_cbc.pod | 24 The RC5 encryption algorithm for EVP. 34 RC5 encryption algorithm in CBC, CFB, ECB and OFB modes respectively. This is a
|
| /freebsd-12.1/crypto/openssl/doc/man7/ |
| H A D | evp.pod | 17 functions provide public key encryption and decryption to implement digital "envelopes". 25 Symmetric encryption is available with the L<B<EVP_Encrypt>I<XXX>|EVP_EncryptInit(3)> 50 =item For encryption and decryption see L<EVP_PKEY_encrypt(3)> 52 these functions perform encryption and decryption only. As public key 53 encryption is an expensive operation, normally you would wrap 60 based encryption. Careful selection of the parameters will provide a PKCS#5 PBKDF1 compatible
|
| /freebsd-12.1/crypto/openssh/ |
| H A D | PROTOCOL.chacha20poly1305 | 2 encryption cipher supported by OpenSSH. 17 authenticated encryption mode. The construction used is based on that 19 data passed to the MAC and in the addition of encryption of the packet 25 The [email protected] offers both encryption and 60 for encryption of the packet payload. 87 ChaCha20 must never reuse a {key, nonce} for encryption nor may it be
|
| /freebsd-12.1/contrib/wpa/wpa_supplicant/ |
| H A D | eap_testing.txt | 120 1) PEAPv1 required new label, "client PEAP encryption" instead of "client EAP 121 encryption", during key derivation (requires phase1="peaplabel=1" in the 175 Note: PEAPv1 requires TLS key derivation to use label "client EAP encryption" 202 Note: PEAPv1 requires TLS key derivation to use label "client EAP encryption" 224 Note: PEAPv1 requires TLS key derivation to use label "client EAP encryption" 363 - uses label "client EAP encryption" 369 - uses label "client EAP encryption" 375 - uses label "client PEAP encryption" 380 - uses label "client PEAP encryption" 386 - uses label "client EAP encryption" [all …]
|
| /freebsd-12.1/crypto/openssl/doc/man1/ |
| H A D | pkcs8.pod | 83 default. If any encryption options are set then a pass phrase will be 95 the password in deriving the encryption key for the PKCS#8 output. 101 structures using an appropriate password based encryption algorithm. With 124 The B<alg> argument is the encryption algorithm to use, valid values include 152 Uses the B<scrypt> algorithm for private key encryption using default 181 PKCS#8 format using the specified encryption parameters unless B<-nocrypt> 191 encryption algorithms such as 56 bit DES. 210 PKCS#8 format because the encryption details are included at an ASN1 235 These algorithms use the PKCS#12 password based encryption algorithm and 236 allow strong encryption algorithms like triple DES or 128 bit RC2 to be used. [all …]
|
| H A D | enc.pod | 49 either by itself or in addition to the encryption or decryption. 86 Base64 process the data. This means that if encryption is taking place 87 the data is base64 encoded after encryption. If decryption is set then 116 Use a given number of iterations on the password in deriving the encryption key. 161 Print out the key and IV used then immediately exit: don't do any encryption 178 Compress or decompress clear text using zlib before encryption or after 184 Use NULL cipher (no encryption or decryption of input). 209 Engines which provide entirely new encryption algorithms (such as the ccgost 228 encryption key. When the salt is being used the first eight bytes of the 257 The B<enc> program does not support authenticated encryption modes [all …]
|
| H A D | rsa.pod | 44 traditional SSLeay compatible format for private key encryption: newer 83 option is not specified. If any encryption options are set then a pass phrase 98 encryption option can be used to remove the pass phrase from a key, or by 99 setting the encryption options it can be use to add or change the pass phrase.
|
| /freebsd-12.1/crypto/heimdal/lib/krb5/ |
| H A D | krb5_err.et | 25 error_code ETYPE_NOSUPP, "KDC has no support for encryption type" 101 error_code PUBLIC_KEY_ENCRYPTION_NOT_SUPPORTED, "Public key encryption not supported" 150 error_code KRB5_PROG_ETYPE_NOSUPP, "Program lacks support for encryption type" 152 error_code KRB5_WRONG_ETYPE, "Requested encryption type not used in message" 200 error_code KRB5_BAD_ENCTYPE, "Bad encryption type" 201 error_code KRB5_BAD_KEYSIZE, "Key size is incompatible with encryption type" 202 error_code KRB5_BAD_MSIZE, "Message size is incompatible with encryption type" 214 error_code KRB5_CC_NOT_KTYPE, "No credentials found with supported encryption types" 259 error_code KRB5_SAM_INVALID_ETYPE, "Invalid encryption type in SAM challenge"
|
| /freebsd-12.1/contrib/apr-util/ |
| H A D | README | 82 encryption software. BEFORE using any encryption software, please 84 import, possession, or use, and re-export of encryption software, to 102 functions that make use of a general-purpose encryption library,
|
| /freebsd-12.1/bin/ed/ |
| H A D | POSIX | 29 encryption. The `x' command prompts the user to enter a key used for 31 is entered as the key, then encryption is disabled. Otherwise, a key 33 effect until encryption is disabled. For more information on the 34 encryption algorithm, see the bdes(1) man page. Encryption/decryption
|
| /freebsd-12.1/crypto/heimdal/doc/ |
| H A D | win2k.texi | 126 care to the encryption types and salting used for those keys. There should be 127 no encryption type stronger than the one configured on Windows side for this 134 @item Windows 2000: maximum encryption type is DES 135 @item Windows 2003: maximum encryption type is DES 136 @item Windows 2003RC2: maximum encryption type is RC4, relationship defaults to DES 137 @item Windows 2008: maximum encryption type is AES, relationship defaults to RC4 140 For Windows 2003RC2, to change the trust encryption type, you have to use the 155 inter-realm keys, using heimdal default encryption types: 199 @samp{des-cbc-md5}) and its own proprietary encryption that is based on MD4 and
|