Basic SSE-C Implementation

[windkit]

Description

Currently only support small object PUT/GET without any checking
(internally leo_ssec does some checking, but errors are not handled in leo_gateway)

Related Issue

#114

Related PR

leo-project/leo_object_storage#28
leo-project/leo_commons#13

[mocchira]

It might be good to Encrypt/Decrypt data on leo_storage rather than leo_gateway as it's CPU intensive task and leo_gateway tend to saturate CPU OTOH leo_storage's CPU tend to be idle.

[yosukehara]

@windkit I and @mocchira, we discussed the way of its implementation. It should be implemented on LeoStorage as @mocchira mentioned. Once, I've close this PR, then we need to re-design it.

• Support server side encryption (SSE) #114 (comment)

Thanks for your contribution.

[windkit]

yes, I have also thought about it, decrypt at leo_storage could be better for performance.

But decrypting at leo_storage means we have to send the key around, is the rpc traffic in Erlang encrypted?
Sending keys around is one issue, sending them in plain text is a big one.

[yosukehara]

@windkit

But decrypting at leo_storage means we have to send the key around, is the rpc traffic in Erlang encrypted?
Sending keys around is one issue, sending them in plain text is a big one.

We need to consider its implementation way which includes your concern.

[yosukehara]

Today, I’ve recognized #114’s design is not mature because there is no detailed design. We need to implement its function in a reliable way I believe, so I closed Wilson’s PR (I appreciate Wilson’s contribution). We need to write a design documentation especially new features.