| How Joomla 1.5.6 came about |
| Coordinator Blog | |||
| Written by Anthony Ferrara | |||
|
As most of you know, a critical security vulnerability affecting all Joomla versions below (and including) 1.5.5 was discovered on Tuesday, August 12th 2008. What most of you don't know, is what went on behind the scenes that day. A whole mass of people came together and immediately worked on all the tasks necessary to make 1.5.6 happen. Experiencing this first hand was quite amazing... Publishing a release is a process that normally has two weeks (and a team of people) devoted to it (for everything from selecting which remaining artifacts will be fixed, to translations, to clicking publish and everything in-between). This all happened in a VERY short time. Here's an abridged breakdown of how 1.5.6 came to be... 15:50 ESTBug Squad member Marijke Stuivenberg points the squad to a reported vulnerability in Joomla 1.5.5. 15:55 ESTBug Squad members Jennifer Mariott, Elin Waring, and Marijke (along with development coordinator Wilco Jansen, OSM Vice President Rob Schley and myself) verify that the vulnerability exists and the report is valid. 15:56 ESTAll available development Work Group members, Bug Squad members and Core Team members are notified of the issue. Bug Squad confirms that 1.5's SVN is stable and is ready for immediate release pending vulnerability fix. Forum moderators are informed of and asked to remove references of this issue until release. 16:05 ESTPatch is generated and provided to Bug Squad for testing/confirmation of fix. 16:20 ESTPatch is confirmed to fix vulnerability. Front page announcement is drafted. 16:30 ESTPatch is committed into SVN along with all preparations for release. Joomla 1.5 branch is frozen for release cycle. Bug Squad begins testing sanity and operation of SVN. 16:46 ESTSecurity announcement (on developer.joomla.org) is drafted. 17:20 ESTFront page announcement provided to translators. Joomlacode prepared for release. 17:30 ESTBug Squad confirms sanity of SVN and that all release preparations are in place. Package generation begins. 17:50 EST Full download packages generated. 18:05 ESTPackages provided to Bug Squad for validation and testing. 18:30 ESTBug Squad confirms package sanity, final steps before release are completed. 18:40 ESTFront Page article and Developer security report published. Full download packages released. 19:30 ESTAll patch downloads tested and published. Release cycle completed. ConclusionTotal time from report of vulnerability to initial release: 2 hours 50 minutes Total time from report of vulnerability to completion of release cycle completion: 3 hours 40 minutes Total number of people directly involved: between 20 and 30
|





