From 27171ef7533779fb2ffdcc88ce583d4649a45653 Mon Sep 17 00:00:00 2001 From: Alex Vanin Date: Fri, 31 Jul 2020 16:51:35 +0300 Subject: [PATCH] [#21] Add container id into EACLTable message EACLTable message and signature stored in blockchain storage. If owner has several containers, malicious node can return correct EACLTable of the container other than client actually requested. With container id field in the EACLTable, this malicious behaviour can be detected. ContainerID has id 1, so contract can easily cut container id from byte sequence. Signed-off-by: Alex Vanin --- acl/types.proto | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/acl/types.proto b/acl/types.proto index 7f3efc9..91e012f 100644 --- a/acl/types.proto +++ b/acl/types.proto @@ -101,6 +101,8 @@ message EACLRecord { // EACLRecord carries the information about extended ACL rules. message EACLTable { + // ContainerID of the container that should use given access control rules. + bytes ContainerID = 1 [json_name="ContainerID"]; // Records carries list of extended ACL rule records. - repeated EACLRecord Records = 1 [json_name="Records"]; + repeated EACLRecord Records = 2 [json_name="Records"]; }