aboutsummaryrefslogtreecommitdiffstats
path: root/crypto/pgpainless/src/main/kotlin/app
AgeCommit message (Collapse)AuthorFilesLines
25 hoursbuild(deps): update Bouncy Castle to 1.86 and PGPainless to 1.7.8Danilo M.3-12/+5
Bouncy Castle 1.78.1 is affected by GHSA-574f-3g2m-x479, GHSA-9pwp-9qqc-pr26, GHSA-c3fc-8qff-9hwx and GHSA-qp49-qgx5-5m26, all fixed by 1.85. PGPainless 1.7.8 is the newest 1.x release. A root resolution rule keeps every Bouncy Castle module on the catalog version; before, bcpg 1.77 shipped next to bcprov 1.78.1. The new stack decrypts the OCB (LibrePGP) packets GnuPG 2.3+ emits by default, which the old one rejected as "non-standard AEAD". Drop the NonStandardAEAD error, its bottom sheet and strings, and replace the mislabelled aead_* fixtures (SHA-1 self-signed keys plus a message encrypted to an unrelated key) with a real GnuPG 2.5 key and OCB message that the tests now decrypt. The new fixture is a throwaway test key, so it is allowlisted in .gitleaksignore by fingerprint. Fix KeyUtils.isKeyUsable, which compared a Boolean to null and so accepted every key that parsed, including keys with no encryption subkey. A signing-only key fixture now covers the rejection path. Also: migrate the removed SelectUserId.firstMatch and deprecated addDecryptionPassphrase APIs, keep one copy of the Bouncy Castle META-INF/LICENSE.md in the APK, and move the existing InvalidPackage lint baseline entries to the bcpkix 1.86 jar. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2024-09-28Reapply "refactor: use `Closeable#use` extension where applicable"Harsh Shandilya1-4/+2
This reverts commit 04f4b9804f10e4724bac22d40bf01711ff708533.
2024-09-26Revert "refactor: use `Closeable#use` extension where applicable"Harsh Shandilya1-2/+4
This reverts commit 69513bf24613d4ba540bcdeaffe04dc9330a65a4.
2024-09-22refactor: use `Closeable#use` extension where applicableHarsh Shandilya1-4/+2
2024-08-14chore: add missing copyright headers and update existing onesHarsh Shandilya7-5/+15
2024-07-30fix null pointer exception when using public only keys (#3143) (#3144)Greg Renda1-1/+1
Co-authored-by: Greg Renda <greg@renda.org>
2024-05-28chore: reformat with trailing commas changesHarsh Shandilya3-12/+6
2024-05-27feat(pgpainless): add detection for passphrase-less messages (#3069)Harsh Shandilya1-0/+11
* WIP: feat(pgpainless): add detection for passphrase-less messages * refactor: test keys instead of the message This makes more logical sense
2024-05-25fix(pgpainless): remove incorrect checkHarsh Shandilya1-5/+0
I don't believe this ever made sense to check in the decryption phase
2024-04-14fix: special-case AEAD failureHarsh Shandilya1-0/+9
Fixes #2974 Fixes #2963 Fixes #2921 Fixes #2924 Fixes #2653 Fixes #2461 Fixes #2586 Fixes #2179
2023-12-27Revert "fix: check if passphrase is necessary before asking for it"Harsh Shandilya2-14/+0
Didn't fix the issue. This reverts commit d8f76b33e9ea74eb567a115dd63559f6b27b2fce.
2023-12-25fix: check if passphrase is necessary before asking for itHarsh Shandilya2-0/+14
Updates #2836
2023-09-28refactor: use `runSuspendCatching` from `kotlin-result`Harsh Shandilya1-1/+1
2023-08-10refactor: un-flatten module structureHarsh Shandilya7-0/+541