Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 4298 - pam_console does not reset group.
pam_console does not reset group.
Product: Red Hat Linux
Classification: Retired
Component: pam (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: David Lawrence
Depends On:
  Show dependency treegraph
Reported: 1999-08-01 05:58 EDT by matthew
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 1999-08-02 10:56:07 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description matthew 1999-08-01 05:58:29 EDT
When a user logins to the console they are given ownership
of various device files.  When they log back out the
ownership is reverted back to what ever is specified in
"/etc/security/console.perms".  Howevcr while they own the
file it is possible for them to change the group of the
files and this isn't reverted.  In the default configuration
this isn't really a big risk becuase the specified modes
don't grant any special rights to the group.  Howerver, if a
jax or zip drives are installed these the group is given
read/write access.  Obviously this would also cause problems
if any of the configured permissions are changed from the
default.  I don't think this is serious but at it's
certainly unexpected and unnessisary behaviour.

Patch to allow a revert group to follow.
Comment 1 Michael K. Johnson 1999-08-02 10:56:59 EDT
Yuck, you are right.  I'm applying your patch, and extending the man
pages and the default console.perms appropriately.  Thanks for
noticing this.  Our next pam release will have this functionality
and will include groups (where necessary) in the console.perms file.

Your patch did an excellent job of following the style of the code
you were modifying, by the way.  :-)

Note You need to log in before you can comment on or make changes to this bug.