summaryrefslogtreecommitdiff
path: root/src/lib/libc/stdlib/malloc.c (unfollow)
Commit message (Collapse)AuthorFilesLines
2016-02-12word fix from previous; ok sthenjmc1-3/+3
2016-02-08sslv3 has been removed;jmc1-16/+21
prompted by a mail from jiri navratil help/ok sthen
2016-02-07compare pointer to NULL in example codemmcc1-3/+3
2016-02-05be more forceful about not using these.espie1-2/+9
improvements sthen@, jmc@. okay millert@, jca@ jmc@
2016-02-05Fix err(3) calls after allocation failures in examples.schwarze1-8/+8
There is long-standing consensus that err(1, NULL) is the best idiom after failure of malloc(3) and friends. Quirk in the manual noticed by tb@.
2016-02-01Sort cert.pem alphabetically, first by organisation, then by CA namesthen1-1604/+1584
(CN if available, otherwise OU). Add a comment identifying the org. Now to get an easy-to-read list of certificates in the file you can use "grep ^[#=] cert.pem". Prepared with https://spacehopper.org/format-pem.20160201. If you would like to verify this commit to ensure that I didn't sneak in any other changes, it will be easier to use the script rather than do it by hand.
2016-01-31Revamp cert.pem certificate information formatting. Skip headers whichsthen1-2459/+184
aren't really useful (the information can be obtained by feeding the cert into "openssl x509 -in filename -text") and add a separator between certs showing the CA's CN or OU (similar to the display format in web browsers). Include both SHA1 and SHA256 fingerprints for all certificates. ok beck@ zhuk@ jung@
2016-01-29Therefor -> Therefore (where appropriate)tb2-2/+2
from ray@, ok jmc@
2016-01-27deprecate SSL_OP_SINGLE_DH_USElibressl-v2.3.2beck4-74/+12
ok jsing@
2016-01-26Don't crash dumping malloc stats if malloc_init hasn't been called, noted byotto1-1/+3
David CARLIER
2016-01-18Call BIO_sock_init() from tls_init() to ensure sockets are enabled on Windows.bcook1-1/+4
This is of course a no-op on other platforms. Noted by equalsraf from github.
2016-01-06Long ago, malloc internally had two kinds of failures, warnings and errors.tedu2-14/+7
The 'A' option elevated warnings to errors, and has been the default for some time. Then warnings were effectively eliminated in favor of everything being an error, but then the 'a' flag turned real errors into warnings! Remove the 'a' option entirely. You shouldn't have used it anyway. ok tb tdeval
2016-01-04Follow style(9) and drop lint /* NOTREACHED */ annotations fromtb2-6/+4
the examples. Diff from Juuso Lapinlampi < wub () partyvan ! eu >, thanks! ok schwarze@
2016-01-04Use the correct values for TLS certificate / private key flags.bcook1-5/+5
fix from Andreas Bartelt <obsd at bartula.de>
2016-01-04Calling clone(2) with CLONE_NEWPID yields multiple processes with pid=1.bcook2-4/+6
Work around this particular case by reseeding whenever pid=1, but as guenther@ notes, directly calling clone(2), and then forking to match another pid, provides other ways to bypass new process detection on Linux. Hopefully at some point Linux implements something like MAP_INHERIT_ZERO, and does not invent a corresponding mechanism to subvert it. Noted by Sebastian Krahmer and the opmsg team. See http://stealth.openwall.net/crypto/randup.c for a test program. ok beck@
2015-12-30Document that the ssl free() functions are NULL safe. OK mmcc@millert6-12/+42
2015-12-30another case where bad things would happen after wrterrortedu1-2/+4
2015-12-30if somebody makes the mistake of disabling abort, don't deref null intedu1-2/+4
validate_junk. from Michal Mazurek
2015-12-28Remove NULL-checks before free() and a few related dead assignments.mmcc2-8/+5
ok and valuable input from millert@
2015-12-28initialize pointer to avoid undefined free on failurebcook1-2/+2
ok beck@
2015-12-28include time.h over sys/time.h for ctime(3)bcook1-2/+2
ok beck@
2015-12-27remove unused variablechl1-2/+1
ok tedu@
2015-12-24more e-mail -> emailmmcc2-5/+5
2015-12-24More adress -> addressmmcc4-4/+4
2015-12-23remove NULL-check before free()mmcc1-3/+2
2015-12-23remove NULL-checks before free()mmcc6-38/+22
2015-12-23assign pointer NULL rather than 0mmcc2-4/+4
2015-12-23assign pointer to NULL rather than 0mmcc2-4/+4
2015-12-22initialize a pointer to NULL rather than 0mmcc2-4/+4
2015-12-19gethostbyname2() and gethostbyaddr() need <sys/socket.h>; discussed withtim1-6/+8
millert@
2015-12-18Simplify return call of rand() and rand_r() to make it easier to read.tb1-2/+2
This is slightly less robust, but RAND_MAX must be one below a power of two in both variants anyway. Based on a suggestion by Matthew Martin. ok tedu@
2015-12-17Add missing colon after "Peer name" in verbose output. Mentioned on themmcc1-2/+2
lists recently.
2015-12-16tweak previous;jmc2-4/+5
2015-12-16Remove support for HOSTALIASES from the resolver. This "open and parsederaadt2-15/+6
any file indicated by an environment variable" feature inside the resolver is incompatible with what pledge "dns" is trying to be. It is a misguided "feature" added way back in history which almost noone uses, but everyone has to assume the risk from. ok eric florian kettenis
2015-12-16clean up some unused variables, and add the printing of the certificate validitybeck1-4/+7
to the verbose output when using tls - from rob@2keys.ca ok mmcc@ jsing@ deraadt@
2015-12-15Remove "C=US, O=VeriSign, Inc., OU=Class 3 Public Primary Certificationsthen1-49/+0
Authority" (serial 3c:91:31:cb:1f:f6:d0:1b:0e:9a:b8:d0:44:bf:12:be) root certificate from cert.pem. ok rpe@ Symantec/VeriSign say "Browsers/root store operators are encouraged to remove/untrust this root from their root stores" and "hasn't been used to generate new certificates in several years, and will now be repurposed to provide transition support for some of our enterprise customers' legacy, non-public applications" (https://www.symantec.com/page.jsp?id=roots, http://www.scmagazine.com/google-will-remove-trust-of-symantecs-pca3-g1-certificate/article/459688/). Also see https://knowledge.symantec.com/support/ssl-certificates-support/index?page=content&id=ALERT1941 https://googleonlinesecurity.blogspot.co.uk/2015/12/proactive-measures-in-digital.html
2015-12-14initialize ext_len to 0.beck2-4/+12
ok guenther@
2015-12-14initialize ok to 0beck2-4/+4
ok guenther@
2015-12-14initialize md_len to 0 for readability to quell warnings.beck2-6/+6
ok guenther@
2015-12-14s/begining/beginning/gmmcc1-2/+2
2015-12-12decipher comment. ok bcook@mmcc2-4/+4
2015-12-12move initialization of buf up to quell warnings and make it obvious the err ↵beck2-8/+10
case is ok. ok bcook@
2015-12-12prevent possibly use of uninitialized variablebeck2-4/+4
ok bcook@
2015-12-12make the counter a size_t as well, which quells a warning on visual studio 2015beck2-4/+6
ok bcook@
2015-12-10Specify SOCKS version in error messages. ok deraadt@mmcc1-3/+3
2015-12-10tiny sanity check on file sizetedu1-1/+3
2015-12-10Map SOCKS error codes to error strings. With input from deraadt@mmcc1-5/+61
2015-12-09bump the major for libcrypto/ssl/tls for a CRYPTO_chacha_20 ABI changebcook5-10/+10
ok jsing@, deraadt@, beck@
2015-12-09Change the counter argument for CRYPTO_chacha_20 to be 64-bits on all platforms.bcook4-10/+12
The recently-added EVP_aead_chacha20_poly1305_ietf() function, which implements informational RFC 7539, "ChaCha20 and Poly1305 for IETF Protocols", needs a 64-bit counter to avoid truncation on 32-bit platforms. The existing TLS ChaCha20-Poly1305 ciphersuite is not impacted by this, but making this change requires an ABI bump. ok jsing@, "Looks sane" beck@
2015-12-09Integrate two patches originally from Daniel Micay.tedu1-8/+76
1. Optionally add random "canaries" to the end of an allocation. This requires increasing the internal size of the allocation slightly, which probably results in a large effective increase with current power of two sizing. Therefore, this option is only enabled via 'C'. 2. When writing junk (0xdf) to freed chunks (current default behavior), check that the junk is still intact when finally freeing the delayed chunk to catch some potential use after free. This should be pretty cheap so there's no option to control it separately. ok deraadt tb
generated by cgit v1.2.3-55-g6feb (git 2.39.1) at 2025-05-02 12:38:50 +0000