Bug 78850 - Typo "SHH" in RH Security guide Chapter 2. Attackers and Risks
Typo "SHH" in RH Security guide Chapter 2. Attackers and Risks
Status: CLOSED CURRENTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: rhl-sg (Show other bugs)
8.0
All Linux
medium Severity low
: ---
: ---
Assigned To: Johnray Fuller
Tammy Fox
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-12-01 23:25 EST by jcpeck
Modified: 2008-08-01 12:22 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-12-09 09:52:42 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)

  None (edit)
Description jcpeck 2002-12-01 23:25:41 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i586; en-US; rv:1.0.1) Gecko/20021003

Description of problem:
Excerpt:
 Even when using secure protocols, such as SHH, a remote user may be vulnerable
to certain attacks if they do not keep their client applications updated.

Document:
Red Hat Linux 8.0: The Official Red Hat Linux Security GuidePrevChapter 2.
Attackers and Risks

Version:
rhl-cg(EN)-8.0-HTML-RHI (2002-08-14T17:28-0400)



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


How reproducible:
Always

Steps to Reproduce:
1.Open documentation.
2.
3.
	

Additional info:
Comment 1 jcpeck 2002-12-01 23:57:06 EST
Changed component to security guide.
Comment 2 Johnray Fuller 2002-12-09 09:31:24 EST
Thanks for catching that. 

I have corrected the source and will correct the online HTML as well.

J
Comment 3 Johnray Fuller 2002-12-09 09:52:36 EST
K, I have corrected the online HTML and am closing the bug.

Thanks a million for your help

johnray
Comment 4 Johnray Fuller 2002-12-09 10:16:46 EST
I have fixed the source for future releases and the online HTML.

Thanks again for taking the time to let me know about this.

Johnray

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