Loading doc/crypto/ASN1_TIME_set.pod +1 −1 Original line number Diff line number Diff line Loading @@ -123,7 +123,7 @@ otherwise. ASN1_TIME_print() returns 1 if the time is successfully printed out and 0 if an error occurred (I/O error or invalid time format). ASN1_TIME_diff() returns 1 for sucess and 0 for failure. It can fail if the ASN1_TIME_diff() returns 1 for success and 0 for failure. It can fail if the pass ASN1_TIME structure has invalid syntax for example. =cut doc/crypto/ASN1_TYPE_get.pod +1 −1 Original line number Diff line number Diff line Loading @@ -78,7 +78,7 @@ ASN1_TYPE_get() returns the type of the ASN1_TYPE argument. ASN1_TYPE_set() does not return a value. ASN1_TYPE_set1() returns 1 for sucess and 0 for failure. ASN1_TYPE_set1() returns 1 for success and 0 for failure. ASN1_TYPE_cmp() returns 0 if the types are identical and non-zero otherwise. Loading doc/crypto/ASN1_generate_nconf.pod +2 −2 Original line number Diff line number Diff line Loading @@ -19,7 +19,7 @@ in an B<ASN1_TYPE> structure. B<str> contains the string to encode B<nconf> or B<cnf> contains the optional configuration information where additional strings will be read from. B<nconf> will typically come from a config file wherease B<cnf> is obtained from an B<X509V3_CTX> structure file whereas B<cnf> is obtained from an B<X509V3_CTX> structure which will typically be used by X509 v3 certificate extension functions. B<cnf> or B<nconf> can be set to B<NULL> if no additional configuration will be used. Loading Loading @@ -181,7 +181,7 @@ A BITSTRING with bits 1 and 5 set and all others zero: FORMAT:BITLIST,BITSTRING:1,5 A more complex example using a config file to produce a SEQUENCE consiting of a BOOL an OID and a UTF8String: SEQUENCE consisting of a BOOL an OID and a UTF8String: asn1 = SEQUENCE:seq_section Loading doc/crypto/BIO_f_cipher.pod +1 −1 Original line number Diff line number Diff line Loading @@ -48,7 +48,7 @@ When encrypting BIO_flush() B<must> be called to flush the final block through the BIO. If it is not then the final block will fail a subsequent decrypt. When decrypting an error on the final block is signalled by a zero When decrypting an error on the final block is signaled by a zero return value from the read operation. A successful decrypt followed by EOF will also return zero for the final read. BIO_get_cipher_status() should be called to determine if the decrypt was successful. Loading doc/crypto/BIO_s_bio.pod +1 −1 Original line number Diff line number Diff line Loading @@ -162,7 +162,7 @@ buffer is full or the read buffer is drained. Then the application has to flush the write buffer and/or fill the read buffer. Use the BIO_ctrl_pending(), to find out whether data is buffered in the BIO and must be transfered to the network. Use BIO_ctrl_get_read_request() to and must be transferred to the network. Use BIO_ctrl_get_read_request() to find out, how many bytes must be written into the buffer before the SSL_operation() can successfully be continued. Loading Loading
doc/crypto/ASN1_TIME_set.pod +1 −1 Original line number Diff line number Diff line Loading @@ -123,7 +123,7 @@ otherwise. ASN1_TIME_print() returns 1 if the time is successfully printed out and 0 if an error occurred (I/O error or invalid time format). ASN1_TIME_diff() returns 1 for sucess and 0 for failure. It can fail if the ASN1_TIME_diff() returns 1 for success and 0 for failure. It can fail if the pass ASN1_TIME structure has invalid syntax for example. =cut
doc/crypto/ASN1_TYPE_get.pod +1 −1 Original line number Diff line number Diff line Loading @@ -78,7 +78,7 @@ ASN1_TYPE_get() returns the type of the ASN1_TYPE argument. ASN1_TYPE_set() does not return a value. ASN1_TYPE_set1() returns 1 for sucess and 0 for failure. ASN1_TYPE_set1() returns 1 for success and 0 for failure. ASN1_TYPE_cmp() returns 0 if the types are identical and non-zero otherwise. Loading
doc/crypto/ASN1_generate_nconf.pod +2 −2 Original line number Diff line number Diff line Loading @@ -19,7 +19,7 @@ in an B<ASN1_TYPE> structure. B<str> contains the string to encode B<nconf> or B<cnf> contains the optional configuration information where additional strings will be read from. B<nconf> will typically come from a config file wherease B<cnf> is obtained from an B<X509V3_CTX> structure file whereas B<cnf> is obtained from an B<X509V3_CTX> structure which will typically be used by X509 v3 certificate extension functions. B<cnf> or B<nconf> can be set to B<NULL> if no additional configuration will be used. Loading Loading @@ -181,7 +181,7 @@ A BITSTRING with bits 1 and 5 set and all others zero: FORMAT:BITLIST,BITSTRING:1,5 A more complex example using a config file to produce a SEQUENCE consiting of a BOOL an OID and a UTF8String: SEQUENCE consisting of a BOOL an OID and a UTF8String: asn1 = SEQUENCE:seq_section Loading
doc/crypto/BIO_f_cipher.pod +1 −1 Original line number Diff line number Diff line Loading @@ -48,7 +48,7 @@ When encrypting BIO_flush() B<must> be called to flush the final block through the BIO. If it is not then the final block will fail a subsequent decrypt. When decrypting an error on the final block is signalled by a zero When decrypting an error on the final block is signaled by a zero return value from the read operation. A successful decrypt followed by EOF will also return zero for the final read. BIO_get_cipher_status() should be called to determine if the decrypt was successful. Loading
doc/crypto/BIO_s_bio.pod +1 −1 Original line number Diff line number Diff line Loading @@ -162,7 +162,7 @@ buffer is full or the read buffer is drained. Then the application has to flush the write buffer and/or fill the read buffer. Use the BIO_ctrl_pending(), to find out whether data is buffered in the BIO and must be transfered to the network. Use BIO_ctrl_get_read_request() to and must be transferred to the network. Use BIO_ctrl_get_read_request() to find out, how many bytes must be written into the buffer before the SSL_operation() can successfully be continued. Loading
Rich Salz <rsalz@akamai.com> Reviewed-by:
Tim Hudson <tjh@openssl.org>