<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openbsd/src/lib/libcrypto/conf/conf.h, branch OPENBSD_7_9</title>
<subtitle>A mirror of https://github.com/libressl/openbsd.git
</subtitle>
<id>https://git.lua4.win/openbsd/atom?h=OPENBSD_7_9</id>
<link rel='self' href='https://git.lua4.win/openbsd/atom?h=OPENBSD_7_9'/>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/'/>
<updated>2025-03-01T10:11:19+00:00</updated>
<entry>
<title>conf.h: remove outdated comment</title>
<updated>2025-03-01T10:11:19+00:00</updated>
<author>
<name>tb</name>
<email></email>
</author>
<published>2025-03-01T10:11:19+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=b153a3d8f93c3656a3ebfecf4dec185b9f3dfc81'/>
<id>urn:sha1:b153a3d8f93c3656a3ebfecf4dec185b9f3dfc81</id>
<content type='text'>
Despite the claim in this comment, the "new" conf code did replace
the "old" conf code (which no longer exists in the public API).
</content>
</entry>
<entry>
<title>Remove OPENSSL_load_builtin_modules</title>
<updated>2024-08-31T09:54:31+00:00</updated>
<author>
<name>tb</name>
<email></email>
</author>
<published>2024-08-31T09:54:31+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=c43a1080cccb2056d64258ef7ca94968f861e9a1'/>
<id>urn:sha1:c43a1080cccb2056d64258ef7ca94968f861e9a1</id>
<content type='text'>
This became obsolete with the automatic library initialization. Now it
is time for it to become an internal API.

ok beck jsing
</content>
</entry>
<entry>
<title>Unexport CONF_set_nconf()</title>
<updated>2024-08-31T09:53:02+00:00</updated>
<author>
<name>tb</name>
<email></email>
</author>
<published>2024-08-31T09:53:02+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=8009530250a9c798e9955d639c0ef72bbab8caf8'/>
<id>urn:sha1:8009530250a9c798e9955d639c0ef72bbab8caf8</id>
<content type='text'>
This translation device from old to new conf guts will need to stay
for a while. However, it's only needed internally.

ok beck jsing
</content>
</entry>
<entry>
<title>Remove more CONF_* functions that are no longer needed</title>
<updated>2024-08-31T09:50:52+00:00</updated>
<author>
<name>tb</name>
<email></email>
</author>
<published>2024-08-31T09:50:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=7f03b50a5d7cfb3cca856ac51fc6c1d4b97709e6'/>
<id>urn:sha1:7f03b50a5d7cfb3cca856ac51fc6c1d4b97709e6</id>
<content type='text'>
This is the next layer of unused cruft that can now go. The code lovingly
called it 'the "CONF classic" functions'. No tear was shed. Don't worry,
we still have the "New CONF" functions!

ok beck jsing
</content>
</entry>
<entry>
<title>Unexport NCONF_default</title>
<updated>2024-08-31T09:44:00+00:00</updated>
<author>
<name>tb</name>
<email></email>
</author>
<published>2024-08-31T09:44:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=646547a8a28c7b6931751a2ab064fd70d5d8cf92'/>
<id>urn:sha1:646547a8a28c7b6931751a2ab064fd70d5d8cf92</id>
<content type='text'>
The only project I'm aware of that ever used this was rust-openssl
and they did so for no good reason. So remove this API, the crate's
code is already adjusted accordingly.

ok beck jsing
</content>
</entry>
<entry>
<title>Inline NCONF_free_data in its only user</title>
<updated>2024-08-31T09:41:53+00:00</updated>
<author>
<name>tb</name>
<email></email>
</author>
<published>2024-08-31T09:41:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=fc84d1fea737eb16413bd12216cd96db95b290c2'/>
<id>urn:sha1:fc84d1fea737eb16413bd12216cd96db95b290c2</id>
<content type='text'>
ok beck jsing
</content>
</entry>
<entry>
<title>const correct uses of CONF_METHOD</title>
<updated>2024-08-31T09:39:31+00:00</updated>
<author>
<name>tb</name>
<email></email>
</author>
<published>2024-08-31T09:39:31+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=3f796b469989d0e93492a6cb12d24e49b3a58dfd'/>
<id>urn:sha1:3f796b469989d0e93492a6cb12d24e49b3a58dfd</id>
<content type='text'>
While not all of this is strictly needed, it was simply incorrect. This
way another global which was modifiable for no good reason becomes const.

ok beck jsing
</content>
</entry>
<entry>
<title>Stop using conf-&gt;meth_data and make CONF_type_default const</title>
<updated>2024-08-31T09:36:38+00:00</updated>
<author>
<name>tb</name>
<email></email>
</author>
<published>2024-08-31T09:36:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=3eb4b5e423acd1dc7ea9a44c39f16acb3671ed45'/>
<id>urn:sha1:3eb4b5e423acd1dc7ea9a44c39f16acb3671ed45</id>
<content type='text'>
Now that we no longer need to hang a poor man's ctype substitute off
the conf structure, we can get rid of the otherwise unused meth_data
member. This allows us to const correct CONF_type_default. Hopefully
we can remove it soon.

ok beck jsing
</content>
</entry>
<entry>
<title>Remove NCONF_WIN32</title>
<updated>2024-08-31T09:34:05+00:00</updated>
<author>
<name>tb</name>
<email></email>
</author>
<published>2024-08-31T09:34:05+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=67af3e257ef9f1c1bdcc16b7bf9e501296005219'/>
<id>urn:sha1:67af3e257ef9f1c1bdcc16b7bf9e501296005219</id>
<content type='text'>
Undocumented and entirely unused. Gets rid of a big, modifiable, global
table.

ok beck jsing
</content>
</entry>
<entry>
<title>Unexport some conf layers unused outside of libcrypto</title>
<updated>2024-08-31T09:26:18+00:00</updated>
<author>
<name>tb</name>
<email></email>
</author>
<published>2024-08-31T09:26:18+00:00</published>
<link rel='alternate' type='text/html' href='https://git.lua4.win/openbsd/commit/?id=465ca291ecb667ff9b02fa56937b3f5ee1ae84cd'/>
<id>urn:sha1:465ca291ecb667ff9b02fa56937b3f5ee1ae84cd</id>
<content type='text'>
imodules are called imodules because they contain Information about
modules that have been Initialized. Which one of these two I it is
is anyone's best guess. Why anything outside of libcrypto would ever
possibly care will also remain a mystery.

Remove the old way of adding a conf module, user data, stop allowing
to set a method (it's opaque now, remember?) and drop a couple bits
more from the public api interface.

ok beck jsing
</content>
</entry>
</feed>
