crypto(3) | OpenSSL | crypto(3) |
The functionality includes symmetric encryption, public key cryptography and key agreement, certificate handling, cryptographic hash functions and a cryptographic pseudo-random number generator.
SYMMETRIC CIPHERS | openssl_blowfish(3), cast(3), openssl_des(3), idea(3), rc2(3), openssl_rc4(3), rc5(3) |
PUBLIC KEY CRYPTOGRAPHY AND KEY AGREEMENT | openssl_dsa(3), openssl_dh(3), openssl_rsa(3) |
CERTIFICATES | x509(3), x509v3(3) |
AUTHENTICATION CODES, HASH FUNCTIONS | openssl_hmac(3), md2(3), md4(3), openssl_md5(3), openssl_mdc2(3), openssl_ripemd(3), openssl_sha(3) |
AUXILIARY FUNCTIONS | openssl_err(3), openssl_threads(3), openssl_rand(3), OPENSSL_VERSION_NUMBER(3) |
INPUT/OUTPUT, DATA ENCODING | asn1(3), openssl_bio(3), openssl_evp(3), pem(3), pkcs7(3), pkcs12(3) |
INTERNAL FUNCTIONS | openssl_bn(3), openssl_buffer(3), openssl_lhash(3), objects(3), stack(3), txt_db(3) |
int X509_CRL_add0_revoked(X509_CRL *crl, X509_REVOKED *rev); int X509_add1_trust_object(X509 *x, ASN1_OBJECT *obj);
The 0 version uses the supplied structure pointer directly in the parent and it will be freed up when the parent is freed. In the above example crl would be freed but rev would not.
The 1 function uses a copy of the supplied structure pointer (or in some cases increases its link count) in the parent and so both ( x and obj above) should be freed up.
July 20, 2009 | 1.0.1-dev |