summaryrefslogtreecommitdiff
path: root/src/lib/libcrypto/man/X509_NAME_get_index_by_NID.3 (follow)
Commit message (Collapse)AuthorAgeFilesLines
* .Lb libcrypto ; OK tb@schwarze2025-06-081-2/+3
|
* Make X509_NAME_get_text_by[NID|OBJ] safer.beck2023-05-291-10/+20
| | | | | | | | | | | | | | | | This is an un-revert with nits of the previously landed change to do this which broke libtls. libtls has now been changed to not use this function. This change ensures that if something is returned it is "text" (UTF-8) and a C string not containing a NUL byte. Historically callers to this function assume the result is text and a C string however the OpenSSL version simply hands them the bytes from an ASN1_STRING and expects them to know bad things can happen which they almost universally do not check for. Partly inspired by goings on in boringssl. ok jsing@ tb@
* Revert utf-8 fix for X509_NAME_get_index_by_NID to avoid libtlsbeck2023-05-031-20/+10
| | | | | | | regress for the moment. this will come back after we rethink the failure versus not there case. ok tb@ jsing@
* Change X509_NAME_get_index_by[NID|OBJ] to be safer.beck2023-05-021-10/+20
| | | | | | | | | | | | | | | | | | | | | | Currently these functions return raw ASN1_STRING bytes as a C string and ignore the encoding in a "hold my beer I am a toolkit not a functioning API surely it's just for testing and you'd never send nasty bytes" kind of way. Sadly some callers seem to use them to fetch things liks subject name components for comparisons, and often just use the result as a C string. Instead, encode the resulting bytes as UTF-8 so it is something like "text", Add a failure case if the length provided is inadequate or if the resulting text would contain an nul byte. based on boringssl. nits by dlg@ ok tb@
* Remove references to openssl/obj_mac.hjsing2022-07-021-6/+5
| | | | Consumers should include openssl/objects.h instead.
* Improve pages that briefly mentioned ERR - usually below SEE ALSO -schwarze2019-06-141-25/+25
| | | | | but failed to provide any real information. OK tb@ jmc@
* Tree structure for manual pages: crypto(3) links to 33 functionschwarze2019-06-061-2/+3
| | | | | | | | | | | 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@
* sync with const changes in x509.h r1.68.tb2018-07-091-4/+4
|
* In x509.h rev. 1.56 2018/05/18 18:05:57 to rev. 1.58 2018/05/18 18:16:39,schwarze2018-05-191-6/+6
| | | | | tb@ added const qualifiers to some arguments of X509_NAME read accessors. Adjust the manual.
* found a complete archive of SSLeay-0.4 to SSLeay-0.8.1b tarballsschwarze2018-03-271-3/+4
| | | | on the web, so fix up SSLeay HISTORY accordingly
* x509.h HISTORY up to SSLeay 0.8.1b; researched from OpenSSL gitschwarze2018-03-211-2/+5
|
* Consistently mark up various ASN.1 type names defined in standardsschwarze2016-12-251-5/+8
| | | | related to X.509 with .Vt such that they can be searched for.
* Make sure all manual pages discussing X509_NAME objectsschwarze2016-12-141-3/+4
| | | | | reference X509_NAME_new(3). Sparingly add a few other references to relevant X509_NAME*(3) pages while here.
* Add Copyright and license.schwarze2016-12-051-4/+72
| | | | | More explanations about X509_NAME_get_index_by_NID(3) from OpenSSL. Merge a typo fix in EXAMPLES from OpenSSL.
* various cleanup;jmc2016-12-031-5/+5
|
* first pass; ok schwarzejmc2016-11-061-1/+3
|
* convert X509 manuals from pod to mdocschwarze2016-11-041-0/+177
generated by cgit v1.2.3-55-g6feb (git 2.39.1) at 2025-08-27 20:09:59 +0000