View Issue Details

IDProjectCategoryView StatusLast Update
000685210000-014: PubSubSpecpublic2021-04-27 15:19
ReporterMatthias Damm Assigned ToMatthias Damm  
PriorityhighSeveritymajorReproducibilityalways
Status closedResolutionfixed 
Summary0006852: Starting value for AES-CTR BlockCounter is not consistent with RFC
Description

Part 14
Table 98 – Layout of the counter block for UADP message security
BlockCounter
The counter for each encrypted block of the NetworkMessage.
The counter is a 32-bit big endian integer (the opposite of the normal encoding for Uint32 values in OPC UA. This convention comes from the AES-CTR RFC).
The counter starts with 0 at the first block. The counter is incremented by 1 for each block.

https://tools.ietf.org/html/rfc3686
Block Counter
The block counter field is the least significant 32 bits of the
counter block. The block counter begins with the value of one,
and it is incremented to generate subsequent portions of the key
stream. The block counter is a 32-bit big-endian integer value.

The starting value for the BlockCounter is different in Part 14 (0) and RFC (1). This is a problem if crypto libraries are used that have a comlete implementation for AES-CRT.

Part 14 should be in sync with the RFC.

TagsNo tags attached.
Commit Version
Fix Due Date

Activities

Matthias Damm

2021-04-27 13:18

developer   ~0014255

Changed starting counter value from 0 to 1 to be consistent with RFC.

Jim Luth

2021-04-27 15:19

administrator   ~0014256

Agreed to changes is 1.05 and 1.04 Errata.

Issue History

Date Modified Username Field Change
2021-04-27 13:11 Matthias Damm New Issue
2021-04-27 13:18 Matthias Damm Assigned To => Matthias Damm
2021-04-27 13:18 Matthias Damm Status new => resolved
2021-04-27 13:18 Matthias Damm Resolution open => fixed
2021-04-27 13:18 Matthias Damm Note Added: 0014255
2021-04-27 15:19 Jim Luth Status resolved => closed
2021-04-27 15:19 Jim Luth Fixed in Version => 1.04
2021-04-27 15:19 Jim Luth Note Added: 0014256