summaryrefslogtreecommitdiffstats
path: root/libexec
Commit message (Collapse)AuthorAgeFilesLines
* Let real users access special files through FTPyar2003-01-311-3/+13
| | | | | | | | | | if allowed by their filesystem permissions. This doesn't break anything since using sendfile(2) is triggered later by a separate S_ISREG conditional. PR: bin/20824 MFC after: 1 week
* When searching for a unique file name in guniquefd(),yar2003-01-291-0/+4
| | | | | | | distinguish between the cases of an existing file and a real system error, such as I/O failure, no access etc. MFC after: 3 days
* Add a new option to ftpd(8), "-h", to disable printing anyyar2003-01-293-6/+25
| | | | | | | | host-specific information in FTP server messages (so paranoid admins can sleep at night :-) PR: bin/16705 MFC after: 1 week
* Give the code around chroot(2)/chdir(2) a major overhaul byyar2003-01-294-41/+101
| | | | | | | | | | | | | | | | | | | | | | | separating its part around chroot(2) from that around initial chdir(2). This makes the below changes really easy. Move seteuid(to user's uid) to before calling chdir(2). There are two goals to achieve by that. First, NFS mounted home directories with restrictive permissions become accessible (local superuser can't access them if not mapped to uid 0 on the remote side explicitly.) Second, all the permissions to the home directory pathname components become effective; previously a user could be carried to any local directory despite its permissions since the chdir(2) was done with euid 0. This reduces possible impact from FTP server misconfiguration, e.g., assigning a wrong home directory to a user. Implement the "/./" feature. Now a guest or user subject to chrooting may have "/./" in his login directory, which separates his chroot directory from his home directory inside the chrooted environment. This works for ftpchroot(5) as well. PR: bin/17843 bin/23944
* Actually extract the second field from a line in ftpchroot(5)yar2003-01-271-15/+17
| | | | instead of just using the rest of the line behind the first field.
* Allow more than one separator character between fields in ftpchroot(5).yar2003-01-271-1/+3
|
* Extend the format of /etc/ftpchroot so an alternative chrootyar2003-01-264-24/+171
| | | | | | | | | | | directory can be specified for a user or a group. Add the manpage ftpchroot(5) since the file's format has grown complex enough. PR: bin/45327 Portions submitted by: Hideki SAKAMOTO <sakamoto@hlla.is.tsukuba.ac.jp> MFC after: 1 week
* GLOB_MAXPATH has been deprecated in favour of GLOB_LIMIT.yar2003-01-251-1/+1
|
* - Add a new option, ``-P port'', to specify the port for ftpd(8)yar2003-01-232-5/+23
| | | | | | | | | to listen at in daemon mode. - Use the port by 1 less than the control port as the default data port instead of always using hard-coded port 20. Submitted by: roam MFC after: 1 week
* Prevent server-side glob(3) patterns from expandingyar2003-01-221-4/+17
| | | | | | | | to a pathname that contains '\r' or '\n'. Together with the earlier STAT bugfix, this must solve the problem of such pathnames appearing in the FTP control stream.
* The FTP daemon was vulnerable to a DoS where an attacker could bind()cjc2003-01-211-19/+26
| | | | | | | | | | | | up port 20 for an extended period of time and thus lock out all other users from establishing PORT data connections. Don't hold on to the bind() while we loop around waiting to see if we can make our connection. Being a DoS, it has security implications, giving it a short MFC time. MFC after: 1 day
* Fix a typo (missed &&).sobomax2003-01-201-1/+1
| | | | Submitted by: marcus
* Add a new gettytab(5) option - `pl', which if set tells getty that the linesobomax2003-01-194-4/+7
| | | | | | | | | | in question is PPP-only line, i.e. no PPP-sequence detection is necessary and PPP login program referenced by `pp' should be started automatically instead of login(1) Feature suggested and sponsored by: United Networks of Ukraine No reply from: re MFC after: 2 weeks
* Prepend a space character if a line begins with a digityar2003-01-161-0/+11
| | | | | | | | | | in the output to the "STAT file" request. This closes one discrepancy with RFC 959 (page 36.) See also http://www.kb.cert.org/vuls/id/328867 Obtained from: OpenBSD
* Replace the instances of literal "/bin/ls"yar2003-01-161-2/+3
| | | | | with the _PATH_LS macro to be consistent with the rest of the ftpd(8) source.
* We have a usable 'LOGIN_NAME_MAX' now.obrien2003-01-061-2/+0
|
* Need to prototype strsuftollx() to quiet a warning.obrien2003-01-061-0/+8
|
* Make the "nbsd_20030105" import build.obrien2003-01-063-1/+18
|
* Implement POSIX grantpt(3) functionality, and add a pt_chown utility (akinjmallett2003-01-023-0/+113
| | | | | | | | to Solaris, it is in /usr/libexec) to perform the handing over of tty nodes to the user being granted the pty. Submitted by: Ryan Younce <ryany@pobox.com> Reviewed by: security-officer@, standards@, mike@
* Correct typos, mostly s/ a / an / where appropriate. Some whitespace cleanup,schweikh2003-01-013-3/+3
| | | | especially in troff files.
* Fix typos, mostly s/ an / a / where appropriate and a few s/an/and/schweikh2002-12-303-3/+3
| | | | Add FreeBSD Id tag where missing.
* english(4) police.schweikh2002-12-273-3/+3
|
* mdoc(7) police: Deal with self-xrefs.ru2002-12-242-2/+2
|
* Fixed the abuses of .Ql visible on stderr in troff mode.ru2002-12-232-2/+2
| | | | PR: docs/37176
* Change the way ELF coredumps are handled. Instead of unconditionallydillon2002-12-161-6/+23
| | | | | | | | | | | | | | | | | | | skipping read-only pages, which can result in valuable non-text-related data not getting dumped, the ELF loader and the dynamic loader now mark read-only text pages NOCORE and the coredump code only checks (primarily) for complete inaccessibility of the page or NOCORE being set. Certain applications which map large amounts of read-only data will produce much larger cores. A new sysctl has been added, debug.elf_legacy_coredump, which will revert to the old behavior. This commit represents collaborative work by all parties involved. The PR contains a program demonstrating the problem. PR: kern/45994 Submitted by: "Peter Edwards" <pmedwards@eircom.net>, Archie Cobbs <archie@dellroad.org> Reviewed by: jdp, dillon MFC after: 7 days
* Uniformly refer to a file system as "file system".ru2002-12-124-6/+6
| | | | Approved by: re
* Fix rtld to handle SPARC_R_UA{16,64} relocations correctly.kan2002-12-051-2/+2
| | | | Approved by: re (rwatson)
* rtld support for PowerPC. Mostly obtained from NetBSD, with modsgrehan2002-12-045-0/+926
| | | | | | | | for binutils 2.13 Reviewed by: benno Approved by: re (blanket)
* Put back a test for binaries with no PT_LOAD entries I over-jealoslykan2002-11-291-0/+4
| | | | | | removed in r1.69. Apploved by: re (rwatson)
* mdoc(7) police:ru2002-11-251-37/+35
| | | | | | | | | Properly sort options, spell "file system" correctly, expand contraction. Catch up to the src/etc/syslog.conf,v 1.23 change: ftpd(8) session logs are now by default get logged to /var/log/xferlog. Approved by: re
* Fix the handling of high PLT entries (> 32764) on sparc64. This requirestmm2002-11-1812-213/+242
| | | | | | | | additional arguments to reloc_jmpslot(), which is why MI code and MD code of other platforms had to be changed. Reviewed by: jake Approved by: re
* Oops. Some ut_time stuff slipped through the cracks. These turned outpeter2002-11-171-1/+2
| | | | to be non-fatal due to stack alignment roundups.
* [DAIVD O'BRIEN's OPINION]obrien2002-11-121-1/+4
| | | | Head off what I think is an abuse of the TRB, and disable lukemftpd.
* o Fix usage().maxim2002-11-121-5/+20
| | | | | | | | o Explicitly initialize domain pointer. o Fix passwd file parsing. PR: bin/39671 (3) MFC after: 2 weeks
* We don't use libpam, libopie, or libmd.obrien2002-11-121-12/+2
|
* We have fparseln(3). Also libskey on RELENG_4.obrien2002-11-121-2/+8
|
* Update for version 1.2 Beta 2.obrien2002-11-121-5/+5
|
* Don't free the current addrinfo list, or else a pointer to a freedyar2002-11-111-1/+1
| | | | | | | | | memory area would arise. Only an addrinfo list from an earlier call to getaddrinfo() should be freed there because it will be substituted by the current list referenced by "res". Reported by: John Long <fbsd1@pruam.com> MFC after: 5 days
* Have ftpd specify the LOGIN_SETMAC flag to setlogincontext() so thatrwatson2002-10-241-2/+3
| | | | | | | | | | | | | | | MAC labels are set if MAC is enabled and configured for the user logging in. Note that lukemftpd is not considered a supported application when MAC is enabled, as it does not use the standard system interfaces for managing user contexts; if lukemftpd is used with labeled MAC policies, it will not properly give up privileges when switching to the user account. Approved by: re Obtained from: TrustedBSD Project Sponsored by: DARPA, Network Associates Laboratories
* Unbreak by merging the change in r1.51 of src/libexec/ftpd/Makefile.kuriyama2002-10-241-1/+1
|
* Teach "ls -Z" to use the policy-agnostic MAC label interfaces ratherrwatson2002-10-241-1/+1
| | | | | | | | | | | than the LOMAC-specific interfaces for listing MAC labels. This permits ls to view MAC labels in a manner similar to getfmac, when ls is used with the -l argument. Next generation LOMAC will use the MAC Framework so should "just" work with this and other policies. Not the prettiest code in the world, but then, neither is ls(1). Obtained from: TrustedBSD Project Sponsored by: DARPA, Network Associates Laboratories
* Add support for binaries with arbitrary number of PT_LOAD sections.kan2002-10-232-45/+55
| | | | Reviewed by: peter
* Change the symbol lookup order to search RTLD_GLOBAL objectskan2002-10-191-12/+12
| | | | | | | | | | before referencing object's DAG. This makes it possible for C++ exceptions to work across shared libraries and brings us closer to the search order used by Solaris/Linux. Reviewed by: jdp Approved by: obrien MFC after: 1 month
* Fix a problem with RTLD_TRACE flag to dlopen(3), which sometimes can returnsobomax2002-10-191-6/+8
| | | | | | | | | | | | | even if there was no error occured (when trying to dlopen(3) object that already linked into executable which does dlopen(3) call). This is more proper fix for `ldd /usr/lib/libc.so' problem, because the new behaviour conforms to documentation. Remove workaround from ldd.c (rev.1.32). PR: 35099 Submitted by: Nathan Hawkins <utsl@quic.net> MFC after: 1 week
* Don't call report() without a format string.kris2002-10-131-1/+1
| | | | MFC after: 3 days
* Mark the logerr() function __printflike().kris2002-10-131-1/+1
| | | | MFC after: 3 days
* Use strlcpy instead of incorrectly using strncpy.kris2002-10-131-1/+1
| | | | MFC after: 2 weeks
* Use the new freebsd output format from Binutils 2.13.1.obrien2002-10-121-2/+2
|
* de-__P()alfred2002-10-092-2/+2
|
* <machine/atomic.h> requires <sys/types.h>.ru2002-10-092-2/+1
| | | | Reviewed by: jake, mike
OpenPOWER on IntegriCloud