[
https://issues.apache.org/jira/browse/JSPWIKI-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18044814#comment-18044814
]
Alex O'Ree commented on JSPWIKI-205:
------------------------------------
i think the easy solution to this is to provide an easy to override method that
would enable encryption or decryption or whatever when something is read or
written from disk or database. That way you can provide your own encryption
mechanism, keyloading etc. If we try to bake it in, someone will always not
like it. So the work for something that wants to encryption is to extend the
File or Database provider, override a method or two, compile, add to classpath,
update the jspwiki-custom.properties and fire it up.
> Obfuscate on disk content type
> ------------------------------
>
> Key: JSPWIKI-205
> URL: https://issues.apache.org/jira/browse/JSPWIKI-205
> Project: JSPWiki
> Issue Type: Improvement
> Components: Core & storage
> Reporter: Chris Lialios
> Priority: Trivial
> Attachments: BasicOverview.doc, BasicOverview.docx,
> EncryptingProviderSource.zip, encryption.patch, encryption.patch,
> encryption.patch, encryption.patch
>
>
> We would like to store passwords within the wiki pages.
> Securing the page is trivial, however the contents on disk remain clear text.
> It would be very nice to have a page type that could be stored in an
> obfuscated form on disk.
> As an addition have a secondary password to display/edit the encrypted
> contents on disk for those who do not want to use wiki security on the page.
> I suspect this will have potentially drastic effects on the revisions
> process, but it would be a small price to pay for security.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
