Hi Devs & Users,
With the new refactoring of officeimporter module, it's possible to
implement a generic office document converter on top of
xwiki-officeimporter. By a "document converter" I meant an xwiki application
where you can upload a .doc file and get it converted to a .pdf, .odt etc.
Supported formats will be those mentioned in
http://artofsolving.com/opensource/jodconverter/guide/supportedformats and
few more Office2007 formats.
Would this application be a good addition to XWiki?
Thanks.
- Asiri
PS: It would take about 2-3 days to fully implement and test the
application.
Hi,
I asked Vincent if there was a security how-to / checklist page in the xwiki
user guide and as such this does not yet exist.
As security is such an important issue for public-facing sites, coupled with
the fact that in order to help those who have to ensure they can carry out
necessary due diligence on security before they are allowed to adopt
solutions such as Xwiki, I'd like to request the help of the community to
gather knowledge and best practices together.
This thread is a request to gather information from experts and users alike
to then create pages in the user guide that provide security guidance for
administrators of public-facing Xwiki deployments... where applicable we
could link to security how-tos for Xwiki dependencies such as web
application servers rather than duplicate well known information, feel free
to share links you would recommend, please.
Some of the questions I'm interested in are...
* how-to 'harden' a xwiki site
** such as the correct access permissions for each file / folder object and
permission lifecycle
* what other dependencies should we ensure we have 'hardenend'
** such as Tomcat, Jetty, the DBs etc... and 'links to' or 'sub-pages in the
wiki' on the essential tasks to carry out
* ensuring the prevention of common attacks such as cross-site scripting and
sql-injection
** is there a test suite we could use or introduce, such as Ronin written in
Ruby, that would help us test that both xwiki and community plugins meet
security standards we aim to achieve?
There are various groups that focus on aspects of security we can study for
guidance such as:
http://www.owasp.orghttp://www.cloudsecurityalliance.org/guidance/
Please feel free to suggest others you feel offer professional and
insightful guidance.
Also, perhaps of interest is an example of a good working security team, I
tip my hat to the Drupal security team who do an excellent job and here's an
interesting post on that subject from the founder of Drupal:
http://buytaert.net/drupal-security-team-past-current-and-future
Thanks for reading and I sincerely hope this is of interest to the wider
community of Xwiki and helps to gain further adoption and success for the
Xwiki project.
--
View this message in context: http://n2.nabble.com/Security-best-practices-for-Xwiki-deployment-and-manag…
Sent from the XWiki- Users mailing list archive at Nabble.com.
Hi everyone,
Just a quick note to wish everyone in the XWiki project very happy
festivities and a happy next year for 2010.
The XWiki project has seen exciting times in 2009 as described on:
http://massol.myxwiki.org/xwiki/bin/view/Blog/XWikiIn2009
Let's all make 2010 even better :)
Take care,
-Vincent
Hello,
The icon (then pen) indicating the section editing appears even on pages
on which the only right access is "view".
I am sure that the users have no rights to "edit" these pages.
The parameter in xwiki.cfg is configured like that :
xwiki.section.edit=1
I have XWiki Entreprise 2.0.
How can I do to hide this icon ?
Thanks,
S.A
Hi all,
I've done a mistake: Renaming a (blog) page to a page having a "/" in the name: "AB5 / CD6".
The page is listed in the blog overview and in the document index. However I am not able to access / delete / rename that page.
I am using 2.1.1.
Any hints? (except exporting the wiki, deleting it from that file - it's a subdirectory within that file, dropping wiki and importing it again)
Thanks
mb
... and by the way: Thanks to all for that great version 2! Merry Christmas and a lot of fun & success in 2010
We are posting a string of name=value pairs seperated by
ampersands with a className property at the end set to the type of
xwiki class that we would like to create.
The object of the correct type is getting created and attached to the page however all of the fields in that object are empty.
What is the correct format needed to post the name=value pairs?
What is the significance of the "property#" bit in the object resources section of the restfulapi doco (http://platform.xwiki.org/xwiki/bin/view/Features/XWikiRESTfulAPI). Do the name=value pairs need to be prefixed with "property#"?
Radek Rekas
VFMFocus Developer
eVALUA Pty Ltd
66B Maryborough St
Fyshwick, ACT, Australia
T: +61 2 6228 1904
F: +61 2 6228 1131
Http://www.evalua.com.au
When using a field named "title" in a live table the caption for that field in the livetables header displays as "Browser Title Bar Text". If I change the name for that field then it displays correctly.
Is this is a bug or are there reserved names that cant be used as fieldnames in livetables?
Below is the macro code that I am using to create the livetable:
#set($collist = ["council", "region","title", "description"])
#set($colprops = {
"council" : { "type" : "list" , "size" : 1, "link" : "view"},
"region" : { "type" : "text" , "size" : 10, "link" : "view"},
"title" : { "type" : "text" , "size" : 20, "link" : "none"},
"description" : { "type" : "text" , "size" : 10, "link" : "none"}
})
#set($options = {
"className":"Tenders.TendersClass",
"tagCloud" : true,
"rowCount": 10
})
#livetable("Tenders" $collist $colprops $options)
Radek Rekas
I am out of the office until 01/04/2010.
I will have limited access to email. If this is an emergency, please call
my cell phone. Merry Christmas and Happy New Year!
Note: This is an automated response to your message "users Digest, Vol 29,
Issue 58" sent on 12/22/09 5:54:13.
This is the only notification you will receive while this person is away.