forked from TrueCloudLab/frostfs-api
526792324d
NeoFS uses different checksum algorithms. It looks like we need to explicitly define what algorithm is used in each particular case. Signed-off-by: Stanislav Bogatyrev <stanislav@nspcc.ru>
67 lines
1.4 KiB
Protocol Buffer
67 lines
1.4 KiB
Protocol Buffer
syntax = "proto3";
|
|
|
|
package neo.fs.v2.refs;
|
|
|
|
option go_package = "github.com/nspcc-dev/neofs-api-go/v2/refs/grpc;refs";
|
|
option csharp_namespace = "NeoFS.API.v2.Refs";
|
|
|
|
// Address of object (container id + object id)
|
|
message Address {
|
|
// container_id carries container identifier.
|
|
ContainerID container_id = 1;
|
|
// object_id carries object identifier.
|
|
ObjectID object_id = 2;
|
|
}
|
|
|
|
// NeoFS object identifier.
|
|
message ObjectID {
|
|
// value carries the object identifier in a binary format.
|
|
bytes value = 1;
|
|
}
|
|
|
|
// NeoFS container identifier.
|
|
message ContainerID {
|
|
// value carries the container identifier in a binary format.
|
|
bytes value = 1;
|
|
}
|
|
|
|
// OwnerID group information about the owner of the NeoFS container.
|
|
message OwnerID {
|
|
// value carries the identifier of the container owner in a binary format.
|
|
bytes value = 1;
|
|
}
|
|
|
|
// Represents API version used by node.
|
|
message Version {
|
|
// Major API version.
|
|
uint32 major = 1;
|
|
|
|
// Minor API version.
|
|
uint32 minor = 2;
|
|
}
|
|
|
|
// Signature of something in NeoFS
|
|
message Signature {
|
|
// Public key used for signing.
|
|
bytes key = 1;
|
|
// Signature
|
|
bytes sign = 2;
|
|
}
|
|
|
|
// Checksum algorithm type
|
|
enum ChecksumType {
|
|
// Unknown. Not used
|
|
CHECKSUM_TYPE_UNSPECIFIED = 0;
|
|
|
|
// Tillich-Zemor homomorphic hash funciton
|
|
TZ = 1;
|
|
|
|
// SHA-256
|
|
SHA256 = 2;
|
|
}
|
|
|
|
// Checksum message
|
|
message Checksum {
|
|
ChecksumType type = 1;
|
|
bytes sum = 2;
|
|
}
|