You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@wicket.apache.org by "Emond Papegaaij (JIRA)" <ji...@apache.org> on 2019/08/06 11:16:00 UTC

[jira] [Resolved] (WICKET-6559) Encrypted page store

     [ https://issues.apache.org/jira/browse/WICKET-6559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emond Papegaaij resolved WICKET-6559.
-------------------------------------
       Resolution: Fixed
    Fix Version/s: 9.0.0-M3
                   9

The implementation of the encryption was fine. The change I made was to move the SecureRandom to a singleton instance to prevent entrophy drain.

> Encrypted page store
> --------------------
>
>                 Key: WICKET-6559
>                 URL: https://issues.apache.org/jira/browse/WICKET-6559
>             Project: Wicket
>          Issue Type: New Feature
>          Components: wicket
>            Reporter: Emond Papegaaij
>            Assignee: Emond Papegaaij
>            Priority: Major
>             Fix For: 9, 9.0.0-M3
>
>
> To make it virtually impossible to tamper with any serialized data on disk, Wicket should encrypt the data with a key bound to the user session. This also prevents accidental leakage of sensitive data (such as passwords) via serialized form contents.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)