chore(deps): Bump openpgp from 5.11.1 to 6.0.0

[dependabot]

Bumps openpgp from 5.11.1 to 6.0.0.

Release notes

Sourced from openpgp's releases.

v6.0.0

What's Changed

OpenPGP.js v6 adds support for the new version of the OpenPGP specification, RFC 9580. It also increases compliance with the specification, as demonstrated by the OpenPGP interoperability test suite.

OpenPGP.js v6 only makes minor API changes. This is the first stable release of OpenPGP.js v6: no more breaking changes to the high-level API will be made until the next major release.

For the changes since the previous pre-release (v6.0.0-beta.3.patch.1), see the end of this message. Here we list a summary of the main changes since v5:

Platform support changes

• The library is now declared as a module (type: module in package.json), and declares exports, alongside the legacy package.json entrypoints, which should ensure backwards compatibility. Still, bundlers might be affected by the package.json changes depending on how they load the library.
• Node.js:
  • Drop support for Node.js versions below 18 (OpenPGP.js v5 supported Node.js v14 and above).
  • Streaming: drop support for native Node Readable stream: require passing Node Web Streams (#1716)
• Web:
  • Require availability of the Web Crypto API's SubtleCrypto (insecure contexts are no longer supported, as SubtleCrypto is not available there)
  • Require availability of the Web Streams API, since it's now supported in all browsers (applications can load a polyfill if they need to support older browser versions: see README.
  • Require availability of native BigInts (not supported by e.g. Safari 13 and below, see full compatibility table)
  • Argon2 has been added as S2K algorithm (on all platforms). For performance reasons, the implementation relies on a WASM module, thus web apps might need to make changes to their CSP policy in order to use the feature. Alternatively, since the Argon2 WASM module is only loaded if needed, apps can manually reject password-encrypted messages and private keys which use Argon2 by checking e.g. SymEncryptedSessionKeyPacket.s2k?.type === 'argon2' or SecretKeyPacket|SecretSubkeyPacket.keyPacket.s2k?.type === 'argon2'.

Breaking API changes

• Ensure primary key meets strength and algo requirements when encrypting/verifying/signing using subkeys (#1719)
• read[Private]Key: support parsing key blocks (return first parsable key); previously, parsing would fail if a block with more than one key was given in input (#1755)
• PrivateKey.getDecryptionKeys will now throw if no decryption key is found (#1789). Previously, an empty array was returned. As a consequence of this change, some openpgp.decrypt errors will be more specific.
• Refuse to use keys without key flags (see config.allowMissingKeyFlags below)
• Randomize v4 and v5 signatures via custom notation (#1737): while this notation solution is interoperable, it will reveal that the signature has been generated using OpenPGP.js, which may not be desirable in some cases. For this reason, the option config.nonDeterministicSignaturesViaNotation (defaulting to true) has been added to turn off the feature.
• AEAD-encrypted v4 keys from OpenPGP.js v5 or older (namely keys generated without .v5Keys flag and encrypted with config.aeadProtect = true) cannot be decrypted by OpenPGP.js v6 (via decryptKey) out-of-the-box (see config.parseAEADEncryptedV4KeysAsLegacy below) (#1672)
• Parsing of v5 keys and v5 signatures now requires turning on the corresponding config flag (see config.enableParsingV5Entities below). The affected entities are non-standard, and in the RFC 9580 they have been superseded by v6 keys, v6 signatures and SEIPDv2 encrypted data, respectively. However, generation of v5 entities was supported behind config flags in OpenPGP.js v5, and some other libraries, hence parsing them might be necessary in some cases. (#1774 , #1779)

Configuration changes

• RFC 9580 has updated parts of the draft RFC 4880bis as implemented by OpenPGP.js v4 and v5. Related changes in v6 are:
  • Drop the config.v5Keys flag and corresponding key generation. The flag is replaced by .v6Keys, and results in a different key format.
  • The config.aeadProtect flag has a different effect than in v5:
    • for private keys, a new encryption mechanism is used;
    • for password-encrypted messages, a new message format is used;
    • when encrypting messages to public keys, the flag is ignored (see openpgpjs/openpgpjs#1678).
  • Add config.parseAEADEncryptedV4KeysAsLegacy to allow decrypting AEAD-encrypted v4 keys from OpenPGP.js v5 or older (namely keys generated without .v5Keys flag and encrypted with config.aeadProtect = true) (#1672).
  • Add config.enableParsingV5Entities to enable parsing support for v5 entities (openpgpjs/openpgpjs#1774 , #1779)
• Add config.allowMissingKeyFlags to bypass the missing key flag check (see openpgpjs/openpgpjs#1677)
• Drop config.minBytesForWebCrypto, and always use WebCrypto if available, since there is no longer a performance overhead for small messages.
• Rename EdDSA-related enums following the standardization of new key formats:
  • Drop enums.publicKey.eddsa in favour of enums.publicKey.eddsaLegacy
  • Rename string value of enums.curve.ed25519Legacy to 'ed25519Legacy' (was: 'ed25519')
  • Rename string value of enums.curve.curve25519Legacy to 'curve25519Legacy' (was: 'curve25519')
• Rename config.useIndutnyElliptic to .useEllipticFallback, to reflect the change of underlying library.
• Remove enums.symmetric.plaintext (internally unused)
• Rename NIST curves to disambiguate the names with the Brainpool curves (#1721).:
  • the identifiers enums.curve.p256, .p384, .p521 are now marked as @deprecated (to be dropped in the main release)

... (truncated)

Commits

• dd01ee0 6.0.0
• a5645e1 Spaces after "RFC" in README
• 0980074 Document required Web Crypto support in README
• 31a7e26 Merge pull request #1629 from openpgpjs/v6
• 42d504a Switch to SHA512 as default preferred hash algo (`config.preferredHashAlgorit...
• fb72ea4 Merge pull request #1802
• f9a3e54 openpgp.sign: add recipientKeys option to get the signing prefs from
• d3e75de openpgp.encrypt: use encryptionKeys to determine preferred hash algo when...
• 12274a1 Update README [skip ci]
• 0138b69 CI: update Browserstack project id to include target branch
• 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 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)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 91.29%. Comparing base (f183353) to head (52dd228).

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #277      +/-   ##
==========================================
- Coverage   93.22%   91.29%   -1.94%     
==========================================
  Files          32       32              
  Lines        7429     7429              
  Branches      453      445       -8     
==========================================
- Hits         6926     6782     -144     
- Misses        503      638     +135     
- Partials        0        9       +9     

Flag	Coverage Δ
packages	91.29% <ø> (-1.94%)	⬇️

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

see 14 files with indirect coverage changes

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f183353...52dd228. Read the comment docs.