[
https://issues.apache.org/jira/browse/WICKET-7190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18105628#comment-18105628
]
ASF subversion and git services commented on WICKET-7190:
---------------------------------------------------------
Commit 2cc4c3b40a2c1b931955221a02629daccd2ec0c5 in wicket's branch
refs/heads/master from Emond Papegaaij
[ https://gitbox.apache.org/repos/asf?p=wicket.git;h=2cc4c3b40a ]
Merge branch 'crypt-unification'
Brings in WICKET-7190, which replaces the crypt subsystem with a single
scheme-based API. ICryptScheme and SchemeCrypt, backed by AES-GCM and
AES-GCM-SIV, take over from ICrypt/AbstractCrypt/SunJceCrypt in
wicket-util, from AESCrypt and the KeyInSession factories in wicket-core,
and from the pageStore ICrypter family. Encrypted pages are now bound to
their page id via AEAD associated data, and CryptoMapper encrypts
deterministically so resource URLs stay cacheable.
The only conflicts were four modify/delete pairs against 848fefaefb,
which had documented AESCrypt, AbstractJceCrypt, AbstractCrypt and
SunJceCrypt as unauthenticated and malleable. This branch removes all
four and replaces them with AEAD schemes, so the deletions were taken and
that javadoc goes with them. SECURITY.md merged cleanly; the scope and
reporting sections from master sit alongside the new page store and
deterministic-URL sections from the branch.
Note for anyone hitting a red build: japicmp is still configured to
compare against 10.0.0 and now fails for wicket-util and wicket-core on
the removed crypt API. Those removals are intentional for the 11 line,
and the baseline needs revisiting separately.
Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
> Unified cryptography API
> ------------------------
>
> Key: WICKET-7190
> URL: https://issues.apache.org/jira/browse/WICKET-7190
> Project: Wicket
> Issue Type: New Feature
> Components: wicket-core
> Reporter: Emond Papegaaij
> Assignee: Emond Papegaaij
> Priority: Major
> Fix For: 11.0.0
>
>
> The current cryptography API in Wicket is split over {{ICrypt}} and
> {{ICrypter}}. Both APIs serve a similar purpose but for different subsystems.
> The goal is to unify these APIs and to allow the implementation of more
> modern ciphers, with AEAD support. Also, the documentation on this API and
> its implementations must be improved, clearly stating what it does and what
> it does not deliver.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
