chore: bump openpgp from 5.0.0 to 5.10.1 in /.github/actions/build-rpm

[dependabot]

Bumps openpgp from 5.0.0 to 5.10.1.

Release notes

Sourced from openpgp's releases.

v5.10.1

Reject cleartext messages with extraneous data preceeding hash, addressing: GHSA-ch3c-v47x-4pgp.

v5.10.0

• crypto-refresh: add support for new Ed25519/X25519 keys, signatures and messages (#1620)
• Support parsing encrypted key with unknown s2k types or cipher algos (#1658)
• Fix forward compatibility of keys, SKESKs, and detached/cleartext signatures and ECDH (#1656)

This release does not include any breaking changes.

Full Changelog: openpgpjs/openpgpjs@v5.9.0...v5.10.0

v5.9.0

• Add support for verifying User Attributes in verifyAllUsers (#1637)
• Allow email addresses with trailing numbers in domain (#1642)
• TS: add declaration for verify with CleartextMessage input (#1640)
• Add revoke to Subkey in type definition (#1639)

v5.8.0

• Add additionalAllowedPackets config option, to allow parsing packets that are not usually expected/allowed in a given context (openpgpjs/openpgpjs#1618)
• Fix shorthand check on user revoked status in getPrimaryUser method (openpgpjs/openpgpjs#1623)
• Run Sequoia's OpenPGP interoperability test suite in CI, to catch interoperability regressions (openpgpjs/openpgpjs#1603)

v5.7.0

• Add support for creating critical signature subpackets (openpgpjs/openpgpjs#1599)
  • Most subpackets are now assigned a criticality based on whether failing to interpret their meaning would negatively impact security.
  • If subpackets that are now marked as critical (such as signature creation date, issuer Key ID, key expiration time if set, etc.) are not supported by another OpenPGP implementation, it will now be considered invalid by the implementation rather than ignored. However, since these subpackets are fundamental to the functioning of OpenPGP, they should indeed never be ignored. If an implementation doesn't support them, please upgrade or report it to the relevant implementation as well as or instead of here.
  • For Notation Data subpackets, the caller can now set their criticality using the signatureNotations[*].critical property. When set to critical, if the OpenPGP implementation reading the signature doesn't understand their meaning, they will be rejected rather than ignored. This is useful if the notation is indeed critical (:slightly_smiling_face:) to the functioning of the signature or the key that contains it.
• Remove default known notations (openpgpjs/openpgpjs#1600)
  • Since OpenPGP.js doesn't interpret any notations, we shouldn't consider any of them "known" by default. Rather, we let the calling application indicate the known notations, and it is then responsible for handling them.
  • Specifically, signatures with a critical notation named "[email protected]" or "[email protected]" will now be rejected by default. We believe that these are not common "in the wild", but if you encounter them, you can add them to the config.knownNotations array, or (preferably) pass a knownNotations array in the config property when verifying a signature, and then handle the preference indicated by the notation data afterwards by inspecting the signaturePacket.notations or rawNotations property.
• TypeScript: added selfCertification property to the PrimaryUser interface definition (openpgpjs/openpgpjs#1594)
• Docs: mark global generateSessionKeys's encryptionKeys parameter as optional (openpgpjs/openpgpjs#1596)
• CI: Update browser targets (openpgpjs/openpgpjs#1549)
• Update ESLint and other minor dependencies; clean up linting rules (openpgpjs/openpgpjs#1602)

v5.6.0

• Allow use of Brainpool curves by default (openpgpjs/openpgpjs#1563)
  • These curves were added back to the crypto refresh of the OpenPGP standard, so we allow them by default again, but please note that their implementation is not constant-time (openpgpjs/openpgpjs#720), so their use is still discouraged in favor of Curve25519.
• Add revoke method to User (openpgpjs/openpgpjs#1584)
• Add support for creating Notation Data subpackets when signing or encrypting messages (openpgpjs/openpgpjs#1598)
• Add RawNotations Type to type definitions (openpgpjs/openpgpjs#1571)
• Adding missing functions in SubKey class type definition (openpgpjs/openpgpjs#1588)
• TypeScript: fix signature of armor function (openpgpjs/openpgpjs#1576, openpgpjs/openpgpjs#1585)
• TypeScript: fix SymEncryptedSessionKeyPacket type name (openpgpjs/openpgpjs#1583)
• Docs: add typescript setup notice (openpgpjs/openpgpjs#1586)
• Docs: clarify Key.clone() behaviour (openpgpjs/openpgpjs#1589)
• CI: move away from Node.js v12 (openpgpjs/openpgpjs#1568)
• Remove internal, unused RandomBuffer (openpgpjs/openpgpjs#1593)

... (truncated)

Commits

• 5d02e3a 5.10.1
• 6b43e02 Merge pull request from GHSA-ch3c-v47x-4pgp
• 11b5999 Reject cleartext messages with extraneous data preceeding hash header
• 4df86e5 5.10.0
• 8d4dd34 Merge pull request #1620
• 5ae2846 CI: test on iOS Safari 14 instead of 15 to have access to SubtleCrypto
• b164190 Internal: rename Curves to CurvesWithOID
• ef953ce Add HKDF fallback for Node 14, where SubtleCrypto is not available
• ee4ad89 Enforce AES with PKESK v3 using x25519 (new format)
• 1c07d26 crypto-refresh: add support for new X25519 key and PKESK format
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by larabr, a new releaser for openpgp since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[sonarcloud]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud