[#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 <alexey@nspcc.ru>
This commit is contained in:
parent
6a2c66cbd8
commit
27171ef753
1 changed files with 3 additions and 1 deletions
|
@ -101,6 +101,8 @@ message EACLRecord {
|
||||||
|
|
||||||
// EACLRecord carries the information about extended ACL rules.
|
// EACLRecord carries the information about extended ACL rules.
|
||||||
message EACLTable {
|
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.
|
// Records carries list of extended ACL rule records.
|
||||||
repeated EACLRecord Records = 1 [json_name="Records"];
|
repeated EACLRecord Records = 2 [json_name="Records"];
|
||||||
}
|
}
|
||||||
|
|
Loading…
Reference in a new issue