Get desktop application:
View/edit binary Protocol Buffers messages
client checks if leaf is specified
Used in:
client needs to check that both of these fields are set for each interior node
needed so client knows how to compute hash
indicates if the hash is for the left or right subtree
Used in: ,
Used in:
client does not assume server has not sent malformed root node
auth path consists of user leaf node, possibly interior nodes, and root node
Used in:
client does not assume server has not sent malformed leaf node
needed so client can loop over interior nodes
Used in:
this is actually the epoch date in milli seconds
need to check that root hash is included
server checks that type, and epoch are specified
epoch should <= than current epoch
provider MUST be specified if type is WITNESS
ok to use same format for getComm and getWitness calls
Used in:
Used in:
Used in: , ,
send the bigintegers (or something) as strings across the wire
Used in: , , ,
check that len matches the Hash size in bytes defined in client/server
need to check that len field is specified
server checks that name and epoch are specified
server must make sure that these two fields are specified
this name MUST be in DB for server to accept
server will parse this from C S expression
client checks that initial epoch and epoch interval are specified
generic server response, sent when error occurs or as ACK
Used in:
This should be generated / verified by parsing / building the ULNChangeReq Then converting to a byte[] Then signing/verifying
Used in:
this is the format of commitments that servers exchange