spec
spec copied to clipboard
opentdf
Trusted Data Format (TDF) is an Open, Interoperable, JSON encoded data format for implementing Data Centric Security for objects (such as files or emails) in zero-trust security world. This repository...
### Proposed Changes * Adds Identifier to Protocol Enum * Require Identifier in KAS Resource Locator ### Checklist - [ ] A clear description of the change has been included...
Policy tables were referencing remote policy despite the lack of context or incorrect statements. Implementation of nanoTDF utilized the nanoTDF diagram which denotes the difference in payload size. - fix...
### Proposed Changes * ### Checklist - [ ] A clear description of the change has been included in this PR. - [ ] A clear description of whether this...
### Proposed Changes * Adds Key Identifier section and references from KAS Payload and Policy Key sections * KAS section is now called KAS Key Identifier ### Checklist - [...
### Proposed Changes * Policy Key Access required with encrypted Policy * https://github.com/opentdf/platform/issues/900 ### Checklist - [ ] A clear description of the change has been included in this PR....
### Proposed Changes To better support web-based JSON APIs, inline payload in the TDF manifest. `manifest.payload.value` `zip` is a heavy operation that only works to create a "container" and IMO...
### Proposed Changes * This allows both copies and spits for keys. * Adds a section on how they are to be used, with samples ### Checklist - [ ]...
1. Right now, TDF uses an RSA keypair for wrapping. 2. EC is smaller, faster, and more secure than RSA - TDF should use EC keys, there is no good...
In the current opentdf implementations for `c++` and `javascript` it seems like we are double encoding the signatures. The spec for the root signature and policy binding it only mentions...
This is another spot where we seem to be double encoding with `hex` and `base64` but the spec and the actual current implementations don't currently align again. It seems that...