Bug 124104 – Nit picking over /etc/shadow description

Bug 124104 - Nit picking over /etc/shadow description

Summary:	Nit picking over /etc/shadow description

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	Red Hat Academy
Classification:	Retired
Component:	RHA030 Curriculum (Show other bugs)
Sub Component:
Version:	2.0
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Bowe Strickland
QA Contact:	Bowe Strickland
Docs Contact:

URL:	https://academy.redhat.com/courses/rh...
Whiteboard:
Keywords:	FutureFeature

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2004-05-23 23:39 EDT by Johnathan Kupferer
Modified:	2007-04-18 13:07 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Enhancement
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2005-01-07 12:31:14 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Johnathan Kupferer 2004-05-23 23:39:46 EDT

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1)
Gecko/20031114

Description of problem:
RHA033 -> Workbook 3 -> Chapter 1 -> Discussion

In the second paragraph after the "User Passwords and the /etc/shadow
file" heading:

"Because the file contains only passwords, its permissions do not
allow people to view its contents."

In addition to the encrypted passwords there is password aging
information.  Maybe pull out "only" and put in "encrypted".


Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
Visit the URL

Additional info:

Comment 1 Bowe Strickland 2005-01-03 11:54:39 EST

changed to "only password related information", more in line 
with point trying to be made... /etc/passwd conatained
encrypted passwords, too....

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