[go: up one dir, main page]
Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Inline payload manifest.payload.value #18

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Inline payload manifest.payload.value #18

wants to merge 1 commit into from

Conversation

arkavo-com
Copy link
@arkavo-com arkavo-com commented Jul 14, 2023 •
edited by pflynn-virtru
Loading

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 is more email-based solution.

{
    "payload": {
        "type": "inline",
        "url": "",
        "protocol": "base64",
        "isEncrypted": true,
        "schemaVersion": "3.1.0",
        "mimeType": "text/plain",
        "value": "nF0zMXcMmkU4hmSugL2/KQz8BUUosMY0PDEioTp0lnZGM+epTZsB"
    },
    "encryptionInformation": {
        "type": "split",
        "keyAccess": [
            {
                "type": "wrapped",
                "url": "http://localhost/api/kas",
                "protocol": "kas",
                "wrappedKey": "M7GGpjpTsSNclmmW9Oa94N9Qy/+QI9iTWXdUgmFT1NWClIZrKEl/Au13nVBDg+P9KympzVZgpHQv8JA1T8GckkFmGbVwc/fFW9OA90aJc0dsUo5ezewgrvd6DOWUskexoxK1o8Xag/fBoLReK3iysvEcPbwTwvhvVEpuS6CpsriQ3hW/PXmGysera/YkRyYMT395ty2MAnfvQJnEssw21l0cpDC7CDU7cR0KCFEvZKW4UBy/zC73JZZk7GoRCbkXBaoyX6snzg22eXy9pG+s+R+X7SEkUduqfxYY7EQkEoOFK7aroqmGcsDaxUQaZYiLY3cwSFCOPtkQJL6X4cB1xA==",
                "encryptedMetadata": "eyJjaXBoZXJ0ZXh0IjoiRDlGM0VIeTB4dXkwQU80OFBZTXc3UkI5Y3FTeC9ZVHdwcTZtR1M1cyIsIml2IjoiRDlGM0VIeTB4dXkwQU80OCJ9",
                "policyBinding": "MzA0NGFjM2ViYzliYWU1ODg4Yjg2MDM1ZWZiZTIzYjJlN2U4Y2YyZTdjOWEwMjZlZDg1YTQwYjg0YTk4NzFjZg=="
            }
        ],
        "method": {
            "algorithm": "AES-256-GCM",
            "isStreamable": true,
            "iv": "D9F3EHy0xuy0AO48"
        },
        "integrityInformation": {
            "rootSignature": {
                "alg": "HS256",
                "sig": "ZmNjOTc4Y2VkZWM3Yjg4NWQ4MTkzMzg0NTU2N2M3YWUxMGUyOWUxYWFjNWFiNDY3NzNiZmNmNjJhOTI3N2FmOA=="
            },
            "segmentHashAlg": "GMAC",
            "segments": [],
            "segmentSizeDefault": 1048576,
            "encryptedSegmentSizeDefault": 1048604
        },
        "policy": "eyJ1dWlkIjoiYjU4ZmY0ZDQtNjc2OC00ODRlLWJjMzEtMjEwYjU0YmYxY2I4IiwiYm9keSI6eyJkYXRhQXR0cmlidXRlcyI6W10sImRpc3NlbSI6W119fQ=="
    }
}

Checklist

  • A clear description of the change has been included in this PR.
  • A clear description of whether this change is a Major, Minor, Patch or cosmetic change as per the Versioning Guidelines has been included in this PR.
  • All schema validation tests have been updated appropriately and are passing.
  • MAJOR/MINOR VERSION CHANGES ONLY: This PR should be made in branches prefixed with draft-<change>
  • MAJOR/MINOR VERSION CHANGES ONLY: A link to a reference implementation (PR or set of PRs) of the change has been included in this PR.
  • MAJOR/MINOR VERSION CHANGES ONLY: A writeup has been included discussing the motivation and impact of this change.
  • MAJOR/MINOR VERSION CHANGES ONLY: The minimum wait time has elapsed.
  • DRAFT MERGE ONLY: Draft Semver has been updated in the VERSION file (optional)
  • DRAFT MERGE ONLY: Tagged this branch with new semver version and an annotation describing the change (ex: git tag -s 4.1.0 -m "Spec version 4.1.0 - did a thing")
  • DRAFT MERGE ONLY: Version numbers have been updated as per the Versioning Guidelines.
  • This change otherwise adheres to the project Contribution Guidelines.

@strantalis
Copy link
Member

I like the idea here. I don't see why this couldn't be used for an email flow either potentially if there are no attachments.

@arkavo-com arkavo-com marked this pull request as ready for review June 6, 2024 17:41
@arkavo-com arkavo-com requested a review from a team as a code owner June 6, 2024 17:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@arkavo-com @strantalis