in-toto / docs

Specification and other related documents.

https://in-toto.io

in-toto/docs Issues

Develop a user doc contribution policy
Updated 3 months ago
Develop a reference doc contribution policy
Updated 3 months ago
Establish workflow for Python Reference Doc edits
Updated 3 months ago
Create a System Overview for user docs
Updated 3 months ago1
Create a Glossary page
Updated 3 months ago1
Create Getting Started Guide
Updated 3 months ago1
Create Doc Home Page
Updated 3 months ago1
Umbrella Issue: CNCF Tech Doc Recommendations
Updated 4 months ago1
Discuss the overlap and comparison with IETF's RATS framework
Updated 5 months ago6
Potential grammatical error
Closed 6 months ago4
Tag v1.0 of the spec
Closed a year ago1
Address remaining review comments from @trishankkarthik
Closed a year ago4
JSON parsing differences can make the same signature verify for different payloads
Updated a year ago1
expiration date might prevent installation
Updated a year ago3
missing key management
Closed a year ago2
pattern matching syntax for artifact rules is undefined
Closed a year ago3
expected python in-toto to consume 'REQUIRE' layout item.
Closed a year ago8
key format specification is inconsistent
Closed a year ago5
"other_headers" field in "signatures" field in reference implementation is not part of the spec
Closed a year ago10
Differences between the in-toto implementations and the specification
Closed a year ago3
Pseudocode for MATCH rule indicates that source and destination patterns can be distinct
Closed a year ago1
Change expiration check to match TUF
Closed a year ago4
Ambiguous rule set: `ALLOW foo` while `DISALLOW *` is also a rule
Closed a year ago1
Document media/MIME type of in-toto payloads
Closed a year ago2
Diagrams that show up in various places are not viewable in darkmode.
Closed a year ago1
PDF Generation Instructions
Closed a year ago1
Broken Hyperlinks in in-toto-spec.pdf
Closed 2 years ago1
would be nice to point to live website docs from README
Closed 2 years ago7
in-toto-spec.md: missing table of contents
Closed 2 years ago
Support ecdsa key-type for commands
Closed 2 years ago1
"keys" JSON format described in spec does not match reference implementation output
Closed 3 years ago1
Update provided PDF
Closed 3 years ago1
in-toto-spec.md: Missing product in 5.3.2 example
Closed 3 years ago1
Document "artifact rule" rationale
Updated 3 years ago7
What's an SCC?
Closed 3 years ago6
Problem with conflicting rules
Updated 4 years ago
Revisit artifact rule path patterns
Updated 4 years ago
Inconsitencies between the in-toto specification and reference implementations: to `_name` or to `name`, that is the question
Closed 4 years ago4
Resolve documentation inconsistency in number of signing methods supported.
Closed 4 years ago
Verify target files of final product without inspection
Updated 4 years ago12