summaryrefslogtreecommitdiffstats
path: root/libexec
Commit message (Collapse)AuthorAgeFilesLines
...
* Finally unifdef -DINTERNAL_LS.ru2000-03-131-1/+1
|
* Use libcrypto instead of libdes.markm2000-02-242-2/+2
|
* Support logging for IPv6 remote host.shin2000-02-181-4/+5
| | | | | | | Approved by: jkh PR: bin/16789 Submitted by: Ben Smithurst <ben@scientia.demon.co.uk
* Doc fix: remove references to ~ftp/bin/ls as we have FTPD_INTERNAL_LSpeter2000-02-171-8/+0
| | | | | | unconditionally active already. Noticed by: obrien
* Add more dual stack consideration.shin2000-02-101-19/+27
| | | | | | | -ftpd need to know each of AF_INET and AF_INET6 addr for hosts specified in /etc/ftphosts. Approved by: jkh
* Revert part of the last commit, remove {g|s}etflags from the libcjoe2000-02-051-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | interface, and statically link them to the programs using them. These functions, upon reflection and discussion, are too generically named for a library interface with such specific functionality. Also the api that they use, whilst ok for private use, isn't good enough for a libc function. Additionally there were complications with the build/install-world process. It depends heavily upon xinstall, which got broken by the change in api, and caused bootstrap problems and general mayhem. There is work in progress to address future problems that may be caused by changes in install-chain tools, and better names for {g|s}etflags can be derived when some future program requires them. For now the code has been left in src/lib/libc/gen (it started off in src/bin/ls). It's important to provide library functions for manipulating file flag strings if we ever want this interface to be adopted outside of the source tree, but now isn't necessarily the right moment with 4.0-release just around the corner. Approved: jkh
* Remove unnecessary -g for CFLAGS.shin2000-02-031-1/+1
| | | | | | | -g for CFLAGS which was set at debugging time was mistakenly committed, so removed it. Approved by: jkh
* Fix ftpd core dump when hostname is not set.shin2000-02-031-1/+2
| | | | | | | | | When hostname is not set, ftpd core dumps, because there is no NULL check for freeing name resolving information for its own hostname. So the check is added. Approved by: jkh
* sync iruserok() extension API with other BSDsshin2000-02-012-23/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Some of rcmd related function is need to be updated to support IPv6. Some of them are already updated as standard document. But there is also several de-facto functions and they are not listed in standard documents. They are, iruserok() (used by rlogind, rshd) ruserok() (used by kerberos, etc) KAME package updated those functions in original way. iruserok_af() ruserok_af() But recently there was discussion on IETF IPng mailing list about how to sync those API, and it is decided, -Those function is not standard and not documented. -But let BSDs sync their API as de-facto. And after some discussion, it is announced that -add update to iruserok() as iruserok_sa() -no ruserok() API change(it is only updated internaly) So I sync those API before 4.0 is released. The changes are, -prototype changes -ruserok() internal update (use iruserok_sa() inside) -removal of ruserok_af() -change iruserok_af() as static functioin, and also prefix the name with __. -add iruserok_sa() (Just call __iruserok_af() inside) -adding flag AI_ALL to getipnodebyaddr() called from __icheckhost(). This is necessary to support IPv4 communication via AF_INET6 socket could be correctly authenticated via iruserok_sa() -irusreok_af() call is replaced to iruserok_sa() call in rlogind, and rshd. Approved by: jkh
* Add a manual page for the ELF dynamic linker. I initially createdjdp2000-01-292-99/+22
| | | | | | rtld.1 by means of a repository copy from "src/libexec/rtld-aout/rtld.1". Then I edited it to make it (more) accurate for the ELF dynamic linker.
* Move the man pages for the a.out dynamic linker into the 1aoutjdp2000-01-292-227/+2
| | | | | | | section. I created rtld.1aout earlier with a repository copy. This clears the way for the ELF dynamic linker man page, which I will commit next.
* When a threads package registers locking methods with dllockinit(),jdp2000-01-295-50/+137
| | | | | | | | | | figure out which shared object(s) contain the the locking methods and fully bind those objects as if they had been loaded with LD_BIND_NOW=1. The goal is to keep the locking methods from requiring any lazy binding. Otherwise infinite recursion occurs in _rtld_bind. This fixes the infinite recursion problem in the linuxthreads port.
* Fix rshd coredump when AF_INET socket is used.shin2000-01-281-1/+1
| | | | Confirmed by: F. Heinrichmeyer <fritz.heinrichmeyer@fernuni-hagen.de>
* Changed setflags() to set_flags(). This fixes world breakage due tobde2000-01-283-5/+5
| | | | recently incremented namespace pollution in <unistd.h>.
* another tcp apps IPv6 updates.(should be make world safe)shin2000-01-277-119/+812
| | | | | | | ftp, telnet, ftpd, faithd also telnet related sync with crypto, secure, kerberosIV Obtained from: KAME project
* several tcp apps IPv6 updateshin2000-01-259-76/+192
| | | | | | | | | | | | -inetd -rshd -rlogind -telnetd -rsh -rlogin Reviewed by: freebsd-arch, cvs-committers Obtained from: KAME project
* Block almost all signals in the default locking method instead ofjdp2000-01-254-32/+40
| | | | | | | | just a few of them. This looks like it solves the recent ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/lockdflt.c:55 failures seen by some applications such as JDK.
* Fix various man pages to stop abusing the .Bx macro to generate thempp2000-01-232-9/+10
| | | | string "FreeBSD". Use the .Fx macro instead.
* Allow files in LD_PRELOAD to be separated by white space, like Solarisjdp2000-01-221-3/+4
| | | | and Linux.
* We do not support the -B option.asmodai2000-01-121-12/+1
| | | | | PR: 15925 Submitted by: Thierry Herbelot
* Revamp the mechanism for enumerating and calling shared objects'jdp2000-01-096-139/+187
| | | | | | | | | | | | init and fini functions. Now the code is very careful to hold no locks when calling these functions. Thus the dynamic linker cannot be re-entered with a lock already held. Remove the tolerance for recursive locking that I added in revision 1.2 of dllockinit.c. Recursive locking shouldn't happen any more. Mozilla and JDK users: I'd appreciate confirmation that things still work right (or at least the same) with these changes.
* . mdoc(7)'fyphantom2000-01-072-11/+29
| | | | | | | | . add Xrs to hosts.equiv(5), auth.conf(5), services(5) to some pages . sort Xrs in SEE ALSO sections Patches based on PR: docs/15680 Submitted by: Christian Weisgerber <naddy@mips.rhein-neckar.de>
* Moved flags_to_string and string_to_flags into libutil. It's used injoe1999-12-301-1/+1
| | | | many places nowadays.
* Work around an assert failure in the dynamic linker's default threadjdp1999-12-284-16/+32
| | | | | | | | | | | | | | | | locking functions. If an application loads a shared object with dlopen() and the shared object has an init function which requires lazy binding, then _rtld_bind is called when the thread is already inside the dynamic linker. This leads to a recursive acquisition of the lock, which I was not expecting -- hence the assert failure. This work-around makes the default locking functions handle recursive locking. It is NOT the correct fix -- that should be implemented at the generic locking level rather than in the default locking functions. I will implement the correct fix in a future commit. Since the dllockinit() interface will likely need to change, warn about that in both the man page and the header file.
* Add a new function dllockinit() for registering thread lockingjdp1999-12-2711-45/+509
| | | | | | | | | | | | | | | | | | | functions to be used by the dynamic linker. This can be called by threads packages at start-up time. I will add the call to libc_r soon. Also add a default locking method that is used up until dllockinit() is called. The default method works by blocking SIGVTALRM, SIGPROF, and SIGALRM in critical sections. It is based on the observation that most user-space threads packages implement thread preemption with one of these signals (usually SIGVTALRM). The dynamic linker has never been reentrant, but it became less reentrant in revision 1.34 of "src/libexec/rtld-elf/rtld.c". Starting with that revision, multiple threads each doing lazy binding could interfere with each other. The usual symptom was that a symbol was falsely reported as undefined at start-up time. It was rare but not unseen. This commit fixes it.
* Revert the libcrypt/libmd stuff back to how it was. This should not havepeter1999-12-182-4/+4
| | | | | | | | happened as it was working around problems elsewhere (ie: binutils/ld not doing the right thing according to the ELF design). libcrypt has been adjusted to not need the runtime -lmd. It's still not quite right (ld is supposed to work damnit) but at least it doesn't impact all the users of libcrypt in Marcel's cross-build model.
* Add libmd (or move it after libcrypt). We don't want the linker to bemarcel1999-12-162-4/+4
| | | | | smart because it will definitely get it wrong. This popped up during cross-linking.
* Correct the ttys.5 and init.8 manpages with respect to the incorrectsheldonh1999-12-061-1/+11
| | | | | | | | | assumption that only getty processes can be managed. Describe the SysV-like ability to keep arbitrary long-running processes alive using a non-device first field in /etc/ttys. PR: 12767 Submitted by: Peter Jeremy <peter.jeremy@alcatel.com.au>
* Reactivate named-xferpeter1999-11-301-1/+1
|
* Move named and associated tools into a seperate makefile section andpeter1999-11-301-4/+29
| | | | disable them pending an import and cleanup of bind 8.2.2.p5.
* Add a ``-P pidfile'' optionbrian1999-11-232-3/+37
|
* Enable pppoedbrian1999-11-211-1/+1
|
* pppoed(8) - a server to accept PPPoE connectionsbrian1999-11-213-0/+735
|
* In revision 1.21 I changed the search order for shared libraries,jdp1999-11-191-1/+1
| | | | | | | but I forgot to make the corresponding fix to the comment. Rectify that. Submitted by: Tony Finch <fanf@demon.net>
* Fix bootpd for Alpha.marcel1999-11-123-9/+11
| | | | | | | | | | | bptypes.h originally defined int32 to be of type long. This obviously doesn't work on the Alpha. By defining int32 (and u_int32) in terms of int32_t (and u_int32_t) it now is what it says it should be. Two occurrences of 'unsigned int32' have been changed to 'u_int32' for consistency. Submitted by: Wilko Bulte <wilko@yedi.iaf.nl>
* Log username with password failure.eivind1999-11-061-1/+1
| | | | This has proved useful in real life installations.
* Allow for a telnet in secure/ (SRA telnet).markm1999-10-071-1/+1
|
* sync with netbsd PR 8534, fix undefined C code.alfred1999-10-071-1/+1
| | | | Pointed out by: David A. Holland
* .Nm += "rtld"phantom1999-09-283-3/+6
| | | | apropos(1) now knows about rtld(1) manpage.
* Correct spelling : ascii -> ASCIIphantom1999-09-201-1/+1
| | | | | | PR: docs/13702 Submitted by: Stephen J. Roznowski <sjr@home.com> Reviewed by: mpp
* Fix for new Kerberos4. Make a fist cut at PAM-ising while I'm here.markm1999-09-198-326/+388
|
* When a STAT command is sent to ftpd as an out-of-band transmission duringmharo1999-09-121-0/+1
| | | | | | | | a file transfer, the command was mishandled on every other receipt of the command. PR: 13261 Submitted by: Ian Lepore <ian@plutotech.com>
* Fix more Common Error brokenness.markm1999-09-062-4/+4
|
* Add common error lib for the Kerberos case.markm1999-09-061-2/+2
|
* Make jdk-1.1.8 work again. It turns out that some code insidejdp1999-09-051-5/+9
| | | | | | | | | | | | | | | libjava peeks into the dynamic linker's private Obj_Entry structures. My recent changes introduced some new members near the front of the structures, causing libjava to get the wrong fields. This commit moves the new members toward the end of the structure so that the layout of the portion that is relevant to JDK remains the same as before. I will work with the JDK porting team to see if we can come up with a less fragile way for them to do what they need to do. I understand the current approach was necessary in order to work around some limitations of the dynamic linker. Maybe it's not necessary any more.
* Enable -Wformat checking for debug_printf().jdp1999-09-041-1/+3
|
* Change the warning about unrecognized entries in the dynamic tablejdp1999-09-041-2/+2
| | | | | | | to a debug message which is disabled in production builds of the dynamic linker. The condition warned about is normally harmless. PR: bin/12849
* When looking up symbols, search the objects loaded at program startjdp1999-09-041-8/+8
| | | | | | | up first -- before the dlopened DAGs containing the referencing object. This makes dynamically loaded perl modules work properly again.
* Get the actual pathname of the dynamic linker from the executable'sjdp1999-08-303-12/+31
| | | | | | | PT_INTERP program header entry, to ensure that gdb always finds the right dynamic linker. Use obj->relocbase to simplify a few calculations where appropriate.
* When checking to see if a shared object is already loaded, look forjdp1999-08-303-7/+38
| | | | a device/inode match if no pathname match is found.
OpenPOWER on IntegriCloud