/openssl/doc/man7/ |
H A D | des_modes.pod | 31 The same plaintext block always produces the same ciphertext block 32 (for the same key) making it vulnerable to a 'dictionary attack'. 54 The CBC mode produces the same ciphertext whenever the same 66 enciphering to the same ciphertext. 86 The CFB mode produces the same ciphertext whenever the same 98 enciphering to the same ciphertext. 133 The OFB mode produces the same ciphertext whenever the same 135 over, in the OFB mode the same key stream is produced when the same 176 produced each time from the same parameters. This would be 211 If all 3 keys are the same, this is effectively the same as normal [all …]
|
H A D | EVP_KEYEXCH-DH.pod | 12 Please note that although both key types support the same key exchange 29 filled with zeros where necessary to make the shared secret the same size as 60 The examples assume a host and peer both generate keys using the same 113 Very similar code can be used by the peer to derive the same shared secret
|
H A D | ossl-guide-tls-client-non-block.pod | 76 Note that it is important that you retry exactly the same operation that you 126 other similar function to do the same thing. C<select> waits for the state of 227 In such a case we must retry the same L<SSL_connect(3)> call at a later time. 241 this stage, so such a response is treated in the same way as a fatal error. 248 we should retry exactly the same L<SSL_write_ex(3)> call again. Note that the 249 parameters must be I<exactly> the same, i.e. the same pointer to the buffer to 250 write with the same length. You must not attempt to send different data on a 280 same way as a fatal error. 341 * SSL_ERROR_ZERO_RETURN (i.e. EOF) above). We should do the same back. 359 must free it. The steps to do this for this example are the same as for the [all …]
|
/openssl/doc/man3/ |
H A D | SSL_set_bio.pod | 24 the same value as previously). 29 SSL_set0_wbio() works in the same as SSL_set0_rbio() except that it connects 31 rbio and wbio are the same then SSL_set0_rbio() and SSL_set0_wbio() each take 43 that it connects both the B<rbio> and the B<wbio> at the same time, and 63 If the B<rbio> and B<wbio> parameters are the same and the B<rbio> is not 64 the same as the previously set value then one reference is consumed. 68 If the B<rbio> and B<wbio> parameters are the same and the B<rbio> is the 74 same as the 81 same as the previously set value and the old B<rbio> and B<wbio> values 82 were the same as each other then one reference is consumed for the B<rbio> [all …]
|
H A D | SSL_CTX_set_tlsext_use_srtp.pod | 53 This corresponds to the profile of the same name defined in RFC7714. 57 This corresponds to the profile of the same name defined in RFC7714. 61 This corresponds to the profile of the same name defined in RFC8723. 65 This corresponds to the profile of the same name defined in RFC8723. 69 This corresponds to the profile of the same name defined in RFC8269. 73 This corresponds to the profile of the same name defined in RFC8269. 77 This corresponds to the profile of the same name defined in RFC8269. 81 This corresponds to the profile of the same name defined in RFC8269. 85 This corresponds to the profile of the same name defined in RFC8269. 89 This corresponds to the profile of the same name defined in RFC8269.
|
H A D | BN_add.pod | 51 I<r> may be the same B<BIGNUM> as I<a> or I<b>. 54 I<r> may be the same B<BIGNUM> as I<a> or I<b>. 57 I<r> may be the same B<BIGNUM> as I<a> or I<b>. 61 (C<r=a^2>). I<r> and I<a> may be the same B<BIGNUM>. 84 the same B<BIGNUM> as I<a> or I<b>. For more efficient algorithms for 85 repeated computations using the same modulus, see 108 places the result in I<r>. I<r> may be the same B<BIGNUM> as I<a> or 120 to use the same B<BIGNUM> object for the modulus as for the output.
|
H A D | d2i_PrivateKey.pod | 63 d2i_PrivateKey() does the same as d2i_PrivateKey_ex() except that the default 65 d2i_PublicKey() does the same for public keys. 66 d2i_KeyParams() does the same for key parameters. 71 d2i_PrivateKey_fp() functions are the same except that they read the data from 80 i2d_PublicKey() does the same for public keys. 81 i2d_KeyParams() does the same for key parameters. 83 i2d_PrivateKey_bio() and i2d_PrivateKey_fp() do the same thing except that they
|
H A D | SSL_CTX_add_session.pod | 19 the same session id already exists, the old session is removed by calling 28 whether a session with the same session id already exists. In this case 29 it is assumed that both sessions are identical. If the same session is 53 the same (identical) session twice. In case of the remove operation, the
|
H A D | SSL_get0_connection.pod | 21 When called on a QUIC connection SSL object, it returns the same object. 23 When called on a non-QUIC object, it returns the same object it was passed. 31 SSL object) and otherwise returns the same SSL object passed. It always returns
|
H A D | OSSL_PARAM_dup.pod | 26 new parameter array. If I<params> and I<params1> contain values with the same 30 I<params1> contain the same key, and there are multiple entries within either 31 array that have the same key.
|
H A D | X509_get_serialNumber.pod | 31 X509_get0_serialNumber() is the same as X509_get_serialNumber() except it 38 X509_ACERT_get0_serialNumber() performs the same operation as 41 X509_ACERT_set1_serialNumber() performs the same operation as
|
H A D | RC4_set_key.pod | 42 the same B<key> yield a continuous key stream. 45 key stream to produce the output), decryption uses the same function 59 multiple encryptions using the same key stream.
|
H A D | BN_mod_inverse.pod | 21 variables. B<r> may be the same B<BIGNUM> as B<a>. 25 It is an error to use the same B<BIGNUM> as B<n>.
|
H A D | BF_encrypt.pod | 45 considered good for strong encryption. Blowfish can be used in the same 65 B<ivec> which needs to be passed along into the next call of the same function 66 for the same message. B<ivec> may be initialized with anything, but the 92 It uses the same parameters as BF_cfb64_encrypt(), which must be initialized 93 the same way.
|
H A D | SSL_CTX_set_generate_session_id.pod | 61 of generating the same session id is extremely small (2^256 for SSLv3/TLSv1). 76 another thread is using the same internal session cache, a race condition 77 can occur in that another thread generates the same session id. 80 and the same race condition applies. 91 same id is already in the cache, or 0 otherwise.
|
H A D | BN_rand.pod | 58 BN_rand() is the same as BN_rand_ex() except that the default library context 67 BN_rand_range() is the same as BN_rand_range_ex() except that the default 71 BN_priv_rand_range() have the same semantics as BN_rand_ex(), BN_rand(), 74 same difference between L<RAND_bytes(3)> and L<RAND_priv_bytes(3)>.
|
H A D | EVP_PKEY_verify_recover.pod | 30 EVP_PKEY_verify_recover_init_ex() is the same as 34 EVP_PKEY_verify_recover_init_ex2() is the same as EVP_PKEY_verify_recover_init_ex(), 68 The function EVP_PKEY_verify_recover() can be called more than once on the same 69 context if several operations are performed using the same parameters.
|
H A D | OCSP_response_status.pod | 51 OCSP_RESPID_set_by_name() sets the name of the OCSP_RESPID to be the same as the 54 OCSP_RESPID_set_by_key_ex() sets the key of the OCSP_RESPID to be the same as the 60 OCSP_RESPID_set_by_key() does the same as OCSP_RESPID_set_by_key_ex() except 73 OCSP_RESPID_match() does the same as OCSP_RESPID_match_ex() except that the
|
H A D | X509V3_set_ctx.pod | 29 I<issuer> may be the same pointer value as I<subject> (which usually is an 38 extension with the same OID. 43 X509V3_set_ctx() have the same pointer value
|
H A D | PKCS12_add1_attr_by_NID.pod | 29 These functions do not check whether an existing attribute of the same type is 30 present. There can be multiple attributes with the same type assigned to a
|
/openssl/demos/sslecho/ |
H A D | A-SSL-Docs.txt | 20 The same keys can be used for both communicating instances; same or different machines.
|
/openssl/test/recipes/30-test_evp_data/ |
H A D | evpciph_aes_cts.txt | 15 # AES_CBC results for aligned block lengths. (Result should be the same as 32 byte CTS1 & CTS2) 41 # Manually edited using the same inputs to also produce CS1 ciphertext 42 # where aligned blocks are the same as CBC mode, and partial lengths 156 # Manually edited using the same inputs to also produce CS2 ciphertext 157 # where aligned blocks are the same as CBC mode, and partial lengths 158 # are the same as CS3. 369 # 16 bytes with CS3 should return the same as plain CBC mode.
|
/openssl/doc/man1/ |
H A D | openssl-ca.pod.in | 219 (see the configuration option B<database>), and uses the same 376 YYMMDDHHMMSSZ format (the same as an ASN1 UTCTime structure) or 492 and long names are the same when this option is used. 496 The same as the B<-outdir> command line option. It specifies 501 The same as B<-cert>. It gives the file containing the CA 522 The same as the B<-startdate> option. The start date to certify 527 The same as the B<-enddate> option. Either this option or 582 The same as B<-preserveDN> 592 The same as B<-msie_hack> 651 If you need to include the same component twice then it can be [all …]
|
H A D | openssl-passphrase-options.pod | 53 If the same I<pathname> argument is supplied to both B<-passin> and B<-passout> 60 sending data via a pipe, for example. The same line handling as described for 67 Reads the password from standard input. The same line handling as described for
|
/openssl/doc/internal/man3/ |
H A D | ossl_namemap_new.pod | 63 ossl_namemap_name2num_n() does the same thing as 75 the same number. If some of them already exist in the I<namemap>, 76 they must all have the same associated number, which will be adopted 108 dealing with the same namemap may cause the list of names to change
|