View Issue Details

IDProjectCategoryView StatusLast Update
000949010000-004: ServicesSpecpublic2024-04-09 16:09
ReporterMatthias Damm Assigned ToRandy Armstrong  
PrioritynormalSeverityminorReproducibilityhave not tried
Status assignedResolutionopen 
Product Version1.05.03 
Summary0009490: Padding in EncryptedSecret Format
Description

More clarification requirements from my colleagues regarding EncryptedSecret Format:

The padding scheme in the EncryptedSecret Format is defined completely different then in every commonly used
standard (eg. in PKCS#7).
From what I understand a N bytes secret and block size of 16 Bytes would be padded as follows.

10 Bytes of Data:
{10 bytes Data, 0x04, 0x04, 0x04, 0x04, 0x04, 0x00}
----Data------, ----4 Bytes Padding---, -padding size--

14 bytes of Data:
{14 bytes data, 0x00, 0x00 }
----Data------, ----0 Bytes Padding---, -padding size--

An example for clarification would be helpful.

A clarification why the padding size needs to be an UInt16 would be also helpful.

Furthermore the padding scheme is described in the generalized EncryptedSecret Format Section (7.41.2.3).
However different encryption algorithms respectively EncryptedSecret types have different requirements to the padding.
For instance the EccEncryptedSecret (7.41.2.5, Table 190) references the padding scheme as described in (7.41.2.3, Table 187).
This however relies on properties of block ciphers (block size).
This makes no sense to me in the context of an EccEncryptedSecret.
A clarification is needed here.

TagsNo tags attached.
Commit Version
Fix Due Date

Relationships

related to 0009450 closedRandy Armstrong Missing information for key Generation for RsaEncryptedSecret in Part 4 

Activities

There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2024-03-21 17:50 Matthias Damm New Issue
2024-03-21 23:36 Matthias Damm Relationship added related to 0009450
2024-04-09 16:09 Jim Luth Assigned To => Randy Armstrong
2024-04-09 16:09 Jim Luth Status new => assigned