wait, does that mean I can go to a BA ticket counter put on the SkyLights headset, which advertises their 1st class to me, where, while in VR, I'll put on the SkyLights offered in First class to verify if having the headset during the flight is worth the upgrade? ;)

...that is educated enough to know how lemmings behave in the wild, or old + educated enough to have played lemmings the computer game. I doubt this analogy is really easy to understand for everyone.

Serdar Somuncu

What worries me the most is that according to the guys holding the presentation there was no reponse from the python team on that issue. Also plone, a web platform based on python, they tested their attack against it and notified the plone guys, didn't implement any countermeasures after being notified. This was fixed in perl in 2003, it's interesting that the opensource community didn't bother to check the hashtable implementations of all other languages back then. Are they in competition not telling others that something important needs to be fixed? Java devs, chose not to change their hash algo in 2003 BTW because it is a too integral part. Well the modified version is in use for 8 years in perl, might wanna upgrade it this time ;)
Also the fixes PHP 5.4rc (and tomcat, and ...) implemented are just workarounds that were already available before with the suhosin extension for example. Limiting the number of variables you can POST is a wannabe fix, can be circumvented with JSON for example (given that the app uses json_decode() on the receiving end).

if you need to constantly change an ENUM field, then it is not supposed to be an enum field in the first place... Use a foreign-key to a table which you can easily edit. BTW, you can edit an enum fields definition, it's just a series of clever DDL queries. but again, an enum column isn't supposed to change by design.