summaryrefslogtreecommitdiff
path: root/src/lib/libc/stdlib/strtoul.c (unfollow)
Commit message (Collapse)AuthorFilesLines
2019-01-18tweak previous;jmc1-7/+7
2019-01-18Expose some symbols in a new tls13_handshake.h for regression testing.tb3-99/+93
Update the handshake state tables and flag names according to the design decisions and naming conventions in the hackroom. Garbage collect some things that turn out not to belong here. ok jsing
2019-01-18Removed unused struct members.jsing1-2/+0
2019-01-18Add the -iter and -pbkdf2 argumenst to encbeck1-2/+11
2019-01-18Change the default digest type to sha256, and add support forbeck1-5/+44
pbkdf2 with OpenSSL compatible flags ok jsing@
2019-01-18Remove this copy, we have decided we can do this in placebeck3-1633/+2
ok jsing@
2019-01-18Add support for RFC 8446 section 4.2 enforcing which extensions maybeck1-8/+43
appear with which messages. ok jsing@
2019-01-18Update regress following TLS extension renaming.jsing2-379/+378
2019-01-18Rename TLS extension handling to use less "hello".jsing4-220/+228
When the TLS extension code was rewritten, TLS extensions could only exist in ClientHello and ServerHello messages - as such, they were named in pairs of *_clienthello_{needs,build} which would be called by the client and *_clienthello_parse. Likewise for *_serverhello_{needs,build} which would be called by a server and *_serverhello_parse, which would be called by a client. Enter TLSv1.3 - TLS extensions can now exist in one of seven messages, with only certain types being allowed to appear in each, meaning the naming scheme no longer works. Instead, rename them to indicate the caller rather than the message type - this effectively means: clienthello_needs -> client_needs clienthello_build -> client_build clienthello_parse -> server_parse serverhello_needs -> server_needs serverhello_build -> server_build serverhello_parse -> client_parse ok beck@ tb@
2019-01-17Add regress for extensible buffer code.jsing3-1/+169
2019-01-17Get rid of is_serverhello in preparation for other messagesbeck1-13/+24
ok jsing@ tb@
2019-01-17Provide an extensible buffer implementation that uses a read callback.jsing3-3/+148
The read callback returns a TLS13_IO_* value on EOF, failure, want pollin or want pollout, or a positive value indicating the number of bytes read. This will be used by upcoming TLSv1.3 handshake message and record processing code, both of which need the ability to read a fixed size header, before extending the buffer to the number of bytes specified in the header. ok beck@ tb@
2019-01-17Add support to enforce restrictions on where extensions can appearbeck2-12/+38
as per RFC8446 section 4.2. Recognized extensions that appear in an incorrect message must abort the handshake. ok jsing@
2019-01-17Add a direct copy of the exension parsing code to be modified for tls13.beck3-2/+1596
At the moment this is mechanical, with the functions renamed. This will be refactored for tls13. ok jsing@
2019-01-16For all functions known to be infected by LC_NUMERIC, add shortschwarze2-4/+22
CAVEATS pointing to the new CAVEATS section in setlocale(3). Make those in wprintf(3) and wscanf(3) more concise since duplicate information is a bad idea. Incompleteness of information originally pointed out by millert@. OK millert@
2019-01-14There are cases where a program doing dns requests wants to set theotto1-2/+4
Checking Disabled flag. Introduce a RES flag to do so. ok krw@ deraadt@ eric@
2019-01-10Move default numer of pools in the multi-threaded case to 8. Various testsotto1-2/+2
by me and others indicate that it is the optimum.
2019-01-10Make the "not my pool" searching loop a tiny bit smarter, whileotto2-22/+39
making the number of pools variable. Do not document the malloc conf settings atm, don't know yet if they will stay. Thanks to all the testers. ok deraadt@
2019-01-10Revert back previous commit and stop including strings.hmestre2-9/+7
Use memset(3) instead of bzero(3) since POSIX recommends using the former and because it's also more portable (conforms to ANSI C standard) OK tedu@ tb@
2019-01-09Include strings.h for bzero in usr.bin/ncinoguchi2-2/+4
bzero is defined in strings.h. ok deraadt@
2019-01-02correct article;jmc2-6/+6
2018-12-27too many words in previous;jmc1-2/+2
2018-12-27port ranges can be ambiguous with hypenated port-names.tedu2-6/+7
specify that ranges must be numeric, and only check for range if first argument is a digit. identified by danj, fix suggest by sthen
2018-12-26Make AES CCM available in tables.tb1-1/+4
Omission reported by reyk and Alice Wonder. ok bcook jsing
2018-12-24Make this page much more readable by deleting as much text as possibleschwarze1-28/+9
about functions that are deprecated, identical to other functions, and never made sense in the first place. As deraadt@ points out, we should not hide the information that matters in a heap of clutter. It would waste reader's time and make confusion and accidental misuse more likely. OK deraadt@ jmc@
2018-12-23EVP_MD_CTX_cleanup() is deprecated and doesn't free, so recommend usingtb4-12/+12
EVP_MD_CTX_free() instead if the goal is to avoid leaking memory. From my corresponding upstream commit, reminded by schwarze
2018-12-22Document EVP_PKEY_new_mac_key(3);schwarze1-8/+50
from Matt Caswell <matt at openssl dot org> via OpenSSL commit d45a97f4 Mar 5 17:41:49 2018 +0000.
2018-12-22Delete irrelevant HISTORY details. Simply use BN_rand(3); thereschwarze1-12/+2
is no need to know at which time BN_pseudo_rand(3) was made the same as BN_rand(3). Considering that question might even mislead people to attempt ill-advised #ifdef'ing. Pointed out by deraadt@.
2018-12-21The wrong header file was given for EVP_PKEY_CTX_set_signature_md(3).schwarze1-13/+69
Also clarify to which algorithms it applies. From Matt Caswell <matt at openssl dot org> via OpenSSL commit d45a97f4 Mar 5 17:41:49 2018 +0000. Document EVP_PKEY_CTX_get_rsa_padding(3), EVP_PKEY_CTX_get_rsa_pss_saltlen(3), EVP_PKEY_CTX_set_rsa_mgf1_md(3), and EVP_PKEY_CTX_get_rsa_mgf1_md(3). From Antoine Salon <asalon at vmware dot com> via OpenSSL commit 87103969 Oct 1 14:11:57 2018 -0700 from the OpenSSL_1_1_1-stable branch, which is still under a free license.
2018-12-21Document the ECDSA_SIG_new(3) return value.schwarze1-2/+10
Inspired by OpenSSL commit 6da34cfb Jun 2 16:17:32 2018 -0400 by Ken Goldman <kgoldman at us dot ibm dot com>, but use the same wording as in ASN1_item_new(3) instead.
2018-12-21Clarify behaviour of DH_get0_pqg(3) and DH_get0_key(3) with NULL arguments;schwarze1-4/+19
from <Matthias dot St dot Pierre at ncp dash e dot com> via OpenSSL commit 5777254b May 27 09:07:07 2018 +0200.
2018-12-21grammar and style fixes from wesinator at githubschwarze1-13/+14
via OpenSSL commit 521738e9 Oct 5 14:58:30 2018 -0400
2018-12-21Since OpenBSD 6.1, BN_pseudo_rand*(3) does the same as BN_rand*(3).schwarze1-10/+18
Say so, and note that OpenSSL followed suit in 1.1.0 according to OpenSSL commit 5ecff87d Jun 21 13:55:02 2017 +0100.
2018-12-21Mention that some functions call BN_GENCB_call(3) with a secondschwarze1-4/+15
argument of 3; from Beat Bolli <dev at drbeat dot li> via OpenSSL commit bd93f1ac Jul 28 16:45:22 2018 -0400.
2018-12-19Correctly describe the return values of BN_hex2bn(3) and BN_dec2bn(3).schwarze1-5/+8
Inspired by OpenSSL commit a130950d Aug 23 12:06:41 2017 -0400 by Rich Salz <rsalz at openssl dot org>, but using a more explicit wording, and fixing *both* places rather than only half of them.
2018-12-19Specify the return values of some of these functions more precisely;schwarze1-15/+16
inspired by OpenSSL commit 1f13ad31 Dec 25 17:50:39 2017 +0800 by Paul Yang <yang sot yang at baishancloud dot com>, but without creating a RETURN VALUES section because that makes no sense here: it would either result in a confusing order of information or in duplicate information.
2018-12-19typo;schwarze1-4/+5
from Jakub Wilk <jwilk at jwilk dot net> via OpenSSL commit a21285b3 Aug 21 18:30:34 2018 +0200
2018-12-16Add regress test for bugs in stdio/fread.c rev 1.13 and 1.17millert3-2/+160
2018-12-16Regenerate root CA list using updated format-pem.pl. Specifically thissthen1-101/+1
drops CA certificates whose validity dates don't comply with the rules on ASN.1 encoding in RFC 5280 (and predecessors - same rule goes back to at least RFC 2459, section 4.1.2.5). LibreSSL strictly enforces this, so attempting to validate certificates signed by these CAs just result in the following: error 13 at 1 depth lookup:format error in certificate's notBefore field "probably" beck@
2018-12-16Add a check that libressl is actually able to verify CA certs.sthen1-12/+28
Skip outputting them if invalid (e.g. GENERALIZEDTIME date before 2050).
2018-12-15add a -R option to set/unset resolver flags.libressl-v2.9.0eric9-20/+101
use strcasecmp for reading args.
2018-12-14Delete a note taken during the rev. 1.1 man page spliteschwarze1-5/+2
that should have been deleted before commit. The cross reference is already present below SEE ALSO. Glitch noticed by jsing@.
2018-12-10Improve speed for the multi-threaded case by reducing lock contention.otto1-30/+21
tested by many; ok florian@
2018-12-09Keep usage in sync with logic if OPENSSL_NO_DES is set.tobias1-1/+3
ok jmc@, jsing@
2018-12-09style; OK ottoflorian1-3/+3
2018-12-07Remove an ugly hack in the client certificate verification code that workstb1-48/+44
around broken GOST implementations. It looks like client certificates with GOST have been completely broken since reimport of the GOST code, so no-one is using LibreSSL this way. The client side was fixed only last week for TLSv1.0 and TLSv1.1. This workaround is now in the way of much needed simplifcation and cleanup, so it is time for it to go. suggested by and ok jsing
2018-12-05remove a stray line accidentally left behind in rev. 1.120;schwarze1-3/+2
patch from Hiltjo Posthuma <hiltjo at codemadness dot org>
2018-12-03Send SSL_AD_DECODE alerts in the case of a bad hello request or antb1-7/+7
invalid change cipher spec. Found due to dead assignment warnings by the Clang static analyzer. ok inoguchi (previous version), jsing
2018-11-30Restore function prototype for ASN1_dup, fixing usage on I32LP64 platforms.jeremy1-1/+7
This prototype was removed inadvertantly in r1.50. OK jsing@
2018-11-29This test does not terminate if malloc conf is preconfigured withbluhm1-2/+6
J. Clear that option to allow running full regress with paranoid malloc flags. This is the same fix as for malloc_ulimit1.
generated by cgit v1.2.3-55-g6feb (git 2.39.1) at 2025-04-27 06:16:44 +0000