openbsd/src/lib/libc/string, branch OPENBSD_5_6 A mirror of https://github.com/libressl/openbsd.git https://git.lua4.win/openbsd/atom?h=OPENBSD_5_6 2014-07-09T17:08:21+00:00 rephrase the stpcpy() warning 2014-07-09T17:08:21+00:00 naddy 2014-07-09T17:08:21+00:00 urn:sha1:ff0f26044242f360fa59cf8865351a7a458cdbd4 new wording agreed by at least kettenis@ millert@ otto@ loosen the spec for timingsafe functions slightly, so as to not 2014-06-21T20:22:15+00:00 tedu 2014-06-21T20:22:15+00:00 urn:sha1:71b30cdd53305a1e04e5f93862d35e680d38af91 artificially constrain alternative implementations. ok deraadt Protect explicit_bzero() from link-time optimization 2014-06-21T02:34:26+00:00 matthew 2014-06-21T02:34:26+00:00 urn:sha1:9c52c243dba540e16f6f2a3f88131dd7f668f419 Modern compiler toolchains are capable of optimizing even across translation unit boundaries, so simply moving the memory clearing into a separate function is not guaranteed to clear memory. To avoid this, we take advantage of ELF weak symbol semantics, and insert a call to an empty, weakly named function. The semantics of calling this function aren't determinable until load time, so the compiler and linker need to keep the memset() call. There are still ways a toolchain might defeat this trick (e.g., optimistically expecting the weak symbol to not be overloaded, and only calling memset() if it is; promoting weak symbols to strong symbols at link-time when emitting a static binary because they won't be interposed; implementing load-time optimizations). But at least for the foreseeable future, these seem unlikely. ok deraadt Add timingsafe_memcmp(). 2014-06-13T02:12:17+00:00 matthew 2014-06-13T02:12:17+00:00 urn:sha1:62fc04d99bb7daa7bc91641190502c1d2b3251cc ok deraadt, jmc, tedu mop up ifndef KERNEL goo; ok miod 2014-06-10T04:17:37+00:00 deraadt 2014-06-10T04:17:37+00:00 urn:sha1:a13b202796a212c4c4e553e85d8bad24bbdffe07 tweak previous; 2014-04-19T16:50:46+00:00 jmc 2014-04-19T16:50:46+00:00 urn:sha1:32d1bba35de775ff86f5f28b036116ea9aba621e Use somewhat harsher language and better examples; demonstrate that 2014-04-19T11:30:40+00:00 deraadt 2014-04-19T11:30:40+00:00 urn:sha1:ac3cb5c172d4edffffbf917c401f9b4bfecea55f non-dangerous use functions is difficult. ok guenther Add some missing names to the NAME sections. 2014-04-07T17:57:56+00:00 schwarze 2014-04-07T17:57:56+00:00 urn:sha1:fa13c5324eed9868f142f97ff49f21d410dbcf23 For inet(3), go the other way, remove some bogus symlinks. Found while testing the new makewhatis(8). ok jmc@ remove the never used bm string functions 2014-03-23T23:16:48+00:00 tedu 2014-03-23T23:16:48+00:00 urn:sha1:35c387ad7bdcb1925b8afb40488f879ff652603f in HISTORY, say where this actually came from; 2014-02-23T23:09:34+00:00 schwarze 2014-02-23T23:09:34+00:00 urn:sha1:2d56df9fd2f6fec6042cae8f61e95154cfdbcd3a ok deraadt@ bentley@