Hi Alex,
I didn't read the Microsoft Word document that was part of the JIRA but it
still seems rather like feature bloat. If someone wants to encrypt the wiki
page content (all or part of it) it would seem writing a SecurePageProvider
would be a better all around solution, i.e., just encrypt everything but
still provide the normal JSPWiki API so that versioning still works.
To some degree I guess I'm just reacting to requests for more features given
JSPWiki is already an enormous code base for a wiki application, about 219K
lines by my count. Earlier this year I wrote my own Spring Boot/Thymeleaf
wiki in about 70K lines. Of course it doesn't do everything JSPWiki does,
but it does support faceted search, themes, plugins and swappable backends.
OTOH, this doesn't sound like a lot of code, and it is marked Trivial priority.
Cheers,
Murray
On 24/08/2026 02:38, Alex O'Ree wrote:
If i recall correctly, the change set was to only add an api that is called
for encrypting or decrypting content with the default implementation that
does nothing. Everything else is left up for plugins/override
implementations.
On Sat, Aug 22, 2026 at 7:20 PM Murray Altheim <[email protected]> wrote:
I'm somewhat failing to see how this is an appropriate feature for a wiki,
and seems characteristic of feature bloat. If such a functionality is
needed by a specific user or community it would seem that this could be
developed as a Plugin or a PageProvider and installed locally, rather than
as a core feature delivered as part of JSPWiki.
The statement "I suspect this will have potentially drastic effects on
the revisions process, but it would be a small price to pay for security"
has an entirely true first clause, but the "small price to pay for
security"
is really overstated as the "security" is for a feature that has never been
a part of JSPWiki in the past, and is not in any way a security requirement
for using the application.
Cheers,
Murray
On 23/08/2026 04:24, Alex O'Ree (Jira) wrote:
[
https://issues.apache.org/jira/browse/JSPWIKI-205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex O'Ree resolved JSPWIKI-205.
--------------------------------
Resolution: Fixed
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
Assignee: Alex O'Ree
Priority: Trivial
Labels: pull-request-available
Fix For: 3.0.0
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)
--
...........................................................................
Murray Altheim <murray18 at altheim dot com> = = ===
http://www.altheim.com/murray/ ===
===
= =
===
In the evening
The rice leaves in the garden
Rustle in the autumn wind
That blows through my reed hut.
-- Minamoto no Tsunenobu
--
...........................................................................
Murray Altheim <murray18 at altheim dot com> = = ===
http://www.altheim.com/murray/ === ===
= = ===
In the evening
The rice leaves in the garden
Rustle in the autumn wind
That blows through my reed hut.
-- Minamoto no Tsunenobu
