Slashdot videos: Now with more Slashdot!

View

Discuss

Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).

DeviceGuru writes "Many of us have griped for years about Roku's retro one-dimensional user interface. Finally, in conjunction with the release of the new Roku 3 model, the Linux-based media streaming player is getting a two-dimensional facelift, making it quicker and easier to access favorite channels and find new ones. Current Roku users, who will now begin suffering from UI-envy, will be glad to learn that Roku plans to push out a firmware update next month to many earlier models, including the Roku LT, Roku HD (model 2500R), Roku 2 HD, Roku 2 XD, Roku 2 XS, and Roku Streaming Stick. A short demo of the new 2D Roku menu system is available in this YouTube video."

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.

slart42 (694765) writes "Following up Tuesday's story, in which Vodaphone brought T-Mobile to court for selling iPhones in Germany without an option to buy them without an expensive two-year contract, T-Mobile has now announced (german Spiegel article) the sale of unlocked iPhones for a "bargain" price of only 999 Euros. Getting your hands on one of these might provide some insight on how to "properly" unlock an iPhone, which won't be relocked with the next firmware update from Apple."Link to Original Source