build(deps): bump openpgp from 5.5.0 to 5.7.0

[dependabot]

Bumps openpgp from 5.5.0 to 5.7.0.

Release notes

Sourced from openpgp's releases.

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 "preferred-email-encoding@pgp.com" or "pka-address@gnupg.org" 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)

Commits

• c60f2e3 5.7.0
• bb0c1f8 Merge pull request #1602 from larabr/update-deps-feb23
• 8ffd7aa Remove import cycles
• 94868e6 ESLint: drop unnecessary rules
• 705f238 Update ESlint
• 1b17132 Update deps
• 080b49a Merge pull request #1549 from larabr/test-update-karma-browsers
• 0ffcc49 Remove default known notations (#1600)
• 6684482 Skip native Crypto tests if native lib is not available
• dcd28fa CI: test latest Safari
• Additional commits viewable in compare view

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 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)

[codecov]

Codecov Report

Merging #924 (d5dc0c5) into main (83bb3d0) will increase coverage by 0.58%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #924      +/-   ##
==========================================
+ Coverage   95.32%   95.90%   +0.58%     
==========================================
  Files           4        4              
  Lines         171      171              
  Branches       49       49              
==========================================
+ Hits          163      164       +1     
+ Misses          8        7       -1     

Flag	Coverage Δ
demo	80.00% <ø> (ø)
macos-latest	95.90% <ø> (+0.58%)	⬆️
script	97.43% <ø> (+0.64%)	⬆️
ubuntu-latest	95.90% <ø> (+0.58%)	⬆️
version	80.00% <ø> (ø)
windows-latest	95.90% <ø> (+0.58%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
src/buildExec.ts	99.18% <0.00%> (+0.81%)	⬆️

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.