DDS-Security 1.0 FTF Avatar
  1. OMG Issue

DDSSEC_ — Which encryption algorithm for the SharedSecret ?

Open Closed All
  • Key: DDSSEC_-32
  • Legacy Issue Number: 19799
  • Status: closed  
  • Source: ZettaScale Technology ( Mr. Julien Enoch)
  • Summary:

    In Table 33 the binary_value1 of the HandshakeFinalMessageToken is described as following:
    "Shall be set to the result of encrypting the SharedSecret with the Public Key of the remote DomainParticipant that is the destination of the HandshakeFinalMessageToken."

    The encryption algorithm to use is not specified. It should be to ensure interoperability between different implementations of this builtin plugin
  • Reported: DDS-Security 1.0b1 — Wed, 10 Jun 2015 04:00 GMT
  • Disposition: Duplicate or Merged — DDS-Security 1.0
  • Disposition Summary:

    Specification of Encryption Algorithm for shared secret mentioned in Table 33

    The encryption algorithm for "Encrypting with a Public Key" is implied by the technology used for creating the Public/Private key pairs.
    In the case of Table 33 it is already specified in Section 9.3 that the Private/Public Key technology used is RSA with 2048-bit keys. However there is indeed an under-specification in that the padding used needs to be also specified.

    This issue of the need to specify the padding was also raised in DDSSEC_-38. Therefore issue DDSSEC_-32 is merged with DDSSEC_-38.
  • Updated: Tue, 12 Jul 2016 14:45 GMT