summaryrefslogtreecommitdiff
path: root/src/lib/libc/string/wcscpy.c (unfollow)
Commit message (Collapse)AuthorFilesLines
2016-05-10Oops: the caching of TCB address in single-threaded processes on archs withguenther1-2/+2
slow TCB_GET (alpha, arm, mips64, sh) was broken when I switched CPP symbols.
2016-05-09Fix mangled function signatures.jsing1-5/+5
From Carlin Bingham <cb at viennan dot net>, thanks!
2016-05-07Use a Thread Information Block in both single and multi-threaded programs.guenther3-135/+252
This stores errno, the cancelation flags, and related bits for each thread and is allocated by ld.so or libc.a. This is an ABI break from 5.9-stable! Make libpthread dlopen'able by moving the cancelation wrappers into libc and doing locking and fork/errno handling via callbacks that libpthread registers when it first initializes. 'errno' *must* be declared via <errno.h> now! Clean up libpthread's symbol exports like libc. On powerpc, offset the TIB/TCB/TLS data from the register per the ELF spec. Testing by various, particularly sthen@ and patrick@ ok kettenis@
2016-05-04fix for integer overflow in encode and encrypt update functions.tedu4-12/+22
additionally, in EncodeUpdate, if the amount written would overflow, return 0 instead to prevent bugs in the caller. CVE-2016-2105 and CVE-2016-2106 from openssl.
2016-05-04fix a padding oracle in aesni cbc mac check. there must be enough datatedu2-2/+8
for both the mac and padding bytes. CVE-2016-2107 from openssl
2016-05-04internal only negative types should not be handled here.tedu6-18/+6
CVE-2016-2108 from openssl.
2016-05-04be careful about consuming excessive memory by reading in chunks.tedu2-28/+74
CVE-2016-2109 from openssl.
2016-05-04revert the big change from yesterday to prepare for smaller commits.tedu14-110/+60
2016-05-03prefer limits.h over sys/limits.hbcook2-4/+4
2016-05-03patch from openssl for multiple issues:tedu16-60/+530
missing padding check in aesni functions overflow in evp encode functions use of invalid negative asn.1 types ok beck
2016-05-02Remove a vax remnant (that was really a no-op anyway).millert1-3/+1
2016-05-01Remove old NeXT-specific cruft. From mmcc@millert1-13/+1
2016-04-28spelling fix;jmc1-2/+2
2016-04-28Crank majors for lib{crypto,ssl,tls} due to symbol removals, symboljsing5-5/+5
additions and functionality changes.
2016-04-28Factor our the keypair handling in libtls. This results in more readablejsing7-52/+164
and self-contained code, while preparing for the ability to handle multiple keypairs. Also provide two additional functions that allow a public certificate and private key to be set with a single function call. ok beck@
2016-04-28Rework the error handling in libtls so that we can associate errors withjsing5-28/+90
both configuration and contexts. This allows us to propagate errors that occur during configuration, rather than either just failing with no reason or delaying the failure until it can be propagated via the tls context. Also provide a tls_config_error() function for retrieving the last error from a tls_config *. ok bcook@
2016-04-28don't go into an unbreakable infinite loop during operations suchtedu2-2/+4
as reading passwords. allow ^C to break. the pain was mine, the fix is miod's.
2016-04-28Update regress test to reflect changes in the cipher list.jsing1-61/+62
2016-04-28Implement the IETF ChaCha20-Poly1305 cipher suites.jsing10-92/+336
Rename the existing ChaCha20-Poly1305 cipher suites with an "-OLD" suffix, effectively replaces the original Google implementation. We continue to support both the IETF and Google versions, however the existing names now refer to the ciphers from draft-ietf-tls-chacha20-poly1305-04. Feedback from doug@
2016-04-28Update AEAD regress to match EVP_aead_chacha20_poly1305() changes.jsing2-83/+83
2016-04-28Rename EVP_aead_chacha20_poly1305() to EVP_aead_chacha20_poly1305_old()jsing6-30/+30
and replace with EVP_aead_chacha20_poly1305_ietf(). The IETF version will become the standard version. Discussed with many.
2016-04-26add "dns" to openssl ocspsemarie1-2/+2
problem reported by Alexandre (kAworu) ok beck@ deraadt@ sthen@
2016-04-25Allow setenv(3) and putenv(3) to operate on a NULL environ pointer.millert1-11/+15
The getenv(3) and unsetenv(3) functions already support this. This will make it easier to emulate the glibc clearenv() function in ports. Based on a diff from and OK jca@
2016-04-24no more outlen; from remcojmc1-5/+3
ok bcook deraadt
2016-04-24typos;jmc1-3/+3
2016-04-19fix typo in comment; ok becktj2-4/+4
2016-04-13Use the correct iv and counter when decrypting the ciphertext forjsing2-8/+8
EVP_aead_chacha20_poly1305_ietf().
2016-04-13After opening an AEAD, ensure that the decrypted output matches thejsing1-0/+5
plaintext for the regress test case.
2016-04-12two times a define to an inline function, from Michael McConville; ok djm@otto1-10/+19
2016-04-09tweak MALLOC_STATS printing (switched off by default), prodded byotto1-14/+14
Michael McConville
2016-04-09redundant memset(3), from Michael McConville, ok armani@otto1-2/+1
2016-04-07hexidecimal->hexadecimal; from mmccjmc1-4/+4
ok beck
2016-04-05Prefer _MUTEX_*LOCK over _THREAD_PRIVATE_MUTEX_*LOCK() when thread-specificguenther2-8/+8
data isn't necessary. ok mpi@, ok&tweak natano@
2016-04-05Update example in comment: setlogin doesn't use {PROTO,DEF}_WRAP() nowguenther1-8/+8
2016-04-03Document ``use after free'' error messageotto1-2/+4
2016-03-30for some time now mandoc has not required MLINKS to functionjmc7-1233/+7
correctly - logically complete that now by removing MLINKS from base; authors need only to ensure there is an entry in NAME for any function/ util being added. MLINKS will still work, and remain for perl to ease upgrades; ok nicm (curses) bcook (ssl) ok schwarze, who provided a lot of feedback and assistance ok tb natano jung
2016-03-27Merge a memleak fix from BoringSSL 6b6e0b2:mmcc2-2/+6
https://boringssl.googlesource.com/boringssl/+/6b6e0b20893e2be0e68af605a60ffa2cbb0ffa64%5E!/#F0 ok millert@, beck@
2016-03-26fix the last bunch of NAME sections that were overlooked earlierschwarze1-2/+9
such that the MLINKS removal can be committed after this; OK jmc@
2016-03-21Return zero from two functions on allocation failure instead of alwaysmmcc4-8/+8
returning one (indicating success). Each function has only a single usage, and both usages check the return value. Merged from BoringSSL 0ce78a757d815c0dde9ed5884229f3a5b2cb3e9c: https://boringssl.googlesource.com/boringssl/+/0ce78a757d815c0dde9ed5884229f3a5b2cb3e9c%5E!/#F0 ok beck@
2016-03-20" the the " -> " the ", or in a couple of cases replace the superfluouskrw9-13/+13
"the" with the obviously intended word. Started with a "the the" spotted by Mihal Mazurek.
2016-03-17properly guard to macrosmmcc1-5/+5
ok otto@
2016-03-17explicit_bzero for asn1 objects on free. Too often these contain sensitive ↵beck2-48/+54
information and they should not be a performance bottleneck ok miod@ krw@
2016-03-15'accomodate' -> 'accommodate' in comments.krw10-18/+18
Started by diff from Mical Mazurek.
2016-03-14small step towards multiple pools: move two globls into the struct dir_infootto1-112/+126
ok @stefan armani@
2016-03-13environ and __progname are not declared in a public header; declare themguenther4-10/+4
in libc's hidden/stdlib.h instead of in each .c file that needs one ok deraadt@ gsoares@ mpi@
2016-03-13check return value for BN_hex2bn in regression testsbcook1-4/+10
2016-03-13Fix examples for EVP_PKEY_CTX_set_rsa_padding.bcook4-4/+4
Noted here, https://github.com/libressl-portable/portable/issues/161, we document a non-existent constant in the examples for EVP_PKEY_CTX_set_rsa_padding. ok deraadt@
2016-03-12Add error handling to the remaining calls to bn_wexpand().bcook4-32/+46
Noticed by pascal-cuoq from Github: https://github.com/libressl-portable/openbsd/issues/56 ok beck@
2016-03-12Remove sentences in RETURN VALUES sections saying that functions withmmcc28-79/+14
void return types 'return no value'. This is obvious and therefore unneccessary to mention. We spare rewind(3)'s sentence because espie@ pointed out that it's a warning - the function masks a potential error. This commit also adds a sentence to X509_free clarifying that it's NULL-safe. This bit was discussed with doug@. ok martijn@, sentiment supported by schwarze@
2016-03-12Bump for LibreSSL 2.4.0bcook2-6/+6
generated by cgit v1.2.3-55-g6feb (git 2.39.1) at 2025-04-28 08:14:07 +0000