openbsd/src/lib/libcrypto/man/PKCS7_add_attribute.3, branch OPENBSD_7_9A mirror of https://github.com/libressl/openbsd.git
https://git.lua4.win/openbsd/atom?h=OPENBSD_7_92025-07-27T19:31:20+00:00Below STANDARDS, reference the two most relevant sections of RFC 5652.2025-07-27T19:31:20+00:00schwarze2025-07-27T19:31:20+00:00urn:sha1:e45df38fdf359c2b4dbbf04d6e24649c51a01b69
Given that RFC 5652 does not override the earlier (and simpler)
standards but instead strives to remain compatible, referencing
both the original and the latest versions seems helpful.
OK tb@
Update PKCS7_add0_attrib_signing_time() docs2025-07-27T07:13:24+00:00tb2025-07-27T07:13:24+00:00urn:sha1:42e6faeb549e5a0113db8e27fa15698b0948fad8
Document the change of behavor from pk7_attr.c r1.17: the time is now
validated to be in correct RFC 5280 time format.
ok kenjiro
.Lb libcrypto ; OK tb@2025-06-08T22:40:31+00:00schwarze2025-06-08T22:40:31+00:00urn:sha1:8be86af02fed1bda350c8dd14ee064cb66e3b0f5describe six more PKCS7 attribute functions2020-06-10T11:39:12+00:00schwarze2020-06-10T11:39:12+00:00urn:sha1:45ebf7393b0624304ba23af89b6900ff4b420486When X509_ATTRIBUTE_create() receives an invalid NID (e.g., -1), return2020-06-04T21:21:03+00:00schwarze2020-06-04T21:21:03+00:00urn:sha1:be3505dc014b9b7022575b6fe4f9c78c2080281c
failure rather than silently constructing a broken X509_ATTRIBUTE object
that might cause NULL pointer accesses later on. This matters because
X509_ATTRIBUTE_create() is used by documented API functions like
PKCS7_add_attribute(3) and the NID comes straight from the user.
This fixes a bug found while working on documentation.
OK tb@ and "thanks" bluhm@
new manual page PKCS7_add_attribute(3);2020-06-04T10:24:27+00:00schwarze2020-06-04T10:24:27+00:00urn:sha1:e0da488570c34ef2f5919259360b745420a92bdd
tweaks and OK tb@