summaryrefslogtreecommitdiff
path: root/src/lib/libcrypto/conf/conf_local.h (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Inline _CONF_get_section_values() in its last caller and remove ittb12 days1-3/+1
| | | | | | NCONF_get_section() isn't any clearer by using this indirection. ok jsing
* Inline last use of OPENSSL_load_builtin_modules()tb2024-10-181-3/+1
| | | | | | | This used to be a trivial wrapper of the ASN1_add_oid_module() horror. It's no longer exported, so it can go away. It moves from the terribly named file conf_mall.c to the equally terribly named file conf_sap.c. I have no idea what mall and sap are supposed to mean in this context.
* Remove unused CONF_imodule struct members and accessorstb2024-10-101-9/+1
| | | | ok beck jsing
* Remove OPENSSL_load_builtin_modulestb2024-08-311-1/+3
| | | | | | | This became obsolete with the automatic library initialization. Now it is time for it to become an internal API. ok beck jsing
* Unexport CONF_set_nconf()tb2024-08-311-1/+3
| | | | | | | 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
* Unexport NCONF_defaulttb2024-08-311-1/+3
| | | | | | | | 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
* const correct uses of CONF_METHODtb2024-08-311-2/+2
| | | | | | | 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
* Retire conf_api.h and the API thereintb2024-08-311-1/+13
| | | | | | | This makes the _CONF_* layer of the conf module internal and gets rid of the entirely unused conf_api.h. ok beck jsing
* Unexport some conf layers unused outside of libcryptotb2024-08-311-1/+17
| | | | | | | | | | | | | 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
* Make CONF_METHOD opaquetb2024-08-311-0/+79
Much of conf is designed in such a way that you really have to reach into its structs. This one piece can be hidden. It might even be removed soon. ok beck jsing