| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
PR: bin/23052
Submitted by: Mike Sellenschuetter <mike.sellenschuetter@bankofamerica.com>
MFC after: 1 week
|
| |
|
|
|
|
| |
functions that exit instead of failing
|
|
|
|
|
| |
These are not perfectly in agreement with each other style-wise, but they
are orders of orders of magnitude more consistent style-wise than before.
|
| |
|
|
|
|
|
|
|
| |
properly, and doesn't hurt the other algorithms.
PR: 28991
Submitted by: Yoshihiro Koya <Yoshihiro.Koya@math.yokohama-cu.ac.jp>
|
| |
|
| |
|
| |
|
|
|
|
| |
Idea from: Theo de Raadt <deraadt@openbsd.org>
|
|
|
|
| |
Submitted by: bde
|
|
|
|
|
|
|
| |
There is still one instance of non-constant format string use inside that
function, but it's hard to fix.
MFC after: 1 week
|
|
|
|
| |
builtints (e.g., exit, strcmp).
|
|
|
|
|
|
|
| |
years; remove them from CFLAGS.
PR: 23712
Submitted by: Volker Stolz <stolz@i2.informatik.rwth-aachen.de>
|
|
|
|
| |
PR: 26674
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
account at creation, create accounts with a "*" password (so you can
use alternate authentication schemes without fearing a "default" password
biting you later), and blank passwords.
Yes, adduser could create a blank password account, but this makes it
slightly more difficult to shoot yourself in the foot.
The /etc/adduser.conf entries are:
# use password-based authentication for new users
# defaultusepassword = "yes" | "no"
defaultusepassword = "yes"
# enable account password at creation
# (the password will be prepended with a star if the account isn't enabled)
# defaultenableaccount = "yes" | "no"
defaultenableaccount = "yes"
# allow blank passwords
# defaultemptypassword = "yes" | "no"
defaultemptypassword = "no"
Requested by: alfred
Reviewed by: alfred
|
|
|
|
| |
Reviewed by: kris
|
|
|
|
|
|
| |
group file. Because of the way the group sorting works while printing
out the new file it's not possible at this time to restore comments
in other locations, but at least they won't just disappear altogether.
|
|
|
|
|
|
|
|
|
|
| |
one user who differs only by case. The other perl tools assume (or enforce)
the all lowercase requirement, therefore making the search through
master.passwd case insensitive seemed a reasonable optimization, IMO.
I understand, although I do not sympathize with, the argument that someone
might want to do this on purpose, and might subsequently want to use the
wrong tool for the job. So, this fix should hopefully satisfy both camps.
|
|
|
|
| |
Dan Langille <dan@freebsddiary.org>.
|
|
|
|
|
|
|
| |
username to rm.
PR: 25961
Submitted by: Linh Pham <lplist@closedsrc.org>
|
| |
|
|
|
|
| |
- MAN[1-9] -> MAN.
|
|
|
|
|
|
| |
so as not to pollute application namespace.
Submitted by: bde
|
| |
|
|
|
|
|
|
|
|
| |
reserved word, causing breakage when a C++ program included libutil.h
This change will be propagated elsewhere shortly.
Submitted by: jkh
Obtained from: TrustedBSD Project
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
utility functions which convert between string namespace names and
numeric constants used by the interface. Right now, two namespaces
are supported, EXTATTR_NAMESPACE_SYSTEM ("system") and
EXTATTR_NAMESPACE_USER ("user"). These functions are used by
various userland EA utilities, rather than hard coding the routines
all over the place.
Obtained from: TrustedBSD Project
|
|
|
|
|
| |
PR: 25187
Approved by: nik
|
|
|
|
|
| |
PR: 25187
Approved by: nik
|
| |
|
|
|
|
|
|
| |
(random() or arc4random())
Reviewed by: bde
|
|
|
|
|
|
| |
Seperate does not exist in the english language.
Submitted to look at by: kris
|
| |
|
| |
|
|
|
|
| |
Submitted by: Peter Avalos <pavalos@theshell.com>
|
|
|
|
|
|
| |
structure internals.
Reviewed by: markm
|
| |
|
| |
|
|
|
|
|
| |
PR: misc/23451
Submitted by: Ben Rosengart, ben@narcissus.net
|
|
|
|
|
| |
* Backslash escape non-alphanumeric chars in the login name so that perl
doesn't choke on things like '$'.
|
| |
|
|
|
|
| |
Use _PATH_* where where possible.
|
|
|
|
| |
PR: docs/13218
|
|
|
|
|
|
|
|
| |
Address this by using getpwnam(), thus killing several birds with
the same stone. My fix is slightly more aggressive than the
originators. :)
PR: misc/22278
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
that applications know how large of a buffer they must allocate before
calling property_find(). Also added a $FreeBSD$ tag while I'm here.
Approved by: jkh
|
|
|
|
|
|
|
|
|
|
| |
getting libutil/libcrypt to work properly. I've determined that GCC
thinks it can inline all functions, including weak-symboled ones, if
it feels like it.
Create a new stub.c and move any stubs there to prevent inlining.
Thanks to jdp and William S. Duncanson for helping me finally find the
problem.
|