summaryrefslogtreecommitdiffstats
path: root/libexec
Commit message (Collapse)AuthorAgeFilesLines
* Implement the dynamic string token substitution in the rpath andkib2009-03-183-10/+148
| | | | | | | | | | | | | | | soneeded pathes. The $ORIGIN, $OSNAME, $OSREL and $PLATFORM tokens are supported. Enabling the substitution requires DF_ORIGIN flag in DT_FLAGS or DF_1_ORIGIN if DF_FLAGS_1, that may be set with -z origin gnu ld flag. Translation is unconditionally disabled for setuid/setgid processes. The $ORIGIN translation relies on the AT_EXECPATH auxinfo supplied by kernel. Requested by: maho Tested by: maho, pho Reviewed by: kan
* Fix build when WITH_SSP is set explicitly.ru2009-02-211-2/+1
| | | | Submitted by: Jeremie Le Hen
* o Fix typo: indentical -> identical.maxim2009-01-301-1/+1
| | | | | | PR: docs/131149 Submitted by: Patrick Oonk MFC after: 1 week
* Fix handling of pts(4) device names in comsat(8). Also catch fork() errors.ed2009-01-171-6/+17
| | | | | | | | | | | | | | | | | Pseudo-terminals allocated with posix_openpt(2) will have more slashes in their path names than comsat(8) allows, so allow slashes when the character device name starts with "pts/". This patch is loosely based on NetBSD's changes, revision 1.33. Because it also included the changes to fork(), I imported them here as well. Maybe we could import even more fixes from the other BSD's? Original commit message from the NetBSD folks: PR/30170: Markus W Kilbinger: src/libexec/comsat complains about: '/' in "/dev/pts/1" Reported by: Robert Huff <roberthuff rcn com>
* Prevent cross-site forgery attacks on ftpd(8) due to splittingcperciva2008-12-233-8/+29
| | | | | | | | | | | | | long commands into multiple requests. [08:12] Avoid calling uninitialized function pointers in protocol switch code. [08:13] Merry Christmas everybody... Approved by: so (cperciva) Approved by: re (kensmith) Security: FreeBSD-SA-08:12.ftpd, FreeBSD-SA-08:13.protosw
* This main goals of this project are:qingli2008-12-151-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | 1. separating L2 tables (ARP, NDP) from the L3 routing tables 2. removing as much locking dependencies among these layers as possible to allow for some parallelism in the search operations 3. simplify the logic in the routing code, The most notable end result is the obsolescent of the route cloning (RTF_CLONING) concept, which translated into code reduction in both IPv4 ARP and IPv6 NDP related modules, and size reduction in struct rtentry{}. The change in design obsoletes the semantics of RTF_CLONING, RTF_WASCLONE and RTF_LLINFO routing flags. The userland applications such as "arp" and "ndp" have been modified to reflect those changes. The output from "netstat -r" shows only the routing entries. Quite a few developers have contributed to this project in the past: Glebius Smirnoff, Luigi Rizzo, Alessandro Cerri, and Andre Oppermann. And most recently: - Kip Macy revised the locking code completely, thus completing the last piece of the puzzle, Kip has also been conducting active functional testing - Sam Leffler has helped me improving/refactoring the code, and provided valuable reviews - Julian Elischer setup the perforce tree for me and has helped me maintaining that branch before the svn conversion
* Provide custom simple allocator for rtld locks in libthr. The allocatorkib2008-12-021-0/+1
| | | | | | | | | does not use any external symbols, thus avoiding possible recursion into rtld to resolve symbols, when called. Reviewed by: kan, davidxu Tested by: rink MFC after: 1 month
* Add two rtld exported symbols, _rtld_atfork_pre and _rtld_atfork_post.kib2008-11-274-0/+22
| | | | | | | | | | | | | | Threading library calls _pre before the fork, allowing the rtld to lock itself to ensure that other threads of the process are out of dynamic linker. _post releases the locks. This allows the rtld to have consistent state in the child. Although child may legitimately call only async-safe functions, the call may need plt relocation resolution, and this requires working rtld. Reported and debugging help by: rink Reviewed by: kan, davidxu MFC after: 1 month (anyway, not before 7.1 is out)
* Convert telnetd(8) to use posix_openpt(2).ed2008-11-131-1/+2
| | | | | | | | | | | | | | | | | | Some time ago I got some reports MPSAFE TTY broke telnetd(8). Even though it turned out to be a different problem within the TTY code, I spotted a small issue with telnetd(8). Instead of allocating PTY's using openpty(3) or posix_openpt(2), it used its own PTY allocation routine. This means that telnetd(8) still uses /dev/ptyXX-style devices. I've also increased the size of line[]. Even though 16 should be enough, we already use 13 bytes ("/dev/pts/999", including '\0'). 32 bytes gives us a little more freedom. Also enable -DSTREAMSPTY. Otherwise telnetd(8) strips the PTY's pathname to the latest slash instead of just removing "/dev/" (e.g. /dev/pts/0 -> 0, instead of pts/0). Reviewed by: rink
* Whitespace and style fixes, build at WARNS level 6.des2008-11-042-29/+35
| | | | MFC after: 3 weeks
* This code has no copyright. It is fairly obvious to me that we're aimp2008-10-131-14/+48
| | | | | | | | | | derivitive of NetBSD's mips_reloc.c, so pull in the copyright notice from there. Also, a minor tweak to load/store pointers. Other changes from NetBSD likely would be useful too... Obtained from: NetBSD
* MFp4: Fix a bug in the mips relocation code that prevents shared imagesimp2008-10-101-22/+14
| | | | | | | | | | | | | | | | | | | | | | | | from working. From p4 filelog of the upstream file in p4 //depot/projects/mips2-jnpr/src/libexec/rtld-elf/mips/reloc.c ... #6 change 140737 edit on 2008/04/27 by gonzo@gonzo_jeeves (text+ko) o Looks like handler for R_MIPS_REL32 brought by CS 137942 is broken for tradmips. Code from NetBSD's libexec/ld.elf_so/arch/mips/mips_reloc.c works just fine. ... #3 change 137942 edit on 2008/03/17 by rrs@rrs-mips2-jnpr (text+ko) Any relocation symbol lookup if its 0. It looks like this is the way the compiler indicates you need to look in another shared library. When we hit these as we relocate a object we will do the symbol lookups and setup the relocation table with the right value. Submitted by: rrs@, gonzo@
* Allow strong symbols to override weak ones for lookups done throughkan2008-10-101-4/+21
| | | | | | | | dlsym with RTLD_NEXT/RTLD_SELF handles. Allow symbols from ld-elf.so to be located this way too. Based on report and original patch from sobomax@.
* add new build knobs and jigger some existing controls to improvesam2008-09-211-5/+21
| | | | | | | | control over the result of buildworld and installworld; this especially helps packaging systems such as nanobsd Reviewed by: various (posted to arch) MFC after: 1 month
* Allow multiple locks to be acquired by detecting correspondingdavidxu2008-09-161-2/+2
| | | | | | | | bit flag, otherwise if a thread acquired a lock, another thread or the current thread itself can no longer acquire another lock because thread_mask_set() return whole flag word, this results bit leaking in the word and misbehavior in later locking and unlocking.
* Make sure internal rtld malloc routines are not called from unlockedkan2008-09-031-14/+17
| | | | | | | | | | | | | contexts as rtld's malloc is not thread safe and is only supposed to be called with exclusive bind lock already held. The originating PR submitted a patch on top of different pre-requisite workaroud for unsafe dlopen calls, and the patch was midief slighlty to apply to stock sources for the purpose of this commit. Running rtld malloc from unlocked contexts is a bug on its own. PR: 126950 Submited by: Oleg Dolgov
* Remove the now unneeded pt_chown utility.ed2008-08-243-112/+0
| | | | | | | | | | | | | | | | | | | | | | | Before we had a posix_openpt() that allocated PTY's with proper permissions in place, we used this set-uid utility to change the ownership of PTY slave devices to the real user ID of the process. This utility was used to implement grantpt(). In my first designs of the MPSAFE TTY layer, I replaced this by adding an ioctl() called TIOCGRANTPT, which was used to change the ownership. I left the pt_chown utility, because older C libraries needed it to work properly. After some discussions back in June I changed the PTY code to set permissions properly upon creation. Fortunately the previous grantpt() implementation changed permissions by hand when pt_chown is not installed, which always succeeds. This means grantpt() still works properly, even though the set-uid utility is missing. I've done tests with FreeBSD 5.2.1, FreeBSD 6.3 and FreeBSD 7.0 jails. All of them still work if I remove pt_chown. Reviewed by: philip (ex-mentor)
* Mark functions as __dead2 in order to help the LLVM static checkercperciva2008-08-041-1/+1
| | | | | | | understand which code paths aren't possible. This commit eliminates 117 false positive bug reports of the form "allocate memory; error out if pointer is NULL; use pointer".
* Enable GCC stack protection (aka Propolice) for userland:ru2008-06-251-0/+2
| | | | | | | | | | | | | | | | | | | | | - It is opt-out for now so as to give it maximum testing, but it may be turned opt-in for stable branches depending on the consensus. You can turn it off with WITHOUT_SSP. - WITHOUT_SSP was previously used to disable the build of GNU libssp. It is harmless to steal the knob as SSP symbols have been provided by libc for a long time, GNU libssp should not have been much used. - SSP is disabled in a few corners such as system bootstrap programs (sys/boot), process bootstrap code (rtld, csu) and SSP symbols themselves. - It should be safe to use -fstack-protector-all to build world, however libc will be automatically downgraded to -fstack-protector because it breaks rtld otherwise. - This option is unavailable on ia64. Enable GCC stack protection (aka Propolice) for kernel: - It is opt-out for now so as to give it maximum testing. - Do not compile your kernel with -fstack-protector-all, it won't work. Submitted by: Jeremie Le Hen <jeremie@le-hen.org>
* Use sysctl to fetch stats from the kernel instead of reading variablesjhb2008-06-102-48/+19
| | | | | | | | directly via libkvm. PR: kern/122875, bin/123014 Tested by: Danny Braniss danny cs.huji.ac.il MFC after: 1 week
* Make the meaning of the %A format specifier, as passed tobms2008-05-151-2/+5
| | | | LD_TRACE_LOADED_OBJECTS_FMT[12], more obvious for users like me.
* Fix conflicts after heimdal-1.1 import and add build infrastructure. Importdfr2008-05-071-2/+2
| | | | all non-style changes made by heimdal to our own libgssapi.
* Fix the problem with the C++ exception handling for the multithreadedkib2008-05-063-4/+8
| | | | | | | | | | | | | | | | | | | | programs. From the PR description: The gcc runtime's _Unwind_Find_FDE function, invoked during exception handling's stack unwinding, is not safe to execute from within multiple threads. FreeBSD' s dl_iterate_phdr() however permits multiple threads to pass through it though. The result is surprisingly reliable infinite looping of one or more threads if they just happen to be unwinding at the same time. Introduce the new lock that is write locked around the dl_iterate_pdr, thus providing required exclusion for the stack unwinders. PR: threads/123062 Submitted by: Andy Newman <an at atrn org> Reviewed by: kan MFC after: 2 weeks
* MFp4: Add mips support for dynamic linking.imp2008-04-045-5/+602
| | | | | | | This code came from the merged mips2 and Juniper mips repositories. Warner Losh, Randall Seager, Oleksandr Tymoshenko and Olivier Houchard worked to merge, debug and integrate this code. This code may also contain code derived from NetBSD.
* Fix some "in in" typos in comments.brueffer2008-03-261-1/+1
| | | | | | | PR: 121490 Submitted by: Anatoly Borodin <anatoly.borodin@gmail.com> Approved by: rwatson (mentor), jkoshy MFC after: 3 days
* For un-prototyped static inline functions declared in pthread_md.h onrwatson2007-12-011-1/+1
| | | | | | sparc64, use ANSI function headers and specifically indicate the lack of arguments with 'void'. Otherwise, warnings are generated at WARNS=3 for libkse, leading to a compile failure with -Werror.
* Add "with" to make the line go smoother.edwin2007-11-231-1/+1
|
* Add the -W options, which acts the same as -w but will generateedwin2007-11-233-8/+104
| | | | | | | | | | | unique names based on the submitted filename, a strftime(3) format string and a two digit sequence number. By default the strftime(3) format string is %Y%m%d (YYYYMMDD), but this can be changed by the -F option. PR: bin/106049 (based on patch in that PR) Approved by: grog@ (mentor)
* Include an extra header to get a function prototype.jb2007-11-191-0/+1
|
* Add a hackish knob to skip rtld, NO_RTLD. In conjunction withyar2007-10-311-1/+1
| | | | | | | | | | | | | | | | | src/Makefile.inc1 rev. 1.590, it can allow installing a world cross-built for a different arch over the live system. The procedure is more or less as follows: cp -R /rescue /rescue.old make installkernel TARGET_ARCH=foo make -DNO_RTLD installworld TARGET_ARCH=foo ^^^^^^^^^ PATH=/rescue.old chflags noschg /libexec/ld-elf.so.1 cp /usr/obj/foo/usr/src/libexec/rtld/ld-elf.so.1 /libexec chflags schg /libexec/ld-elf.so.1 <ditto for ld-elf32.so.1 if installing for amd64> reboot
* - Fix the handling of R_SPARC_OLO10, which is a bit of a special casemarius2007-10-161-9/+14
| | | | | | | | | | | | | | | | | | | | in the way we implement handling of relocations. As for the kernel part this fixes the loading of lots of modules, which failed to load due to unresolvable symbols when built after the GCC 4.2.0 import. This wasn't due to a change in GCC itself though but one of several changes in configuration done along the import. Specfically, HAVE_AS_REGISTER_PSEUDO_OP, which causes GCC to denote global registers used for scratch purposes and in turn GAS uses R_SPARC_OLO10 relocations for, is now defined. While at it replace some more ELF_R_TYPE which should have been ELF64_R_TYPE_ID but didn't cause problems so far. - Sync a sanity check between kernel and rtld(1) and change it to be maintenance free regarding the type used for the lookup table. - Sprinkle const on lookup tables. - Use __FBSDID. Reported and tested by: yongari MFC after: 5 days
* Fixed static linkage (build with -DNO_SHARED).ru2007-10-011-1/+1
| | | | Approved by: re (kensmith)
* Stop mentioning /usr/X11R6.delphij2007-07-241-1/+1
| | | | Approved by: re (hrs)
* Unbreak the dynamic linker by not creating a cache for rtld-elfmarcel2007-07-151-2/+6
| | | | | | | | | itself. It needs mmap(2), which now needs getosreldate(3) and which in turn uses a global variable to cache the result. This cannot be done before linking is done. See also: ../sparc64/reloc.c:1.15 Approved by: re (kensmith)
* Cache does not serve any purpose when rtld is relocating itself, dokensmith2007-07-131-2/+6
| | | | | | | not bother allocating one. Submitted by: kan Approved by: re (bmah)
* Add r_debug_state to the list of symbols exported from rtld. GDB needs tokan2007-07-111-0/+1
| | | | | | be able to find it in order to trap shared library events from rtld. Approved by: re (rwatson)
* Significantly reduce the memory leak as noted in BUGS section forscf2007-07-041-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | setenv(3) by tracking the size of the memory allocated instead of using strlen() on the current value. Convert all calls to POSIX from historic BSD API: - unsetenv returns an int. - putenv takes a char * instead of const char *. - putenv no longer makes a copy of the input string. - errno is set appropriately for POSIX. Exceptions involve bad environ variable and internal initialization code. These both set errno to EFAULT. Several patches to base utilities to handle the POSIX changes from Andrey Chernov's previous commit. A few I re-wrote to use setenv() instead of putenv(). New regression module for tools/regression/environ to test these functions. It also can be used to test the performance. Bump __FreeBSD_version to 700050 due to API change. PR: kern/99826 Approved by: wes Approved by: re (kensmith)
* Link pf 4.1 to the build:mlaier2007-07-033-14/+11
| | | | | | | | - move ftp-proxy from libexec to usr.sbin - add tftp-proxy - new altq mtag link Approved by: re (kensmith)
* Note PAM support in atrun(8).yar2007-06-171-4/+17
| | | | | Sort FILES section while there. Touch document date.
* Add PAM support to atrun(8).yar2007-06-152-11/+36
|
* Actually use new features of perr() and perrx().yar2007-06-151-44/+33
|
* Catch up with perr() becoming variadic.yar2007-06-151-1/+1
|
* Make perr() variadic and add perrx() to use in cases whereyar2007-06-151-4/+30
| | | | | errno is irrelevant. Some code duplication can be reduced if perr() is variadic and perrx() is available.
* Use a single setusercontext(3) instead of a bunch of basic syscalls.yar2007-06-142-0/+29
| | | | | Besides aesthetic benefits, that makes at(1) jobs subject to such login.conf(5) settings as resource limits.
* Spotted another copy of the loony error message.yar2007-06-141-1/+1
|
* Fix an error message that was beside the point.yar2007-06-141-1/+1
|
* Fix a typical off-by-one error that can result in an unterminated string:yar2007-06-141-1/+1
| | | | | | | | strncpy(dst, src, sizeof(dst)); by substituting the safer strlcpy() for strncpy(). X-Security: none (the source string isn't user-supplied)
* Correct a typo.bz2007-06-031-1/+1
| | | | | PR: 106049 Submitted by: edwin (as part of a larger patch)
* Update the man page to reflect that certain variables will be unset incsjp2007-05-171-2/+4
| | | | | the case that the program is set-user-ID or set-group-ID. Add missing annotations for LIBMAP and LIBMAP_DISABLE.
* In the event a process is tainted (setuid/setgid binaries), un-set anycsjp2007-05-171-10/+20
| | | | | | | | | | | | | | | | | | | | potentially dangerous environment variables all together. It should be noted that the run-time linker will not honnor these environment variables if the process is tainted currently. However, once a child of the tainted process calls setuid(2), it's status as being tainted (as defined by issetugid(2)) will be removed. This could be problematic because subsequent activations of the run-time linker could honnor these dangerous variables. This is more of an anti foot-shot mechanism, there is nothing I am aware of in base that does this, however there may be third party utilities which do, and there is no real negative impact of clearing these environment variables. Discussed on: secteam Reviewed by: cperciva PR: kern/109836 MFC after: 2 weeks
OpenPOWER on IntegriCloud