feat(push): Optionally use OAEP padding#6139
Conversation
Co-Authored-By: Claude Opus 4.7 <[email protected]> Signed-off-by: Joas Schilling <[email protected]>
|
|
||
| private fun decryptSubject(privateKey: PrivateKey, base64DecodedSubject: ByteArray): ByteArray = | ||
| try { | ||
| val cipher = Cipher.getInstance("RSA/None/PKCS1Padding") |
|
APK file: https://github.com/nextcloud/talk-android/actions/runs/25114728585/artifacts/6710069920 |
|
✅ Confirmed via a test run on sermo |
mahibi
left a comment
There was a problem hiding this comment.
works fine for both OAEP and PKCS1.
No hard feelings regarding the order, also fine to avoid the warning and check OAEP first
Also use OAEPWithSHA-1AndMGF1Padding instead of RSA/ECB/OAEPPadding Signed-off-by: Marcel Hibbe <[email protected]>
|
APK file: https://github.com/nextcloud/talk-android/actions/runs/25159079583/artifacts/6727473090 |
🏁 Checklist
/backport to stable-xx.x