Thursday, 11 December 2008
Monday, 01 December 2008
Did you notify the 200,000 website owners of the security problem?
Friday, 28 November 2008
Tuesday, 25 November 2008
Monday, 24 November 2008
saludos desde España
Friday, 14 November 2008
Thursday, 13 November 2008
Great versions.
Thanks
Wednesday, 12 November 2008
Monday, 10 November 2008
Nick
Monday, 10 November 2008
Thanks
Wednesday, 05 November 2008
(When will they publish the movie?)
Saturday, 01 November 2008
Thursday, 30 October 2008
Wednesday, 15 October 2008
Saturday, 11 October 2008
Thanks,
Fabio
Friday, 26 September 2008
By the way amazing work guys...As it happens I had a 1.5.5 build on me and was installing it onto my brothers website. Just for kicks I visited the Joomla website and found 1.5.6 and read about the security venerability in 1.5.5.
Thats all fixed now.
And Abhay I hope you find a good girl friend and wont have to hit on women over the joomla developers comment posts.
OHH P.S. Which comment component is this?
Saturday, 20 September 2008
Wednesday, 17 September 2008
Monday, 15 September 2008
Mine is arora.abhay@gmail.com
Saturday, 13 September 2008
Bradly - have you lost a baby? It's important to keep perspective; Web sites are not anywhere as important as people. If your point is that we, as a community, must continue to work hard to strengthen security, then your point is absolutely correct.
Friday, 12 September 2008
Because all the junior hackers will test and try to hack our Websites, your detailed fixed is silly, because it described to everyone how to hack a Joomla 1.5.5, the biggest threat is your detailed descriptions!!!!
Thursday, 04 September 2008
Kinda like a drunk driver that goes out and sideswipes several cars, runs over a baby but luckily..
15:50 EST calls lawyer
15:55 EST Lawyer looks up "HOW TO PERFORM ROADSIDE CPR" via GOOGLE, relates info to client
15:58 As our hapless driver tries in vain to locate a banana to stuff up the car's tailpipe, they both realize the attorney has looked up "ROADSIDE CAPER" instead of road side CPR
16:10 performs CPR on several auto tailpipes (to warm up, before attempting CPR on child.
16:20 after failing, advises mom to place child in trunk, for 30 days, then claim child was given to babysitter and/or abducted.
Thursday, 28 August 2008
Thanks!
Thursday, 28 August 2008
Monday, 25 August 2008
So ladies and gentlemen thank you VERY MUCH for your hard work.
Monday, 25 August 2008
I'm patching it right now - and glad to see you guys working hard to fix these things!
Sunday, 24 August 2008
You guys doing great jobs. Keep it up. You are like gladiators in this open source world. Keep rocking. Let them hack again, we will kick their ass even more harder than this.
Regards,
Surya.
Friday, 22 August 2008
The idea of a security team is great and a "critical fixes" email-list would be a good addition to that. Only this kind of "emergency" information could be shared instantly to the administrators joined this list.
Do you, I mean we
Thursday, 21 August 2008
A Big thank you to the team. What list do I need to subscribe to to the the security updates in a timely manor?
Thursday, 21 August 2008
Is there a way to build a background "check at launch" into the Joomla admin backend to check if a critical -- i.e. security -- update is required? Have it enabled by default, with optional user disabling. This might make a lot more admins aware of such issues more quickly. (It could also contain an option to advise on any version update, whether security-related or not.)
If Firefox can tell me when one of my plugins has an update available, this shouldn't be all that difficult to implement.
Thursday, 21 August 2008
Wednesday, 20 August 2008
Wednesday, 20 August 2008
Tuesday, 19 August 2008
Well done on fast response but surely more can be done. It is not a isolated problem. I will even offer mys ervices to trying to find a solution if I can be of any help.
Tuesday, 19 August 2008
Tuesday, 19 August 2008
Monday, 18 August 2008
Monday, 18 August 2008
Monday, 18 August 2008
Jorgen
Monday, 18 August 2008
Sunday, 17 August 2008
Great Job.
Regards
Lucas
Sunday, 17 August 2008
Saturday, 16 August 2008
thats unbelievable..
guys, forget everything, please focus on security
if you lose someone's trust, there's no turning back
dont sacrifice such a great project to a simple mistakes
Saturday, 16 August 2008
The only comment I wish to make to this article is that, YOUR timeframe from bug-to-fix is perfect. But OUR timeframe (the users of Joomla!) is significant lower. Currently there is no good way to stay on top of these urgents updates, e.g. mailinglist/xml feed with -only- latest version info.
Just my 2 cents.
Friday, 15 August 2008
I am upgrading now though...
Friday, 15 August 2008
Friday, 15 August 2008
Friday, 15 August 2008
Thursday, 14 August 2008
Thursday, 14 August 2008
Thursday, 14 August 2008
Thursday, 14 August 2008
Thursday, 14 August 2008
You should subscribe to the security announcements forum. If you do you will get an email any time there is an announcement. Also you can take the RSS feed from the security center here.
Thursday, 14 August 2008
thanks for your efforts
Thursday, 14 August 2008
but, my two sites are hacked using this bug before 1.5.6 released (and many others as i know)
i think this bug is listed on well-known hacker's sites before patching.
security is everything, somethimes it costs too much. for example, i've lost my two joomla customers yesterday..
Thursday, 14 August 2008
Great work!
Thursday, 14 August 2008
Thursday, 14 August 2008
Thursday, 14 August 2008
1. why there is no Multisite Feature? How can I have a codebase for all sites? This is also very important for security updates.
2. I see no security mailing list or any kind of notification where I could subscribe for security updates ONLY - a joomla sec announce list or something would be really very very useful and nowadays every project should come wit that.
3. I can not search the site (THIS site). This is totally annoying.
Please change these things fast so we can go on with our review. Thanks!
Gabor Goldbowm
Thursday, 14 August 2008
Thursday, 14 August 2008
I've never heard such short respond time to a problem.
Actually you guys must be even faster than the emergency team at NASA !
Impressive! And thank you so much for your effort to make sure end user like me don't go through boxes of paracetamol because of a exploited site.
cheers
Thursday, 14 August 2008
Thursday, 14 August 2008
Thursday, 14 August 2008
Thursday, 14 August 2008
Thursday, 14 August 2008
Thursday, 14 August 2008
Great work everyone!
Thursday, 14 August 2008