Loading doc/crypto/DH_set_method.pod +1 −1 Original line number Original line Diff line number Diff line Loading @@ -36,7 +36,7 @@ structures created later. B<NB>: This is true only whilst no ENGINE has been set as a default for DH, so this function is no longer recommended. as a default for DH, so this function is no longer recommended. DH_get_default_method() returns a pointer to the current default DH_METHOD. DH_get_default_method() returns a pointer to the current default DH_METHOD. However, the meaningfulness of this result is dependant on whether the ENGINE However, the meaningfulness of this result is dependent on whether the ENGINE API is being used, so this function is no longer recommended. API is being used, so this function is no longer recommended. DH_set_method() selects B<meth> to perform all operations using the key B<dh>. DH_set_method() selects B<meth> to perform all operations using the key B<dh>. Loading doc/crypto/DSA_set_method.pod +1 −1 Original line number Original line Diff line number Diff line Loading @@ -36,7 +36,7 @@ structures created later. B<NB>: This is true only whilst no ENGINE has been set as a default for DSA, so this function is no longer recommended. been set as a default for DSA, so this function is no longer recommended. DSA_get_default_method() returns a pointer to the current default DSA_get_default_method() returns a pointer to the current default DSA_METHOD. However, the meaningfulness of this result is dependant on DSA_METHOD. However, the meaningfulness of this result is dependent on whether the ENGINE API is being used, so this function is no longer whether the ENGINE API is being used, so this function is no longer recommended. recommended. Loading doc/crypto/RAND_set_rand_method.pod +1 −1 Original line number Original line Diff line number Diff line Loading @@ -30,7 +30,7 @@ true only whilst no ENGINE has been set as a default for RAND, so this function is no longer recommended. is no longer recommended. RAND_get_default_method() returns a pointer to the current RAND_METHOD. RAND_get_default_method() returns a pointer to the current RAND_METHOD. However, the meaningfulness of this result is dependant on whether the ENGINE However, the meaningfulness of this result is dependent on whether the ENGINE API is being used, so this function is no longer recommended. API is being used, so this function is no longer recommended. =head1 THE RAND_METHOD STRUCTURE =head1 THE RAND_METHOD STRUCTURE Loading doc/crypto/RSA_set_method.pod +1 −1 Original line number Original line Diff line number Diff line Loading @@ -42,7 +42,7 @@ structures created later. B<NB>: This is true only whilst no ENGINE has been set as a default for RSA, so this function is no longer recommended. been set as a default for RSA, so this function is no longer recommended. RSA_get_default_method() returns a pointer to the current default RSA_get_default_method() returns a pointer to the current default RSA_METHOD. However, the meaningfulness of this result is dependant on RSA_METHOD. However, the meaningfulness of this result is dependent on whether the ENGINE API is being used, so this function is no longer whether the ENGINE API is being used, so this function is no longer recommended. recommended. Loading doc/crypto/engine.pod +3 −3 Original line number Original line Diff line number Diff line Loading @@ -183,7 +183,7 @@ Due to the modular nature of the ENGINE API, pointers to ENGINEs need to be treated as handles - ie. not only as pointers, but also as references to treated as handles - ie. not only as pointers, but also as references to the underlying ENGINE object. Ie. one should obtain a new reference when the underlying ENGINE object. Ie. one should obtain a new reference when making copies of an ENGINE pointer if the copies will be used (and making copies of an ENGINE pointer if the copies will be used (and released) independantly. released) independently. ENGINE objects have two levels of reference-counting to match the way in ENGINE objects have two levels of reference-counting to match the way in which the objects are used. At the most basic level, each ENGINE pointer is which the objects are used. At the most basic level, each ENGINE pointer is Loading @@ -200,7 +200,7 @@ B<functional> reference. This kind of reference can be considered a specialised form of structural reference, because each functional reference specialised form of structural reference, because each functional reference implicitly contains a structural reference as well - however to avoid implicitly contains a structural reference as well - however to avoid difficult-to-find programming bugs, it is recommended to treat the two difficult-to-find programming bugs, it is recommended to treat the two kinds of reference independantly. If you have a functional reference to an kinds of reference independently. If you have a functional reference to an ENGINE, you have a guarantee that the ENGINE has been initialised ready to ENGINE, you have a guarantee that the ENGINE has been initialised ready to perform cryptographic operations and will remain uninitialised perform cryptographic operations and will remain uninitialised until after you have released your reference. until after you have released your reference. Loading Loading @@ -587,7 +587,7 @@ extension). The ENGINE API and internal architecture is currently being reviewed. Slated for The ENGINE API and internal architecture is currently being reviewed. Slated for possible release in 0.9.8 is support for transparent loading of "dynamic" possible release in 0.9.8 is support for transparent loading of "dynamic" ENGINEs (built as self-contained shared-libraries). This would allow ENGINE ENGINEs (built as self-contained shared-libraries). This would allow ENGINE implementations to be provided independantly of OpenSSL libraries and/or implementations to be provided independently of OpenSSL libraries and/or OpenSSL-based applications, and would also remove any requirement for OpenSSL-based applications, and would also remove any requirement for applications to explicitly use the "dynamic" ENGINE to bind to shared-library applications to explicitly use the "dynamic" ENGINE to bind to shared-library implementations. implementations. Loading Loading
doc/crypto/DH_set_method.pod +1 −1 Original line number Original line Diff line number Diff line Loading @@ -36,7 +36,7 @@ structures created later. B<NB>: This is true only whilst no ENGINE has been set as a default for DH, so this function is no longer recommended. as a default for DH, so this function is no longer recommended. DH_get_default_method() returns a pointer to the current default DH_METHOD. DH_get_default_method() returns a pointer to the current default DH_METHOD. However, the meaningfulness of this result is dependant on whether the ENGINE However, the meaningfulness of this result is dependent on whether the ENGINE API is being used, so this function is no longer recommended. API is being used, so this function is no longer recommended. DH_set_method() selects B<meth> to perform all operations using the key B<dh>. DH_set_method() selects B<meth> to perform all operations using the key B<dh>. Loading
doc/crypto/DSA_set_method.pod +1 −1 Original line number Original line Diff line number Diff line Loading @@ -36,7 +36,7 @@ structures created later. B<NB>: This is true only whilst no ENGINE has been set as a default for DSA, so this function is no longer recommended. been set as a default for DSA, so this function is no longer recommended. DSA_get_default_method() returns a pointer to the current default DSA_get_default_method() returns a pointer to the current default DSA_METHOD. However, the meaningfulness of this result is dependant on DSA_METHOD. However, the meaningfulness of this result is dependent on whether the ENGINE API is being used, so this function is no longer whether the ENGINE API is being used, so this function is no longer recommended. recommended. Loading
doc/crypto/RAND_set_rand_method.pod +1 −1 Original line number Original line Diff line number Diff line Loading @@ -30,7 +30,7 @@ true only whilst no ENGINE has been set as a default for RAND, so this function is no longer recommended. is no longer recommended. RAND_get_default_method() returns a pointer to the current RAND_METHOD. RAND_get_default_method() returns a pointer to the current RAND_METHOD. However, the meaningfulness of this result is dependant on whether the ENGINE However, the meaningfulness of this result is dependent on whether the ENGINE API is being used, so this function is no longer recommended. API is being used, so this function is no longer recommended. =head1 THE RAND_METHOD STRUCTURE =head1 THE RAND_METHOD STRUCTURE Loading
doc/crypto/RSA_set_method.pod +1 −1 Original line number Original line Diff line number Diff line Loading @@ -42,7 +42,7 @@ structures created later. B<NB>: This is true only whilst no ENGINE has been set as a default for RSA, so this function is no longer recommended. been set as a default for RSA, so this function is no longer recommended. RSA_get_default_method() returns a pointer to the current default RSA_get_default_method() returns a pointer to the current default RSA_METHOD. However, the meaningfulness of this result is dependant on RSA_METHOD. However, the meaningfulness of this result is dependent on whether the ENGINE API is being used, so this function is no longer whether the ENGINE API is being used, so this function is no longer recommended. recommended. Loading
doc/crypto/engine.pod +3 −3 Original line number Original line Diff line number Diff line Loading @@ -183,7 +183,7 @@ Due to the modular nature of the ENGINE API, pointers to ENGINEs need to be treated as handles - ie. not only as pointers, but also as references to treated as handles - ie. not only as pointers, but also as references to the underlying ENGINE object. Ie. one should obtain a new reference when the underlying ENGINE object. Ie. one should obtain a new reference when making copies of an ENGINE pointer if the copies will be used (and making copies of an ENGINE pointer if the copies will be used (and released) independantly. released) independently. ENGINE objects have two levels of reference-counting to match the way in ENGINE objects have two levels of reference-counting to match the way in which the objects are used. At the most basic level, each ENGINE pointer is which the objects are used. At the most basic level, each ENGINE pointer is Loading @@ -200,7 +200,7 @@ B<functional> reference. This kind of reference can be considered a specialised form of structural reference, because each functional reference specialised form of structural reference, because each functional reference implicitly contains a structural reference as well - however to avoid implicitly contains a structural reference as well - however to avoid difficult-to-find programming bugs, it is recommended to treat the two difficult-to-find programming bugs, it is recommended to treat the two kinds of reference independantly. If you have a functional reference to an kinds of reference independently. If you have a functional reference to an ENGINE, you have a guarantee that the ENGINE has been initialised ready to ENGINE, you have a guarantee that the ENGINE has been initialised ready to perform cryptographic operations and will remain uninitialised perform cryptographic operations and will remain uninitialised until after you have released your reference. until after you have released your reference. Loading Loading @@ -587,7 +587,7 @@ extension). The ENGINE API and internal architecture is currently being reviewed. Slated for The ENGINE API and internal architecture is currently being reviewed. Slated for possible release in 0.9.8 is support for transparent loading of "dynamic" possible release in 0.9.8 is support for transparent loading of "dynamic" ENGINEs (built as self-contained shared-libraries). This would allow ENGINE ENGINEs (built as self-contained shared-libraries). This would allow ENGINE implementations to be provided independantly of OpenSSL libraries and/or implementations to be provided independently of OpenSSL libraries and/or OpenSSL-based applications, and would also remove any requirement for OpenSSL-based applications, and would also remove any requirement for applications to explicitly use the "dynamic" ENGINE to bind to shared-library applications to explicitly use the "dynamic" ENGINE to bind to shared-library implementations. implementations. Loading
