[ https://issues.apache.org/jira/browse/JSPWIKI-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14138431#comment-14138431 ]
Craig L Russell commented on JSPWIKI-205: ----------------------------------------- I'm no expert on this subject, but it seems from an architecture perspective that a filter is the better solution. I don't know of many cases where the markup for a page should be encrypted. So I'd rather see a more general purpose filter that encrypts the variable content even at the risk of exposing the fixed content with no encryption. As to the packaging, I'm a fan of providing the interface and a no-encryption filter in core that can be substituted by an encrypting filter. I seem to recall that providing an encrypting filter would require some registration for export controls. > 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)