Symfony security concerns and other issues

Ian P. Christian's personal blog

Quicksearch

Calendar

Back July '08 Forward
Mon Tue Wed Thu Fri Sat Sun
  1 2 3 5 6
7 8 9 10 11 12 13
14 15 16 17 18 19 20
21 22 23 24 25 26 27
28 29 30 31      

Blog Administration


Trackbacks

No Trackbacks

Comments
Display comments as (Linear | Threaded)

I think you've raised a valid point. I think security reporting system would be a really good first step.

In regards to the *_dev.php files, I like ot have mine around from time to time, so I always add a security check...

http://www.steercms-project.org/trac/steercms/browser/steerCMSSandbox/trunk/web/dev.php

That way, only authorised people have access.
#1 Piers Warmers (Homepage) on 2008-05-14 01:23 (Reply)
I think we should discuss these issues on the dev mailing list. In fact, I think you should repost a most constructive version of this post to the mailing list.

Also, we do have weekly blog posts that show the changes, and if people have security concerns it is there responsibility to bring the issues up in the mailing list.

I do agree the symfony-project.com has had issues, but they are not issues with the framework its self, but rather server/network issues. I do agree we should have a static mirror available.
#2 Dustin (Homepage) on 2008-05-14 01:24 (Reply)
You're right that this should be brought up on the mailing list - but some of these issues already have.

I'll admit I'm playing the devil's advocate, but I really do think it's important that these issues are handled.

I don't think the mailing list is the right place for all security issues, but the right place for discussing where the right place to discuss it is!

There are 100s (1000s probably) of sites out there that run symfony - I run a few - and the uptime of those is very good. However when it comes to the main symfony website - it's very important for the image of symfony that it's up. It doesn't matter if its down due to symfony, or a disk failure - 24/7 monitoring should be in place making sure that we're not being let down by the site.
#2.1 Ian P. Christian (Homepage) on 2008-05-14 09:16 (Reply)
Wow, I did not imagine problems like that could exist in the framework. I totally agree with you there must be a system where people could find this usefull information.

(btw, i' m gonna patch right now some sites where that could be a completely dissaster )

Thanks.
#3 neonard0 on 2008-05-14 04:00 (Reply)
We had problems with the symfony project hosting in the past and we switched to another hosting company some time ago to provide a better service to the community (http://www.symfony-project.org/blog/2007/10/15/good-bye-azur-welcome-hippocampe). So, now we do have 24/7 monitoring in place. The reliability problems we had during the last 4 weeks were quite tricky to identify and solve. But the good news is that they have been solved last week and now that the server is stable, we will definitely post something on the blog to explain the issue. I think the reliability problem is now behind us.

As far as security or major problems are concerned, I'm with you. We need to be better organized and we really need more people to be involved in the core team. People like Dustin, Fabian, or Carl already do a tremendous amount of work with ticket qualification, bug fixing, patchs, new features implementation, ... but we need more.

On a side note, you have write access to the whole symfony repository, so feel free to fix such issues by yourself. Ticket #1617 has been fixed yesterday and Gregoire is going to release symfony 1.0.16 today with some explanation on the issue.

So, now, let's start a discussion on the dev mailing-list to improve the way the symfony community works.
#4 Fabien (Homepage) on 2008-05-14 10:09 (Reply)
The site has been up and down for me plenty this week and last. I thought it was a dodgy DNS at work - it seemed to work at home more - so glad it's not just me.

FWIW, a security portal or part of the project that specifically looks after security is a good idea. This could be Sensio, or they may be happy to farm it out to trusted members of the community (as you say, they are probably busy, so this might require volunteers).
#5 halfer on 2008-05-14 10:14 (Reply)
I'm a fan of the framework too, but they really need to get some hardened security guys in the team. Most open source seems to lack this and I think it would clamp down the shocking amount of vulnerabilities there are.
#6 Adult Ühler (Homepage) on 2008-06-30 16:10 (Reply)
Symfony's security history actually isn't that bad IMO.

Since my post a security team and reporting system has been implemented too.
#6.1 Ian P. Christian (Homepage) on 2008-06-30 16:12 (Reply)

Add Comment

Enclosing asterisks marks text as bold (*word*), underscore are made via _word_.
Standard emoticons like :-) and ;-) are converted to images.