<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openbsd/src/lib/libcrypto/man/OCSP_cert_to_id.3, branch libressl-v3.3.4</title>
<subtitle>A mirror of https://github.com/libressl/openbsd.git
</subtitle>
<id>https://git.lua4.win/openbsd/atom?h=libressl-v3.3.4</id>
<link rel='self' href='https://git.lua4.win/openbsd/atom?h=libressl-v3.3.4'/>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/'/>
<updated>2019-06-06T01:06:59+00:00</updated>
<entry>
<title>Tree structure for manual pages: crypto(3) links to 33 function</title>
<updated>2019-06-06T01:06:59+00:00</updated>
<author>
<name>schwarze</name>
<email></email>
</author>
<published>2019-06-06T01:06:59+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=580f04977d3a77664477818e7264e008d1ba5843'/>
<id>urn:sha1:580f04977d3a77664477818e7264e008d1ba5843</id>
<content type='text'>
group pages, and these link on to all their second-level subpages.
Only a handful of second-level pages have third-level subpages.
So all crypto pages can now be reached from the www.libressl.org
frontpage via at most four clicks, in most cases three clicks.
Also link back from leaf pages to their respective group pages
and add a couple of additional links between related pages.
Triggered by a question from deraadt@.
OK jmc@ tb@
</content>
</entry>
<entry>
<title>Document const change for OCSP_cert_to_id()</title>
<updated>2018-08-24T20:04:10+00:00</updated>
<author>
<name>tb</name>
<email></email>
</author>
<published>2018-08-24T20:04:10+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=f1777ff7b396365116d8aa4df0d56e4087ccac71'/>
<id>urn:sha1:f1777ff7b396365116d8aa4df0d56e4087ccac71</id>
<content type='text'>
ok jsing
</content>
</entry>
<entry>
<title>In ocsp.h rev. 1.14 2018/05/13 10:30:52, tb@ added const qualifiers</title>
<updated>2018-05-13T14:20:13+00:00</updated>
<author>
<name>schwarze</name>
<email></email>
</author>
<published>2018-05-13T14:20:13+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=0c7a19d0ea69be2bae02c4270b611516553c057b'/>
<id>urn:sha1:0c7a19d0ea69be2bae02c4270b611516553c057b</id>
<content type='text'>
to the arguments of OCSP_cert_id_new(3).  Adjust the manual.
</content>
</entry>
<entry>
<title>crypto HISTORY up to 0.9.7; researched from OpenSSL git</title>
<updated>2018-03-22T21:08:22+00:00</updated>
<author>
<name>schwarze</name>
<email></email>
</author>
<published>2018-03-22T21:08:22+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=d1309e0bd6b01602902f2b12832ae8d7492733e1'/>
<id>urn:sha1:d1309e0bd6b01602902f2b12832ae8d7492733e1</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Consistently mark up various ASN.1 type names defined in standards</title>
<updated>2016-12-25T22:15:10+00:00</updated>
<author>
<name>schwarze</name>
<email></email>
</author>
<published>2016-12-25T22:15:10+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=7f3157687a730f8df92ddc11f707bf4e97be9a47'/>
<id>urn:sha1:7f3157687a730f8df92ddc11f707bf4e97be9a47</id>
<content type='text'>
related to X.509 with .Vt such that they can be searched for.
</content>
</entry>
<entry>
<title>Make sure all manual pages discussing X509_NAME objects</title>
<updated>2016-12-14T16:20:28+00:00</updated>
<author>
<name>schwarze</name>
<email></email>
</author>
<published>2016-12-14T16:20:28+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=3c15a77c233c82358d5de43dedd45b53fd49f48c'/>
<id>urn:sha1:3c15a77c233c82358d5de43dedd45b53fd49f48c</id>
<content type='text'>
reference X509_NAME_new(3).  Sparingly add a few other
references to relevant X509_NAME*(3) pages while here.
</content>
</entry>
<entry>
<title>Document OCSP_CERTID_new(3) listed in &lt;openssl/ocsp.h&gt; and in OpenSSL</title>
<updated>2016-12-12T20:41:48+00:00</updated>
<author>
<name>schwarze</name>
<email></email>
</author>
<published>2016-12-12T20:41:48+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=404b396cfc71ebac163e039f7d0982cc2cc14142'/>
<id>urn:sha1:404b396cfc71ebac163e039f7d0982cc2cc14142</id>
<content type='text'>
doc/man3/X509_dup.pod.  Note that the OpenSSL documentation specifies
the wrong header file.

Add some information about what the OCSP_CERTID object actually
represents, along with the pertinent STANDARDS reference.
</content>
</entry>
<entry>
<title>Delete most references to crypto(3).  That page isn't useful enough</title>
<updated>2016-12-06T14:54:55+00:00</updated>
<author>
<name>schwarze</name>
<email></email>
</author>
<published>2016-12-06T14:54:55+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=08cf20e679b8fa063147338e4c21d29d9ff9c0b3'/>
<id>urn:sha1:08cf20e679b8fa063147338e4c21d29d9ff9c0b3</id>
<content type='text'>
to be pointed to from random individual pages.
</content>
</entry>
<entry>
<title>various cleanup;</title>
<updated>2016-11-30T20:54:25+00:00</updated>
<author>
<name>jmc</name>
<email></email>
</author>
<published>2016-11-30T20:54:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=2f28744cd6ea33fb21cde52453fa9ca739e5e641'/>
<id>urn:sha1:2f28744cd6ea33fb21cde52453fa9ca739e5e641</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Import OCSP documentation from OpenSSL, leaving out some stuff</title>
<updated>2016-11-27T20:40:07+00:00</updated>
<author>
<name>schwarze</name>
<email></email>
</author>
<published>2016-11-27T20:40:07+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=2613b464a5e73671df478b07cbb7bb84c6ceea0d'/>
<id>urn:sha1:2613b464a5e73671df478b07cbb7bb84c6ceea0d</id>
<content type='text'>
that we don't have, fixing some bugs and tweaking some parts for
readability.

P.S.
Why did some people write a HTTP client implementation and then
decide that the best place to publish it might be a crypto(3)
library?  Oh never mind, to go easy on my sanity, i should probably
stop asking such questions and just document what i find.
</content>
</entry>
</feed>
