Rich Felker c49d3c8ada avoid loading of multiple libc versions via explicit pathname ... such loading is unsafe, and can happen when programs use their own logic to locate a .so file then pass the absolute pathname to dlopen, or if an absolute pathname ends up in DT_NEEDED headers. multiple loads with only the base name were already precluded, provided libc was named appropriately, by special-casing standard library names. one function symbol (in the reserved namespace, but public, since it's part of the crt1 entry point ABI) and one data symbol are checked. this way we avoid likely false positives, particularly from libraries interposing and wrapping functions. there is no hard requirement to avoid breaking such usage, since trying to run a hook before libc is even initialized is not a supported usage case, but it's friendlier not to break things.		2017-03-14 18:51:27 -04:00
..
dlstart.c	fix regression in SH/FDPIC dynamic linker	2016-02-18 04:13:05 +00:00
dynlink.c	avoid loading of multiple libc versions via explicit pathname	2017-03-14 18:51:27 -04:00