Bug 1233886

Summary: [QE] Use "symmetric key" instead of "two-way key"
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Josef Cacek <jcacek>
Component: DocumentationAssignee: David Michael <dmichael>
Status: CLOSED CURRENTRELEASE QA Contact: Josef Cacek <jcacek>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.4.0CC: dmichael, eap-docs, jtymel, mchoma, pnag, zrhoads
Target Milestone: post-GAKeywords: Documentation, EasyFix, Triaged
Target Release: EAP 6.4.2   
Hardware: Unspecified   
OS: Unspecified   
URL: https://access.stage.redhat.com/beta/documentation/en/red-hat-jboss-enterprise-application-platform-64-security-architecture
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-10-20 04:56:59 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1233489    

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.