summaryrefslogtreecommitdiffstats
path: root/libexec
Commit message (Collapse)AuthorAgeFilesLines
* Clean up some warnings that don't result in a change in the object file:dwmalone2003-03-201-17/+20
| | | | | | | Constness, missing prototypes, non-ansi prototypes, missing initialisers, unnecessary declarations, shadowing. Reviewed by: md5
* Fix for ia64/48024 - ensure function pointer equality across elfarun2003-03-191-52/+77
| | | | | | | | | | | | objects. Programs such as sshd depend on two pointers to the same function being equal in a given process. However, the current ia64 implementation ensures that they're equal when both the pointers are instantiated in the same ELF object. The attached patch ensures that they're equal irrespective of where they're instantiated. Reviewed by marcel@ (mentor) and kan@
* Run a revision of the devstat interface:phk2003-03-151-4/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Kernel: Change statistics to use the *uptime() timescale (ie: relative to boottime) rather than the UTC aligned timescale. This makes the device statistics code oblivious to clock steps. Change timestamps to bintime format, they are cheaper. Remove the "busy_count", and replace it with two counter fields: "start_count" and "end_count", which are updated in the down and up paths respectively. This removes the locking constraint on devstat. Add a timestamp argument to devstat_start_transaction(), this will normally be a timestamp set by the *_bio() function in bp->bio_t0. Use this field to calculate duration of I/O operations. Add two timestamp arguments to devstat_end_transaction(), one is the current time, a NULL pointer means "take timestamp yourself", the other is the timestamp of when this transaction started (see above). Change calculation of busy_time to operate on "the salami principle": Only when we are idle, which we can determine by the start+end counts being identical, do we update the "busy_from" field in the down path. In the up path we accumulate the timeslice in busy_time and update busy_from. Change the byte_* and num_* fields into two arrays: bytes[] and operations[]. Userland: Change the misleading "busy_time" name to be called "snap_time" and make the time long double since that is what most users need anyway, fill it using clock_gettime(CLOCK_MONOTONIC) to put it on the same timescale as the kernel fields. Change devstat_compute_etime() to operate on struct bintime. Remove the version 2 legacy interface: the change to bintime makes compatibility far too expensive. Fix a bug in systat's "vm" page where boot relative busy times would be bogus. Bump __FreeBSD_version to 500107 Review & Collaboration by: ken
* Update to current devstat API.phk2003-03-151-6/+6
|
* Free obj->priv field in obj_free functions. This field is NULLkan2003-03-141-0/+1
| | | | | on all architectures except ia64, which uses it to keep function description table.
* No need to zero fill memory, mmapped anonymously. Kernel willkan2003-03-146-15/+1
| | | | | | return pre-zeroed pages itself. Noticed by: jake
* mdoc(7) police: Scheduled sweep.ru2003-02-241-1/+1
|
* mdoc(7) police: expand contraction.ru2003-02-231-1/+1
|
* Do not remove object from the lists at the unref_dag() stage.kan2003-02-171-8/+26
| | | | | | | Introduce a new unlink_object() function and call it in unload_object() instead. Removing the object in unref_dag() is too early, rtld calls _fini() function after that and shared objects might fail resolve their own symbols.
* Add #include <sys/resource.h>phk2003-02-161-0/+1
|
* Remove <sys/dkstat.h> #includephk2003-02-161-1/+0
|
* Advertize rtld(1) as ld.so(1) in manual pages worldphantom2003-02-132-1/+3
|
* Fix a typo in rtld_dirname.kan2003-02-131-1/+1
|
* Implement dlinfo() function.kan2003-02-132-32/+262
| | | | | | | | | | Introdice RTLD_SELF special handle and properly process it within dlsym() and dlinfo() functions. The intention is to improve our compatibility with Solaris and to make a Java port easier. Partially submitted by: phantom
* Add missing include files I forgot about in previous commit.kan2003-02-131-0/+2
|
* Remove /usr/lib/elf from a default search path.kan2003-02-133-19/+17
| | | | | | Move xprintf to malloc.c, it is only used there. Make static. Submitted by: phantom
* Kill unnecessary vertical whitespace.yar2003-02-111-1/+0
|
* Use LOG_AUTHPRIV to hide the username attempted during an invalid loginyar2003-02-111-1/+5
| | | | | | | from everyone but sysadmins. PR: bin/29487 MFC after: 3 days
* When unloading dependencies make sure they are removed from all thekan2003-02-101-9/+10
| | | | | | | | | | | | associated lists: remove RTLD_GLOBAL objects from global objects list; remove the parent object from dldags list of its children. Previosly we were doing that only to the top-level object OF the DAG being unloaded and all its dependencies were ignored, leading to mysterious crashes later. Submitted by: peter (partially)
* Add FBSDID. udp/bootps -> bootps/udp. Use err(3).charnier2003-02-054-46/+41
|
* Allow "~/" in pathnames to work for a chrooted user.yar2003-02-051-2/+4
|
* Let tilde expansion be done even if a file/directory doesn't exist yet.yar2003-02-041-35/+98
| | | | | | | | | | | | This makes such natural commands as "MKD ~user/newdir" or "STOR ~/newfile" do what they are supposed to instead of failing miserably with the "File not found" error. This involves a bit of code reorganization. Namely, the code doing glob(3) expansion has been separated to a function; a new function has been introduced to do tilde expansion; the latter function is invoked on a pathname before the former one. Thus behaviour mimicing that of the Bourne shell has been achieved.
* RFC 959 doesn't list reply code 550 as a valid responce to STOR/STOU,yar2003-02-041-1/+1
| | | | | so return reply code 553 to indicate a error from open(2) for consistency, as long as the code is used in the rest of the STOR/STOU handler.
* Add OPIE and PAM libs to the mix.obrien2003-02-021-0/+4
|
* OPIE and PAM bits to agument LukeMftpd.obrien2003-02-021-0/+153
| | | | Submitted by: mikeh (reworked by me)
* 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
OpenPOWER on IntegriCloud