| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
PR: 17875
Submitted by: Bjoern Fischer <bfischer@Techfak.Uni-Bielefeld.DE>
|
|
|
|
|
| |
of the typeset output, tend to make diffs harder to read and provide
bad examples for new-comers to mdoc.
|
|
|
|
| |
Approved by: jkh
|
| |
|
|
|
|
| |
Approved by: jkh
|
|
|
|
|
|
|
|
| |
might it confuse people, but it causes a warning message with
nroff, and no version history mentions a 1.2 version of FreeBSD.
If anything, a ``HISTORY'' section should show which version this
appeared in.
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
smart because it will definitely get it wrong. This popped up during
cross-linking.
|
|
|
|
|
|
|
|
| |
commit and those which cause ugly nroff output have been fixed, since
the purpose of the style guideline which they contravene is to reduce
the sizes of deltas.
Reported by: bde
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Consistently misspell built-in as builtin.
* Add a builtin(1) manpage and create builtin(1) MLINKS for all shell
builtin commands for which no standalone utility exists. These MLINKS
replace those that were created for csh(1).
* Add appropriate xrefs for builtin(1) to the csh(1) and sh(1) manpages,
as well as to the manpages of standalone utilities which are supported
as shell builtin commands in at least one of the shells. In such
manpages, explain that similar functionality may be provided as a
shell builtin command.
* Improve sh(1)'s description of the cd builtin command. Csh(1) already
describes it adequately. Replace the cd(1) manpage with a builtin(1)
MLINKS link.
* Clean up some mdoc problems: use Xr instead of literal "foo(n)"; use
Ic instead of Xr for shell builtin commands.
* Undo English contractions.
Reviewed by: mpp, rgrimes
|
| |
|
|
|
|
|
| |
chown failures in some places, but instead log them like we do all
other errors.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
track.
The $Id$ line is normally at the bottom of the main comment block in the
man page, separated from the rest of the manpage by an empty comment,
like so;
.\" $Id$
.\"
If the immediately preceding comment is a @(#) format ID marker than the
the $Id$ will line up underneath it with no intervening blank lines.
Otherwise, an additional blank line is inserted.
Approved by: bde
|
|
|
|
| |
add gid switching before chdir and comment why it needed
|
|
|
|
| |
trimdomain() now works as expected.
|
| |
|
|
|
|
|
| |
format. This fixes the undefined symbols when building login for
a.out.
|
|
|
|
| |
there is now a static version of libpam.
|
|
|
|
|
|
|
| |
authentication only). This comes handy when you're tight on space.
Submitted by: mostly John Baldwin <jobaldwi@vt.edu>
Reviewed by: John D. Polstra <jdp@polstra.com>
|
|
|
|
|
|
|
|
|
| |
to be written to /etc.
The only essential change is in paths.h, so any third-party software
written correctly will pick it up in the next rebuild.
Reviewed by: the committers list (actually an old version)
|
|
|
|
| |
logins get logged.
|
|
|
|
|
| |
Add a reference to pam(8) in the login(1) and login.access(5) manual
pages.
|
|
|
|
|
|
|
|
|
|
| |
because libpam is built shared only. There is a way to build PAM
into a static library that contains all (or a selected subset) of
the modules. But our Makefiles don't support that yet. Until I get
that working, just force NOSHARED=no in login's Makefile. Of
course, it still won't work if NOPIC is set.
Submitted by: bde
|
|
|
|
|
|
|
|
| |
Change login to use PAM for authentication. I kept the built-in
passwd/NIS authentication support, to handle cases where the system
is missing its "/etc/pam.conf" file. S/Key and KerberosIV
authentication methods are removed from the login program, but
still available in PAM modules.
|
|
|
|
|
|
| |
it's here to stay.
This code is starting to look almost reasonable again.
|
|
|
|
|
|
|
|
|
| |
not complete, and it hasn't been touched for 18 months. All the
ifdefs obfuscate the code. I discussed the LOGIN_CAP_AUTH support
with its author and he agreed that it is a dead end. I am bringing
PAM into the tree within the next two weeks. It is much more
flexible than LOGIN_CAP_AUTH, and will serve as a superior replacement
for it.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
PR: 6529
Submitted by: Dan Lukes <dan@obluda.cz>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
libc/gen/getpass.c. The old behaviour of blocking SIGINT and not
changing SIGQUIT was restored in rev.1.5 of getpass.c. The change
here completely restores the old behaviour of not supporting killing
login with keyboard signals (only) at the password prompt. There
is no reason to support this, since login can be exited normally
by typing a couple of ^D's. Login certainly shouldn't dump core
in response to user input. Previously, SIGQUIT killed login
immediately but SIGINT killed it only after the password was
entered.
PR: 7444
|
|
|
|
|
|
|
|
| |
if LOGIN_CAP_AUTH was defined. This is kind of silly, because
LOGIN_CAP_AUTH doesn't work anyway, is not defined currently,
probably will never be defined, and IMHO should not be defined.
But I'm sure you'll sleep better tonight, knowing that these bugs
are gone.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Here is a some example for avoiding a confusion.
It asssumes a logged host domain is "spec.co.jp". All
example is longer than UT_HOSTNAMELEN value.
1) turbo.tama.spec.co.jp: 192.19.0.2 -> trubo.tama
2) turbo.tama.foo.co.jp : 192.19.0.2 -> 192.19.0.2
3) specgw.spec.co.jp : 202.32.13.1 -> specgw
Submitted by: Atsushi Murai <amurai@spec.co.jp>
|
| |
|
|
|
|
|
|
|
|
|
| |
is on a NFS partion without root read access. Also, flip euid again for
the duration of the chdir() to the homedir for the same reason.
PR: 5145
Submitted by: Joel.Faedi@esial.u-nancy.fr
Also tested by: A Joseph Koshy <koshy@india.hp.com>
|
| |
|
|
|
|
|
|
| |
file referred to a path ending in "/*" which was reasonable to me,
but gcc wasn't so sure. So now the comment refers to a path ending in
"*".
|
|
|
|
|
|
|
|
|
|
|
| |
for some DES passwords
crypt(real_password, salt)
is equal to
crypt("", salt);
It means that this user (and not only he) can login without
entering password at all, just pressing Return.
So if empty password entered and crypted password is not empty,
invalidate any crypt result by assigning ":"
|
|
|
|
|
|
|
|
|
| |
Otherwise, when pressing the INT ke at the password prompt, the password
will be displayed. Now login will be killed.
Probably the same will have to be done for the LOGIN_CAP_AUTH case.
I have not done that.
Reviewed by: Joerg Wunsch
|
| |
|
|
|
|
|
| |
PR: bin/4801
Submitted by: mishania@demos.su (Mikhail A. Sokolov)
|
|
|
|
| |
Also quieten -Wall a bit.
|
|
|
|
| |
Submitted by: Vincent Poy <vince@venus.gaianet.net>
|
|
|
|
| |
elf, libskey.so will not expose it's implementation on it's caller.
|
|
|
|
|
| |
update man page. Add usage().
Obtained from: OpenBSD
|
|
|
|
| |
(It has been ``SKEY.ACCESS''.)
|
| |
|
|
|
|
| |
auth_rmfiles() was being called in error without LOGIN_CAP_AUTH defined.
|
| |
|