| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
revision 1.8 of uucplock.c.
|
|
|
|
|
|
|
| |
ISSUES:
An example and better explansion on how to specify a user's login
class in /etc/master passwd is needed.
(As I don't seem to be specifiying it right, I can't do it).
|
|
|
|
|
|
| |
target.
Reviewed by: <many different folks>
Submitted by: Nickolay N. Dudorov" <nnd@nnd.itfs.nsk.su>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
$ vipw
[corrupt a line in editor, exit editor]
pwd_mkdb: corrupted entry
pwd_mkdb: at line #2
pwd_mkdb:
/etc/pw.012585: Inappropriate file type or format
re-edit the password file? [y]: n^D^D
[hang]
|
| |
|
|
|
|
| |
Suggested by: guido
|
|
|
|
| |
is restricted from running a given program.
|
|
|
|
| |
denying execution of certain programs.
|
| |
|
|
|
|
|
|
|
| |
the database.
PR: 3397
Submitted by: taob@risc.org (Brian Tao)
|
|
|
|
|
|
|
| |
indent and make this compile -Wall clean like the
Makefile suggests that it should. :)
Pointed out by: Bruce Evans <bde@zeta.org.au>
|
|
|
|
| |
Suggested by: joerg
|
|
|
|
| |
rcsid.
|
| |
|
| |
|
|
|
|
| |
disconnect.
|
| |
|
|
|
|
|
| |
PR: 3878
Submitted by: roman@rpd.univ.kiev.ua
|
|
|
|
|
| |
PR: 3820
Submitted by: Joseph Stein <joes@spiritone.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
These changes add the ability to specify that a UFS file/directory
cannot be unlinked. This is basically a scaled back version
of the IMMUTABLE flag. The reason is to allow an administrator
to create a directory hierarchy that a group of users
can arbitrarily add/delete files from, but that the hierarchy
itself is safe from removal by them.
If the NOUNLINK definition is set to 0
then this results in no change to what happens normally.
(and results in identical binary (in the kernel)).
It can be proven that if this bit is never set by the admin,
no new behaviour is introduced..
Several "good idea" comments from reviewers plus one grumble
about creeping featurism.
This code is in production in 2.2 based systems
|
| |
|
|
|
|
|
|
|
| |
visible type names in prototypes in user space headers. libutil.h
generates warnings with -Wall over the use of "const char *ttyname".
It's lucky it wasn't a #define conflict.
Is a single '_' prefix acceptable? or does it need to be two?
|
|
|
|
|
|
|
| |
PR:
Reviewed by:
Submitted by:
Obtained from:
|
|
|
|
| |
disqualified.
|
|
|
|
|
|
|
|
| |
bumped only 0.1 or 1.0 between releases. (See handbook.)
Note that if you have built world in -current in the last 48 hours or
so, you should manually remove /usr/lib/libutil.so.2.3 before
rebuilding world to cleanse your system.
|
|
|
|
| |
Suggested by: joerg
|
| |
|
|
|
|
| |
Suggested by: bde
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
o Incorporated BSDI code and enhancements, better logging for error
checking (which has been shown to be a problem, and is therefore
justified, imho); also some minor things we were missing, including
better quad_t math, which checks for under/overflows.
o setusercontext() now allows user resource limit overrides, but
does this AFTER dropping root privs, to restrict the user to
droping hard limits and set soft limits within the kernel's
allowed user limits.
o umask() only set once, and only if requested.
o add _secure_path(), and use in login.conf to guard against
symlinks etc. and non-root owned or non-user owned files being
used. Derived from BSDI contributed code.
o revamped authentication code to BSDI's latest api, which
includes deleting authenticate() and adding auth_check()
and a few other functions. This is still marked as depecated
in BSDI, but is included for completeness. No other source
in the tree uses this anyway, so it is now bracketed with
#ifdef LOGIN_CAP_AUTH which is by default not defined. Only
auth_checknologin() and auth_cat() are actually used in
module login_auth.c.
o AUTH_NONE definition removed (collided with other includes
in the tree). [bde]
o BSDI's login_getclass() now accepts a char *classname
parameter rather than struct passwd *pwd. We now do likewise,
but added login_getpwclass() for (sort of) backwards
compatiblity, namely because we handle root as a special
case for the default class. This will require quite a few
changes elsewhere in the source tree.
o We no longer pretend to support rlim_t as a long type.
o Revised code formatting to be more bsd-ish style.
|
|
|
|
| |
related files.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Reduce space for error bufer from 512 to 128: there is no such long strings
can be returned from strerror()
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Use snprintf instead of sprintf to avoid buffer overflows
Use snprintf in uu_lockerr instead of lots of hardcoded constants
and not null-terminated strncpy
Return "" for OK and "device in use" for INUSE, it allows simple
strcpy(buf, uu_lockerr(retcode)) without testing for special OK
case (NULL was there) and obtaining meaningful result for INUSE
("" was there) without special testing for it too.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
in uu_lock(). Add uu_lockerr() for turning the results of
uu_lock into something printable. Remove bogus section in man page
about race conditions allowing both processes to get the lock.
Include libutil.h and use uu_lock() correctly where it should.
Suggested by: ache@freebsd.org
|
| |
|
| |
|
|
|
|
| |
One manifestation of this bug: all networking users have coredumpsize=0
|
| |
|
| |
|
| |
|
|
|
|
| |
committer wasn't using the MicroSlop Natural keyboard though! :)
|
| |
|
| |
|