IT16573: PCOM: SECURITY ENCRYPTION LEVEL DISPLAY FIELD SHOWS INCORRECT VALUES

PCOMM_1201_MLS
PCOMM_6.0.18.0_MLS_RefreshPack
PCOMM_6.0.18.0_JAP_RefreshPack
PCOMM_6.0.18.0_KOR_RefreshPack
PCOMM_6.0.18.0_CHT_RefreshPack
PCOMM_6.0.18.0_CHS_RefreshPack
PCOMM_6.0.18.0_Document_Admin_Aids
PCOMM_60180_Document_Admin_Aids
PCOMM_60180_DocumentAdminAids
PCOMM_60180_MLS_RefreshPack
PCOMM_60180_KOR_RefreshPack
PCOMM_60180_JAP_RefreshPack
PCOMM_60180_CHT_RefreshPack
PCOMM_60180_CHS_RefreshPack
Personal Communications 6.0.18
IBM Personal Communications 12.0.1

APAR status

• Closed as program error.

Error description

• We have PCOMM V6 defined with TLS1.2 option selected.  We also
  have the TLS1.2 ciphers available on the Mainframe.  The client
  is connecting with one of the TLS1.2 ciphers (as per our ZEN
  Implex display information), but when looking at the
  Configuration, Security Information pull-down on the PCOMM
  client once a session is started, it shows an incorrect cipher
  value (older SSLV3 cipher).  In this case it is showing
  0x000035 - TLS_RSA_WITH_AES_256_CBC_SHA
  when in fact it has connected with
  0x00009D - TLS_RSA_WITH_AES_256_GCM_SHA384
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All users of IBM Personal Communications using MSCAPI secure *
  * connection                                                   *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Incorrect cipher specification is shown by Communication ->  *
  * Security Information menu item when using Microsoft          *
  * CryptoAPI (MSCAPI) security package.                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Users of IBM Personal Communications MSCAPI secure connection
  will see incorrect cipher specification under the Communication
  - > Security Information menu item. Cipher specification
  actually used for communication is different than what is shown.
  

Problem conclusion

• PCSTLNET.DLL has been corrected to address the problem.
  
  Fix scheduled for PCOMM 6.0.18 and PCOMM 12.0.1.0 Refresh Pack
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Modules/Macros

• pcstlnet
  

Fix information

• Fixed component name

  PCOMM COMBO-ENC

• Fixed component ID

  5639I7000

Applicable component levels

• R60G PSY

     UP

• RC00 PSY

     UP