clear query| facets| time Search criteria: author:"erickt".   Results from 1 to 10 from 40 (0.0s).
Loading phrases to help you
refine your search...
0.9 timestamp example was missing "version" - TUF - [issue]
...The 0.9 tuf spec in section 4.6 mentions that "version" is included in the signed portion of timestamp.json, but was missing from the example file. This adds it.Feel free to reject this patc...
https://github.com/theupdateframework/specification/pull/37    Author: erickt , 2019-03-19, 18:24
Fix a misspelling of snapshot - TUF - [issue]
https://github.com/theupdateframework/specification/pull/26    Author: erickt , 2018-08-07, 23:02
Fix a typo in section 5.3.1 - TUF - [issue]
...It looks like an extra newline and bullet point was accidentally introduced in section 5.3.1. This removes it, and re-wraps the section....
https://github.com/theupdateframework/specification/pull/25    Author: erickt , 2018-08-07, 23:03
What is the PEM encoding for RSA public keys? - TUF - [issue]
...In section 4.2, the spec states that RSA public keys are stored in PEM format, but may be vague. RSA PEM keys support two forms of encoding, RSAPublicKey form, as in:-----BEGIN RSA PUBLIC KE...
https://github.com/theupdateframework/specification/issues/48    Author: erickt , 2019-08-08, 08:36
Use hex encoding is used for ed25519 and target hashes - TUF - [issue]
...According to #42, the spec should explicitly state that the ed25519 public key, and the target hash values are hex encoded values, since that is used by the majority of tuf implementations.C...
https://github.com/theupdateframework/specification/pull/47    Author: erickt , 2019-08-06, 09:04
divergence between implementations serializing ed25519 public keys - TUF - [issue]
...There is some ambiguity in the spec regarding how to encode ed25519's public portion of the keyval:The 'ed25519' format is:  { "keytype" : "ed25519",    "scheme" : "ed25519",&...
https://github.com/theupdateframework/specification/issues/42    Author: erickt , 2019-08-06, 09:04
Snapshot.json example is missing hash(es) and size for the root role - TUF - [issue]
...In section 4.6 of the spec, the description of the snapshot.json file states:The snapshot.json file is signed by the snapshot role. It lists the version numbers of all metadata on the reposi...
https://github.com/theupdateframework/specification/issues/31    Author: erickt , 2019-10-17, 19:08
Remove root, add delegation hashes to the snapshot metadata - TUF - [issue]
...According to @JustinCappos in #31, the root.json is no longer needed in the snapshot metadata, because the workflow will already have updated the root metadata before the snapshot metadata i...
https://github.com/theupdateframework/specification/pull/40    Author: erickt , 2019-10-17, 20:39
Fix keyids in the 1.0 spec - TUF - [issue]
...It looks like the sample Key IDs in the 1.0 spec were not updated to the TUF 1.0 algorithm. For example:>>> key_meta = { "keytype": "ed25519", "keyval": { "public": "72378e5bc588793...
https://github.com/theupdateframework/specification/pull/43    Author: erickt , 2019-10-17, 20:38
Clarify the type of the target "custom" field - TUF - [issue]
...In 4.5 of the spec, the TARGETPATH is defined as: { TARGETPATH : {       "length" : LENGTH,       "hashes" : HASHES,       ("...
https://github.com/theupdateframework/specification/issues/50    Author: erickt , 2019-08-15, 15:39