History log of /freebsd/usr.bin/su/su.c (Results 151 – 175 of 204)
Revision (<<< Hide revision tags) (Show revision tags >>>) Date Author Comments
Revision tags: release/4.6.1
# 831ab44e 09-Jul-2002 Andrey A. Chernov <ache@FreeBSD.org>

Remove tcsetpgrp() stuff across suspend/continue because it cause upper level
tcsh killed on resume (fg). It is because tcsh is interactive itself and
do its own things with terminal group.


Revision tags: release/4.6.0_cvs
# b22ac97b 26-Jun-2002 Matthew Dillon <dillon@FreeBSD.org>

This is Alexander Kabaev's patch to solve the signal problem with su
(see 'zsh exits upon ^C' thread). This may be temporary be he's been
running it for a year without incident so we should be golde

This is Alexander Kabaev's patch to solve the signal problem with su
(see 'zsh exits upon ^C' thread). This may be temporary be he's been
running it for a year without incident so we should be golden with it.

Approved by: des

show more ...


# 6592cfde 26-Jun-2002 Matthew Dillon <dillon@FreeBSD.org>

Backout 1.51 on DES's request.

Approved by: des


# 743ea208 29-May-2002 Dag-Erling Smørgrav <des@FreeBSD.org>

Make our child the leader of its own process group to avoid receiving
signals in its stead. This fixes the dread "zsh exits upon ^C" bug.


# a1bdb05c 28-May-2002 Dag-Erling Smørgrav <des@FreeBSD.org>

Drive-by whitespace cleanup & add NAI copyright


# 17e623ac 06-Mar-2002 Dag-Erling Smørgrav <des@FreeBSD.org>

Belatedly OpenPAMify. I forgot this patch in last night's megacommit.

Sponsored by: DARPA, NAI Labs


Revision tags: release/4.5.0_cvs, release/4.4.0_cvs
# 905fd6f3 24-Jan-2002 Dag-Erling Smørgrav <des@FreeBSD.org>

Don't set PAM_RHOST, this is a local login.

Sponsored by: DARPA, NAI Labs


# 69ebfe34 12-Sep-2001 Mark Murray <markm@FreeBSD.org>

Reinstate complete (and now correctly functioning) WARNS=2.


# 73bd08dd 07-Sep-2001 Mark Murray <markm@FreeBSD.org>

Back out (with prejudice) the last WARNS=2 fix. I cannot understand
its failure mode, and will revisit it later.


# 4239cf1c 04-Sep-2001 Mark Murray <markm@FreeBSD.org>

WARNS=2 fixes.

The remaining problem of converting highly incompatible pointer types
is done by "laundering" the value through a union.

This solves the problem (in my own mind) of how a "const char

WARNS=2 fixes.

The remaining problem of converting highly incompatible pointer types
is done by "laundering" the value through a union.

This solves the problem (in my own mind) of how a "const char *" _ever_
actually gets a value in a WARNS=2 world.

show more ...


# b1743630 20-Aug-2001 Mark Murray <markm@FreeBSD.org>

Very minor stylistic nit.

Discussed with: ru


# bf1bf891 15-Aug-2001 Ruslan Ermilov <ru@FreeBSD.org>

Substitute ARGSTR in-place.
Forgot trailing newline in usage().


# d1433646 15-Aug-2001 Ruslan Ermilov <ru@FreeBSD.org>

Fixed the usage() string.

This also reverts change in rev. 1.36 to the documented
style of writing usage().

PR: bin/29730
Submitted by: Joseph Mallett <jmallett@xMach.org>


# 788222e4 11-Aug-2001 Mark Murray <markm@FreeBSD.org>

Set the RUSER for PAM so that (eg) kerberos can set up tickets properly.


# 8cc3b02f 11-Aug-2001 Mark Murray <markm@FreeBSD.org>

WARNS=2 type cleanup.

WARNS=2 cannot be enable because of an unresolvable conflict in arg 2
of execv(). Document this in the Makefile.

Reviewed by: bde (su.c only)


