RESTful KT API: Replace "Entry" objects with "User" objects

google / keytransparency

A transparent and secure way to look up public keys.

https://security.googleblog.com/2017/01/security-through-transparency.html

Apache License 2.0

1.57k stars 151 forks source link

RESTful KT API: Replace "Entry" objects with "User" objects #913

Open gdbelvin opened 6 years ago

gdbelvin commented 6 years ago

The KT api currently does not really look like a RESTful API. This is because, unlike most restful APIs, KT is returning a lot of cryptographic "proof" in each response.

This can be improved by getting and posting a single "User" object which may optionally include a "UserCommitment" and "UserProof". The "UserCommitment" would be an obfuscated object that gets put in the Merkel Tree, while the "UserProof" would tie the data in "User" to the "UserCommitment".

gdbelvin commented 6 years ago

API Cleanup Actions:

[x] Rename Epoch with Revision for consistency with the Trillian Map.
[x] Rename Domain with Tree for clarity