Bug 1233886 - [QE] Use "symmetric key" instead of "two-way key"
Summary: [QE] Use "symmetric key" instead of "two-way key"
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Documentation
Version: 6.4.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: post-GA
: EAP 6.4.2
Assignee: David Michael
QA Contact: Josef Cacek
URL: https://access.stage.redhat.com/beta/...
Whiteboard:
Depends On:
Blocks: 1233489
TreeView+ depends on / blocked
 
Reported: 2015-06-19 16:21 UTC by Josef Cacek
Modified: 2015-10-20 04:56 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-10-20 04:56:59 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Josef Cacek 2015-06-19 16:21:43 UTC
Book: Security Architecture
Revision: n_1415923_security-architecture_version_6.4_edition_1.0_release_0-revision_1
Section: SSL/TLS and Certificates

Issue description:
The "Two-way encryption key" term used in the guide is not commonly used and it could confuse users. The correct term is "symmetric key" or "key for symmetric encryption" (as used in TLS 1.2 RFC-5246).

Suggestions for improvement:
Use "symmetric key" instead of "two-way key".

Comment 4 Jan Tymel 2015-07-31 12:20:46 UTC
Failed verification in revision "n_1415923_security-architecture_version_6.4_edition_1.0_release_0-revision_6701121" of https://access.stage.redhat.com/documentation/en/red-hat-jboss-enterprise-application-platform/version-6.4/red-hat-jboss-enterprise-application-platform-64-security-architecture.

There are still several places, where the terms "two-way encryption key" or "two-way key" are used in the section "SSL/TLS and Certificates". Please, rewrite these occurrences to "symmetric key" too.
1) To ensure a secure exchange of the two-way encryption key, (...)
2) When a client requests a secure connection to exchange two-way keys (...)
3) (...) the client generates the two-way encryption key for the SSL/TLS connection (...)
4) The server decrypts the two-way encryption key (...)
5) (...) is encrypted using the two-way encryption key.


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