[
https://issues.apache.org/jira/browse/JSPWIKI-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14138501#comment-14138501
]
David Vittor commented on JSPWIKI-205:
--------------------------------------
Hi Craig,
Thanks for the comment. My thinking is also towards the filter, especially as
being part of the core application. Custom "PageProviders" can always be
written for specific use cases.
I really like your idea of having a "no-encryption" as a default, which can be
substituted by another one. I'll add this.
"Export controls"?? - I didn't realize there was a way to export the wiki
content? That was going to be my next task to build an export mechanism for
getting the raw text pages, in a zip format, so it can be imported into a
different wiki.
> 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, EncryptingProviderSource.zip,
> 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
(v6.3.4#6332)