Tiger UNIX security tool - Tasks: task #3070, Standardize "noshell"...
You are not allowed to post comments on this tracker with your current authentication level.
task #3070: Standardize "noshell" shell definitions.
Submitter: | Ryan Bradetich <rbrad> | ||
Submitted: | Mon 26 Jan 2004 07:06:54 AM UTC | ||
Category: | Make Tiger easier to run/inst | Should Start On: | Mon 01 Mar 2004 12:00:00 AM UTC |
Should be Finished on: | Sat 01 May 2004 12:00:00 AM UTC | Priority: | 5 - Normal |
Status: | None | Privacy: | Public |
Percent Complete: | 0% | Assigned to: | None |
Open/Closed: | Open | Effort: | 0.00 |
Mon 26 Jan 2004 09:28:10 AM UTC, comment #1: |
Javier Fernandez-Sanguino Peña <jfs>![]() |
Mon 26 Jan 2004 07:06:54 AM UTC, original submission:
We probably need to standarise the "invalid shell" defintion so that it can be configured per system and it can be used by both check_anonftp and check_accounts. |
Ryan Bradetich <rbrad>![]() |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
CC list is empty
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follows 1 latest change.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2004-01-26 | jfs | Summary | Standardize invalid shell definitions. | ![]() |
Standardize "noshell" shell definitions. |
"Invalid Shell" is not really a good name. Invalid is a shell that does not exist in /etc/shells and can be executed in the system, but is unknown to Tiger (i.e. not csh, ash...). The "noshell" definition is a list of shells that look like they are invalid (might or might not exist in /etc/shells) but are usually used as shells for blocked (system) accounts in some operating systems.
Since this varies per operating system, and is used by different security checks, it should be a configuration item