Skip to content

Manifest Hashes Format #162

Description

@ezzak

For the best possible security, you can optionally specify the path where the asset should exist. This allows you to prevent attacks where valid assets are used in the “wrong” position. Imagine swapping a “Yes” and “No” button, when asking “Should I share all messages publicly”, etc.

"hashes": {
  "/assets/x.html": "ca978112ca1bbdcafac231b39a23dc4da786eff8147c4e72b9807785afee48bb",
  "/assets/main.js": "fb8e20fc2e4c3f248c60c39bd652f3c1347298bb977b8b4d5903b85055620603",
  "/assets/css/main.css": "5e737a67c38189a01f73040b06b4a0393b7ea71c86cf73744914bbb0cf0062eb",
  // Allowed anywhere
  "": [
    "684ad58287ff2d085927cb1544c7d685ace897b6b25d33e46d2ec46a355b1f0e",
    "3431742b9dbff1751bba9ba47483ed62ae7fdf42d560a480a282af38b6c8de0a",
    "f802517f1b2406e308599ca6f4c02d2ae28bb53ff2a5dbcddb538391cb6ad56a"
  ]
}

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions