dynamic_repo_secure

Secure

ONLY FOR remote.type=="dynamic_repo"

To confirm that the update in your resource pack was released by you, the mod supports OpenPGP Verify (mainly for hosts where you are not the owner.)

If you don't need it

Enable this flag. dynamicmapack.json

{
  [...]
  "remote": {
    [...]
    "sign_no_required": true
  },
  "formatVersion": 1
}

If you need it --- Client-side

dynamicmapack.json

{
  "current": {"build": 10},
  "remote": {
    "type": "dynamic_repo",
    "url": "https://raw.githubusercontent.com/.......",
    "public_key": "mQINBGX1HNIBEACnBGMXslyy4jYlFVyHEY......."
  },
  "formatVersion": 1
}

You need to generate a key pair using the gpg program. And insert the public key without headers and footers

-----BEGIN PGP PUBLIC KEY BLOCK-----
Comment: ......
.....

mQGNBGXvaiABDA....               <----- ALL THIS BASE64 TEXT
-----END PGP PUBLIC KEY BLOCK-----

Server-side

Sign dynamicmcpack.repo.json with this key pair, the signature file should be nearby and called dynamicmcpack.repo.json.sig (is a binary file ⚠️)

Done

Good look!