Skip to content
Snippets Groups Projects
Select Git revision
  • upstream/master
  • upstream/1.3
  • upstream/gh-pages
  • master default
  • upstream/thaidn-patch-1
  • upstream/1.2
  • upstream/merge_test
  • upstream/master_backup
  • v1.3.0-rc3
  • v1.3.0-rc2
  • v1.3.0-rc1
  • v1.2.2
  • v1.2.1
  • v1.2.0
  • v1.2.0-rc4
  • v1.2.0-rc3
  • v1.2.0-rc2
  • v1.1.1
  • v1.1.0
  • v1.0.0
20 results
Compare History
user avatar
Basic infrastructure.
Thai Duong authored 
- Directory structure follows TensorFlow.
- Rules for protobuf building are based on https://github.com/pubref/rules_protobuf, as I can't find anything simpler.
- Continuous integration with Kokoro (work in progress).

I also copied some existing Java/CC code from Bartosz and Daniel's experimental folders.

Change-Id: I7f993934d149c114320e3388fee84fbdafd7ba81
433c7b23
Name Last commit Last update
cc
java
proto
.gitignore
README.md
WORKSPACE
README.md

Cloud Crypto SDK

An open-source SDK that provides cloud customers with cryptographic functionalities needed to extend key management offering of Cloud KMS.

In particular, Cloud KMS needs support for “Envelope Encryption”, i.e., a client-side encryption of data with user-generated keys protected by KMS encryption: cloud user generates a data encryption key (DEK) locally, encrypts data with DEK, sends DEK to Storky to be encrypted (with a key managed by Storky), and stores encrypted DEK with encrypted data; at a later point user can retrieve encrypted data and DEK, use Storky to decrypt DEK, and use decrypted DEK to decrypt the data. A guiding principles for the design of the SDK are security, simplicity, and resistance to user errors.