MarcoFR/Ackbar:I've noticed this group, and think it's a great project. Unfortunatly they are so fresh, that their site doesn't contain much info.
In some ways intersting, I found this
link they provided to the PHP Manual Security pages, which displays the main problem with security and app development: [
the developer! Meaning, one can provide the best information, and still people wont implement, what has been pointed out.
DonXoops:And yes, no matter what we will be doing to the core, the vulnerability is with 3'rd party modules. Especially as people like myself, use XOOPS as means to teach themselves web application development skills.
Thankfully, two new XOOPS projects (at least this is the impression I have), will most likely assist us with this problem (eleviating most of the need for luck; we still need it though, to get the people together to take care of the accompaning workload
):
- Security Group
- Quality Control
To keep up a positivist attitude, I believe there are a couple of other things we could do.
1) on dev.xoops.org wiki, have a page dedicated to
"basic security measures" when developing, such as checking all input, never to use "Globals On", etc..., with a link placed amongst all those other "Manuals"
2) have a special forum on dev.xoops.org dedicated to security questions ("hey guys, could you look at this code, and point out any possible security risks?" "Ahh, this might be an offender" "Why" "well....." -> discussion)
Too often do dev's believe, thought once about security, job done. Reality suggests, that checking security is an ongoing issue, which is difficult to implement as dev, as our interest lays first with getting a certain task done, then we worry about how it looks and works, the period at which thoughts regarding security usually/might kick in.
There is no 100% security, but there is 100% security awareness, which we should strive for. And judging by this thread, we are on the right path