| commit | 8dea5b5ab97087a68a55675cce8e79d4b579b674 | |
| author | Juergen Weigert <jw@suse.de> | |
| Wed, 24 Feb 2010 01:43:33 +0000 (23 20:43 -0500) | ||
| committer | Sadrul Habib Chowdhury <sadrul@users.sourceforge.net> | |
| Wed, 24 Feb 2010 01:43:33 +0000 (23 20:43 -0500) | ||
| tree | 07b4facd660fa61f4445610491b7896011138199 | treesnapshot (tar.gz zip) |
| parent | 1df022599350ae3882843b772b2bc0869348b894 | commitdiff |
Reset displays before dumping a core.
If defined SHADOWPW, we may have passwd records in core, that the user
would not be able to access otherwise. In that case, we should not dump
core, as the core file would contain the passwd records, and would be
readable for the user.
We do not explicitly check for eff_uid == 0, because if his real_uid is
also 0 he could have read all this anyway. Leaving only the cases where the
two uids differ.
If defined SHADOWPW, we may have passwd records in core, that the user
would not be able to access otherwise. In that case, we should not dump
core, as the core file would contain the passwd records, and would be
readable for the user.
We do not explicitly check for eff_uid == 0, because if his real_uid is
also 0 he could have read all this anyway. Leaving only the cases where the
two uids differ.
| src/screen.c | diffblobblamehistory |