Re: [openssl-commits] Adding set1 aliases for existing *_set_* functions?

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Re: [openssl-commits] Adding set1 aliases for existing *_set_* functions?

Benjamin Kaduk
On 08/01/2016 02:02 PM, Dr. Stephen Henson wrote:
The branch master has been updated
       via  c2e888b54c3b25e89732f6ba66e489ef1ee5ef59 (commit)
       via  b26ab17f3d3f56be57000e99b8ad94a4e90197a6 (commit)
       via  67302ade22b99eaa42031016d4861068b0681db3 (commit)
      from  10b0b817a0abe54f5dabe3b21717d77569ad2d9b (commit)
diff --git a/doc/crypto/X509_get_notBefore.pod b/doc/crypto/X509_get_notBefore.pod
new file mode 100644
index 0000000..ebbd156
--- /dev/null
+++ b/doc/crypto/X509_get_notBefore.pod
[...]
+X509_set_notBefore() and X509_set_notAfter() set the B<notBefore>
+and B<notAfter> fields of B<x> to B<tm>. Ownership of the passed
+parameter B<tm> is not transferred by these functions so it must
+be freed up after the call.
+

Is it worth adding [at this point in the release cycle] X509_set1_not{Before,After}() aliases to make it easier to deprecate the *_set_* forms in the future?

--
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev