From 88f2388e928adbd5bf3d553115ce535a709f679d Mon Sep 17 00:00:00 2001 From: akwizgran Date: Fri, 24 Apr 2015 18:01:26 +0000 Subject: [PATCH] Blog signature must cover the client ID --- BSP.markdown | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/BSP.markdown b/BSP.markdown index be996b1..07c90c9 100644 --- a/BSP.markdown +++ b/BSP.markdown @@ -18,17 +18,17 @@ BSP uses a cryptographic hash function, H(m), with an output length of HASH_LEN ### Client identifiers -Each client has a unique identifier HASH_LEN bytes long: +Each client has a unique random identifier HASH_LEN bytes long: * `client_id = R(HASH_LEN)` ### Channel identifiers -Each channel has a unique identifier HASH_LEN bytes long, which is the hash of the client identifier and a client data structure describing the channel: +Each channel has a unique identifier HASH_LEN bytes long. The identifier is calculated by hashing the client identifier and a data structure called the channel descriptor: -* `channel_id = HASH("CHANNEL_ID", client_id, client_data_structure)` +* `channel_id = HASH("CHANNEL_ID", client_id, channel_descriptor)` -Including the client identifier in the hash prevents collisions between clients that use similar data structures. +The channel descriptor is supplied by the client and is not interpreted by BSP. Including the client identifier in the hash prevents collisions between clients that use similar data structures for their descriptors. ### Message format