Bug 604058 - errors in Security guide - 3. Encryption
Summary: errors in Security guide - 3. Encryption
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: doc-Security_Guide
Version: 6.0
Hardware: All
OS: Linux
Target Milestone: rc
: ---
Assignee: Scott Radvan
QA Contact: Karel Srot
Depends On:
Blocks: 547585
TreeView+ depends on / blocked
Reported: 2010-06-15 10:19 UTC by Karel Srot
Modified: 2015-04-07 03:19 UTC (History)
1 user (show)

Clone Of:
Last Closed: 2010-06-15 21:03:22 UTC

Attachments (Terms of Use)

Description Karel Srot 2010-06-15 10:19:02 UTC
Description of problem:

* 3.7.3. Step-by-Step Instructions
  step 14 verify your fstab entry: mount /home
  This is a bit weird because according to the step 10 /home is already mounted. Well, it is not really an issue but I think
  that the user should be at least told to expect the warning.

* 3.8.1. 7-Zip Installation
  p7zip is AFAIK not available in RHEL6

* 3.9.1. Creating GPG Keys in GNOME
  key creation: From the ''Key'' menu select ''Create New Key...'' then ''PGP Key'...
  There is no Key menu in seahorse from rhel6, you have to select ''File'' > ''New'' then ''PGP Key'...

* 3.9.3. Creating GPG Keys Using the Command Line
  Before the gpgcode> program asks for signature information, the following prompt appears: Is this correct (y/n)? 
  Enter   ycode> to finish the process.
  - there are "code>" strings in the text.

Version-Release number of selected component (if applicable):
Security Guide
A Guide to Securing Red Hat Enterprise Linux
Edition 1.5

Comment 1 RHEL Product and Program Management 2010-06-15 10:33:15 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for

Comment 2 Scott Radvan 2010-06-15 21:03:22 UTC
all fixed, will appear upon next publish

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