-
Notifications
You must be signed in to change notification settings - Fork 381
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Define Canonical Representations for SignedLogRoot and SignedMapRoot #958
Comments
After much discussion the new message SignedLogRoot {
bytes key_hint = 1; // Typically log_id.
bytes log_root = 2;
bytes signature = 3;
} The content inside
|
Fixed? |
Fixed
…On Tue, 22 May 2018 at 19:13, Al Cutter ***@***.***> wrote:
Fixed?
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#958 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAMHTpgAU-3RnbbLGbiN4ZTMdV_KNl6Uks5t1FU_gaJpZM4RzwJc>
.
|
The current
ObjectHash
based signature for theSignedLogRoot
andSignedMapRoot
in Trillian is not stable enough for production use. A simpler, well defined signature scheme is desired. A simpler scheme would enable:The proposed canonical encoding is a TLS struct containing the relevant fields.
Design Doc
Backwards compatibility
This change would break backwards compatibility with existing
SignedLogRoot
s.However:
SignedLogRoot
s.SignedLogRoot
. (Please speak up if you know of a counter example)Going forward, the
TreeInfo
struct will declare what signature format to use.The text was updated successfully, but these errors were encountered: