[jira] [Commented] (JSPWIKI-205) Obfuscate on disk content type
[ https://issues.apache.org/jira/browse/JSPWIKI-205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14140141#comment-14140141 ] Jürgen Weber commented on JSPWIKI-205: -- The JRE has all you need for encryption in Java. So, export restrictions problems are solved by Oracle, and not by any Java application vendor. A blowfish sample using only JRE classes: [http://www.java2s.com/Tutorial/Java/0490__Security/ABlowfishexample.htm] 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)
[jira] [Commented] (JSPWIKI-835) better mobile experience
[ https://issues.apache.org/jira/browse/JSPWIKI-835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14140443#comment-14140443 ] Jürgen Weber commented on JSPWIKI-835: -- The appearance on a mobile device can be tested with Chrome's [Device Mode|https://developer.chrome.com/devtools/docs/device-mode] better mobile experience Key: JSPWIKI-835 URL: https://issues.apache.org/jira/browse/JSPWIKI-835 Project: JSPWiki Issue Type: Improvement Components: Default template Affects Versions: 2.10 Reporter: Jürgen Weber Attachments: Screenshot_2014-03-26-22-55-48.png, Screenshot_2014-03-26-23-07-11.png Currently JSPWiki is not optimized for mobile devices, it looks the same on mobile as on desktop, with the effect, that the left menu and the tabs on top of the page look very small. JSPWiki should automatically recognise that it is accessed from a mobile device and format its output for mobile. see http://mail-archives.apache.org/mod_mbox/jspwiki-dev/201403.mbox/browser -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (JSPWIKI-835) better mobile experience
[ https://issues.apache.org/jira/browse/JSPWIKI-835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14140450#comment-14140450 ] Glen Mazza commented on JSPWIKI-835: For our small project, it would probably be better for JSPWiki to have a responsive theme (similar to those used by Bootstrap, Foundation, etc.) that will work reasonably well on each type of device, while still making sure it looks best for those using regular monitors or tablets, JSPWiki's primary use case. Device detection is a very messy art and if we went that route I believe it would engender countless JIRAs whenever we get it wrong for a particular device, which would be often, bringing down the project in the process. better mobile experience Key: JSPWIKI-835 URL: https://issues.apache.org/jira/browse/JSPWIKI-835 Project: JSPWiki Issue Type: Improvement Components: Default template Affects Versions: 2.10 Reporter: Jürgen Weber Attachments: Screenshot_2014-03-26-22-55-48.png, Screenshot_2014-03-26-23-07-11.png Currently JSPWiki is not optimized for mobile devices, it looks the same on mobile as on desktop, with the effect, that the left menu and the tabs on top of the page look very small. JSPWiki should automatically recognise that it is accessed from a mobile device and format its output for mobile. see http://mail-archives.apache.org/mod_mbox/jspwiki-dev/201403.mbox/browser -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (JSPWIKI-856) Enhance FileSystemProvider to be able to save page attributes as properties
[ https://issues.apache.org/jira/browse/JSPWIKI-856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Vittor updated JSPWIKI-856: - Attachment: providers.patch I think changing this to pageproperty is a good idea. I've made the change, updated some code to use TextUtil, added documentation to the ini/jspwiki.properties file and have attached a new patch. Enhance FileSystemProvider to be able to save page attributes as properties --- Key: JSPWIKI-856 URL: https://issues.apache.org/jira/browse/JSPWIKI-856 Project: JSPWiki Issue Type: New Feature Components: Core storage Affects Versions: 2.10.1 Reporter: David Vittor Priority: Minor Labels: provider Attachments: AbstractFileProvider.java, AbstractFileProvider.java, FileSystemProvider.java, FileSystemProvider.java, VersioningFileProvider.java, VersioningFileProvider.java, WikiPage.java, providers.patch, providers.patch, providers.patch, providers.patch *Requirements:* * 1. Plugins and other code should be able to store some page attributes into the properties of a page, just as author and changenote currently are. * 2. This should work for both FileSystemProvider and VersioningFileProvider and any future JDBCProviders or EncryptionProviders * 3. The properties added should be dynamic, e.g. all properties starting with @ like @likes, or @hitcount ** 3.1. A protected addCustomProperties() method should be done added * 4. The property names and property values should be validated ** 4.1. A protected validateCustomProperties() method should be done added ** 4.2 e.g. only contain ascii characters ** 4.3 Max property key length ** 4.4 Max property value length ** 4.5 Max number of properties -- This message was sent by Atlassian JIRA (v6.3.4#6332)
