summaryrefslogtreecommitdiff
path: root/src/lib/libc/stdlib/exit.c (unfollow)
Commit message (Collapse)AuthorFilesLines
2017-01-04Complete rewrite:schwarze1-58/+72
Better one-line description. Specify the correct header file. Same parameter names as in ASN1_item_d2i(3). Lots of new information. The ASN1_OBJECT interfaces appear specifically designed to maximize the number and subtlety of traps, maybe in order to trap the wary along with the unwary. All the quirks, caveats, and bugs of ASN1_item_d2i(3) apply, and there are three additional ones on top in this page. It looks like that design approach was so successful that the designers managed to trap even themselves: see the new BUGS section.
2017-01-04Describe what ASN1_OBJECT_new(3), ASN1_OBJECT_free(3), OBJ_dup(3),schwarze2-34/+105
and OBJ_create(3) really do rather than making broad and incomplete statements that are only true in some cases. Improve the one-line descriptions. Some minor wording improvements while here. There is obviously more work to do in the vicinity...
2017-01-03Document d2i_ASN1_TYPE(3) and i2d_ASN1_TYPE(3),schwarze1-9/+46
both listed in <openssl/asn1.h> and in OpenSSL doc/man3/d2i_X509.pod. Minor wording improvements while here.
2017-01-03consistently spell ASN.1;jmc1-12/+12
2017-01-03Document ASN1_TYPE_new(3) and ASN1_TYPE_free(3), even though OpenSSLschwarze2-34/+106
does not document them. By being in <openssl/asn1.h>, they are public, and it makes no sense to document accessors but not document constructors and destructors. Improve the one-line description. Mention various missing details. Many wording improvements. Add some cross references.
2017-01-03If certificate verification has been disabled, do not attempt to load ajsing1-5/+9
CA chain or specify CA paths. This prevents attempts to access the file system, which may fail due to pledge. ok bluhm@
2017-01-03Revert previous - the original code was correct since X509_verify_cert()jsing1-5/+5
should not have changed the X509_STORE_CTX error value on success and it was initialised to X509_V_OK by X509_STORE_CTX_init(). Other software also depends on this behaviour. Previously X509_verify_cert() was mishandling the X509_STORE_CTX error value when validating alternate chains. This has been fixed and further changes now explicitly ensure that the error value will be set to X509_V_OK if X509_verify_cert() returns success.
2017-01-03Add regress tests for max shared version code.jsing1-2/+133
2017-01-03Pull out, rework and dedup the code that determines the highest sharedjsing4-79/+62
version. ok beck@ doug@
2017-01-03It takes a special style of creative writing to be unspecific about the errorbeck1-15/+5
return code of a function in a man page. Let's remove the ambiguity and half truths in here. ok jsing@
2017-01-03Add a small bit of belt and suspenders around ERR_V_OK with X509_STORE_ctxbeck1-2/+20
and X509_verify_cert - We at least make it so an an init'ed ctx is not "valid" until X509_verify_cert has actually been called, And we make it impossible to return success without having the error set to ERR_V_OK. ok jsing@
2017-01-03bring in boring's internal check_trust function to fix a bug introducedbeck1-24/+79
when we went to alternate cert chains. this correctly does not clobber the ctx->error when using an alt chain. ok jsing@
2017-01-02fix cert verify. a cert with an alt chain may verify but leave an errortedu1-5/+5
in the context. don't look for errors in case of success. fixes spurious verify errors. guilty change tracked and fix tested by sthen
2017-01-01Various work on cert.pem, ok bcook@sthen1-969/+869
- print/sort using the full certificate subject rather than a pretty-printed subset (as done in the current version of format-pem.pl); previously this was resulting in a problem where a CN conflict resulted in the GlobalSign R2 CA accidentally getting dropped in r1.10; problem found by Steven McDonald - remove CA certificates that are no longer present in the CA store of the release branch of Mozilla - possible now that libressl has support for alternate chains (libcrypto/x509/x509_vfy.c r1.52) - add new CA certificates from Mozilla's store from those organisations which we already list
2016-12-30Display details of the server ephemeral key, based on OpenSSL.jsing3-3/+44
ok doug@
2016-12-30Add support for SSL_get_server_tmp_key().jsing2-3/+74
ok doug@
2016-12-30Add regress coverage for enabled protocol version range.jsing2-1/+146
2016-12-30Pull out (and largely rewrite) the code that determines the enabledjsing3-40/+54
protocol version range. This also fixes a bug whereby if all protocols were disabled, the client would still use TLSv1.2 in the client hello, only to have if fail with unsupported version when it received and processed the server hello. ok doug@
2016-12-30Place ASN_ITEM_{ptr,rptr,ref} and DECLARE_ASN1_ITEM under #ifndefjsing1-2/+4
LIBRESSL_INTERNAL.
2016-12-30Expand ASN1_ITEM_rptr macros here as well... used with NETSCAPE_X509 of alljsing2-4/+4
things...
2016-12-30Expand ASN1_ITEM_rptr macros - no change in preprocessor output.jsing2-9/+9
2016-12-30Expand ASN1_ITEM_rptr and ASN1_ITEM_ptr macros - no change in generatedjsing9-33/+33
assembly.
2016-12-30Stop using M_PKCS12_* compatibility macros here as well.jsing1-3/+3
2016-12-30Expand ASN1_ITEM_ref and ASN1_ITEM_ptr macros - no change in generatedjsing22-66/+66
assembly. Of particular interest is ASN1_ITEM_ptr which does nothing and resulted in code like: if (method->it) ASN1_ITEM_free(..., ASN1_ITEM_ptr(method->it));
2016-12-30Expand ASN1_ITEM_rptr macros - no change in generated assembly.jsing2-6/+6
2016-12-30Expand ASN1_ITEM_rptr macros - no change in generated assembly.jsing10-37/+37
2016-12-30Expand ASN1_ITEM_rptr macro - no change in generated assembly.jsing2-4/+4
2016-12-30Expand ASN1_ITEM_rptr macros - no change in generated assembly.jsing2-55/+55
2016-12-30Remove now unused c2l, c2ln, l2c, n2l, l2cn and n2l3 macros.jsing2-53/+2
2016-12-30Explicitly include openssl/opensslconf.h in headers that use OPENSSL_NO_*jsing2-2/+4
defines - do not rely on another heading making those available for us.
2016-12-30Place M_PKCS12_* compatibility macros under #ifndef LIBRESSL_INTERNAL.jsing1-1/+5
2016-12-30Expand M_PKCS12_* "compatibility" macros. No change to generated assembly.jsing3-10/+10
2016-12-29Write d2i_ASN1_NULL(3) manual page from scratch.schwarze2-1/+86
Both functions are listed in <openssl/asn1.h> and in OpenSSL doc/man3/d2i_X509.pod. After reading the code, i'm not amused. You wouldn't think that it might take eight stack levels to decode a constant sixteen bit value that does not even allow a single content octet, or would you? Nota bene, this is an average of four stack levels for each non-zero bit decoded... :-(
2016-12-29fix typo; from OpenSSLschwarze1-4/+4
commit 67adf0a7c273a82901ce8705ae8d71ee2f1c959c Author: Markus Triska <triska@metalevel.at> Date: Sun Dec 25 19:58:38 2016 +0100
2016-12-28Write documentation for <openssl/x509v3.h> DER decoding andschwarze9-8/+861
encoding functions from scratch. All 46 functions are listed in OpenSSL doc/man3/d2i_X509.pod.
2016-12-28add missing .Vt macrosschwarze2-8/+15
2016-12-28standard section name;jmc1-3/+3
2016-12-28Rewrite and add d2i_X509_REQ_INFO(3) and i2d_X509_REQ_INFO(3),schwarze1-66/+99
both listed in <openssl/x509.h> and in OpenSSL doc/man3/d2i_X509.pod.
2016-12-28Rewrite and add d2i_X509_CRL_INFO(3), i2d_X509_CRL_INFO(3),schwarze1-67/+94
d2i_X509_REVOKED(3), and i2d_X509_CRL_INFO(3), all listed in <openssl/x509.h> and in OpenSSL doc/man3/d2i_X509.pod.
2016-12-28Use the same parameter names as in ASN1_item_d2i(3).schwarze1-53/+32
Use simpler standard wordings. Add X.509 references.
2016-12-28rewrite in the standard wayschwarze1-60/+29
2016-12-28Minor cleanup:schwarze1-17/+19
Improve the one-line description. Use the standard wordings in some places. Complete the RETURN VALUES section.
2016-12-28Write new manual pages d2i_X509_ATTRIBUTE(3) and d2i_X509_EXTENSION(3)schwarze6-7/+176
from scratch. All six functions are listed in <openssl/x509.h> and in OpenSSL doc/man3/d2i_X509.pod.
2016-12-28In contrast to OpenSSL, do not attempt to document the worldschwarze1-5/+98
in this page - but do include documentation for immediate subobjects that are used nowhere else. All six functions listed in <openssl/x509.h> and in OpenSSL doc/man3/d2i_X509.pod.
2016-12-28Basic cleanup:schwarze1-311/+60
Improve .Nd. Sort functions. Use the same parameter names as in ASN1_item_d2i(3). Point to ASN1_item_d2i(3) for all he details. Delete all the information that's now in ASN1_item_d2i(3). Add missing entries to the RETURN VALUES section. Add STANDARDS section.
2016-12-28Full rewrite.schwarze1-60/+123
Also document d2i_PKCS8_bio(3), i2d_PKCS8_bio(3), d2i_PKCS8_fp(3), and i2d_PKCS8_fp(3) while here, listed in <openssl/x509.h> and in OpenSSL doc/man3/d2i_X509.pod. No, these functions have nothing to do with the many other d2i_PKCS8*(3) functions all around, and nothing with PKCS#8 at all in the first place. Read the BUGS section. I couldn't make this stuff up.
2016-12-28Add a dire warning to not confuse i2d_PKCS8PrivateKey_bio(3)schwarze1-4/+12
with i2d_PKCS8PrivateKeyInfo_bio(3). While here, polish the cross references.
2016-12-28Document i2d_PKCS8PrivateKeyInfo_bio(3) and i2d_PKCS8PrivateKeyInfo_fp(3),schwarze1-6/+41
listed in <openssl/x509.h> and in OpenSSL doc/man3/d2i_X509.pod. These functions are very similar to i2d_PrivateKey(3) but very different from i2d_PKCS8PrivateKey_bio(3), that's why they go into this manual page and not into the other one. When the naming was decided, somebody clearly considered too briefly or too long.
2016-12-28Write new manual page d2i_PKCS8_PRIV_KEY_INFO(3) from scratch.schwarze2-1/+116
These six function are listed in <openssl/x509.h> and in OpenSSL doc/man3/d2i_X509.pod.
2016-12-27Write new manual pages d2i_OCSP_REQUEST(3) and d2i_OCSP_RESPONSE(3)schwarze3-1/+423
from scratch. All these functions are listed in <openssl/ocsp.h> and in OpenSSL doc/man3/d2i_X509.pod.
generated by cgit v1.2.3-55-g6feb (git 2.39.1) at 2025-04-27 22:40:12 +0000