# 5b3771f1 26-May-2001 Mark Murray <markm@FreeBSD.org>

Deconvolute the authentication mess, and hand total responsiblity
for authentication to PAM. This meens that WHEELSU-type logic can
now be effected in the pam.conf "su" configuration stack. While her

Deconvolute the authentication mess, and hand total responsiblity
for authentication to PAM. This meens that WHEELSU-type logic can
now be effected in the pam.conf "su" configuration stack. While here,
clean up the mess that the code had assumed over years of hacking by
folks using different styles. ANSIfy.

There is more policy in here that can be handed over to PAM. This will
be revisited.

show more ...


# af32b80c 10-May-2001 David E. O'Brien <obrien@FreeBSD.org>

Tell the user what group they must be in to su to root.

Submitted by: Seth Kingsley <sethk@osd.bsdi.com>


# 1351464c 28-Apr-2001 Mark Murray <markm@FreeBSD.org>

Dike out the Kerberos(IV) support on the grounds that better kerberos
support can be already obtained via PAM.


Revision tags: release/4.3.0_cvs, release/4.3.0
# 5bc9d93d 27-Mar-2001 Mark Murray <markm@FreeBSD.org>

Add full PAM support for account management and sessions.

The PAM_FAIL_CHECK and PAM_END macros in su.c came from the util-linux
package's PAM patches to the BSD login.c

Submitted by: "David J. Mac

Add full PAM support for account management and sessions.

The PAM_FAIL_CHECK and PAM_END macros in su.c came from the util-linux
package's PAM patches to the BSD login.c

Submitted by: "David J. MacKenzie" <djm@web.us.uu.net>

show more ...


# e292984c 01-Dec-2000 Robert Watson <rwatson@FreeBSD.org>

o Make comment match reality, synch code with comment.
o In practice: the comment indicates that all but umask and
environmental variables of the users login class are applied when su
occurs, unl

o Make comment match reality, synch code with comment.
o In practice: the comment indicates that all but umask and
environmental variables of the users login class are applied when su
occurs, unless -m is used to specify a class. This was incorrect;
in practice, the uid, gids, resources, and priority were set, and
then resources and priority were selectively removed. This meant
that some aspects of the user context were not set, including handling
of login events (wtmp, utmp), as well as the path specified in
login.conf.
o I changed it so that the behavior is the same, but instead,
LOGIN_SETALL is used, and appropriate flags are removed, including
the LOGIN_SETLOGIN and LOGIN_SETPATH entries that were implicitly
not present before. I also updated the comment to reflect
reality, selecting reality as the "correct" behavior.
o This has the practical benefit that as new LOGIN_SET* flags are
introduced, they are supported by su unless specifically disabled.
For example, of a LOGIN_SETLABEL flag is introduced to support
MAC labels determined by the user's login class, then su no longer
has to be modified.
o It might be desirable to have su use LOGIN_SETPATH depending on
its command line parameters, as it might or might not be
considered part of the "environment".

Obtained from: TrustedBSD Project

show more ...


Revision tags: release/4.2.0, release/4.1.1_cvs, release/4.1.0, release/3.5.0_cvs, release/4.0.0_cvs
# 0ed9356c 24-Feb-2000 Mark Murray <markm@FreeBSD.org>

Use libcrypto in place of libdes.


Revision tags: release/3.4.0_cvs, release/3.3.0_cvs
# c3aac50f 28-Aug-1999 Peter Wemm <peter@FreeBSD.org>

$Id$ -> $FreeBSD$


# 7312edce 13-Aug-1999 Sheldon Hearn <sheldonh@FreeBSD.org>

Axe LOGIN_CAP_AUTH.

PR: 10115
Reported by: Gene Skonicki <gene@cif.rochester.edu>
Requested by: jdp


# 95103bc0 02-Jul-1999 Bruce Evans <bde@FreeBSD.org>

Actually fixed ambiguous else. The previous revision had no effect.


# f32e012b 01-Jul-1999 Bill Fumerola <billf@FreeBSD.org>

Fix ambigious else.

Reviewed By: eivind


123456789