Bug 757580 - Incorrect information about gpg keys in 3.9.3
Summary: Incorrect information about gpg keys in 3.9.3
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: doc-Security_Guide
Version: 6.2
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: rc
: ---
Assignee: Martin Prpič
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-27 23:10 UTC by Ondrej Moriš
Modified: 2011-12-07 12:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-07 12:37:44 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Ondrej Moriš 2011-11-27 23:10:57 UTC
Description of problem:

There is incorrect of outdated information in 3.9.3. Creating GPG Keys Using the Command Line:

"Please select what kind of key you want: (1) DSA and ElGamal (default) (2) DSA (sign only) (4) RSA (sign only) Your selection? In almost all cases, the default is the correct choice. A DSA/ElGamal key allows you not only to sign communications, but also to encrypt files."

But there are actually more choices:

Please select what kind of key you want:
   (1) RSA and RSA (default)
   (2) DSA and Elgamal
   (3) DSA (sign only)
   (4) RSA (sign only)

Moreover:

"Next, choose the key size: minimum keysize is 768 bits default keysize is 1024 bits highest suggested keysize is 2048 bits What keysize do you want? (1024) Again, the default is sufficient for almost all users, and represents an ''extremely'' strong level of security."

But minimum keysize is 1024 and maximum is 4096.

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

1.5


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