suggest encryption

This commit is contained in:
Igor Sirotin 2026-04-28 21:45:15 +01:00
parent 09133e0a3f
commit 91ac51dd21
No known key found for this signature in database
GPG Key ID: 0EABBCB40CB9AD4A

View File

@ -187,8 +187,16 @@ Libraries **SHOULD** require only `segmentSize` from the application for normal
### Privacy
`entire_message_hash` enables correlation of segments that belong to the same original message but does not reveal content.
To prevent this correlation, applications **SHOULD** encrypt each segment after segmentation (see [Encryption](#encryption)).
Traffic analysis may still identify segmented flows.
### Encryption
This specification does not provide confidentiality.
Applications **SHOULD** encrypt each segment after segmentation
(i.e., encrypt the serialized `SegmentMessageProto` prior to transmission),
so that `entire_message_hash` and other identifying fields are not visible to observers.
### Integrity
Implementations **MUST** verify the Keccak256 hash post-reconstruction and discard on mismatch.