Slashdot Mirror
Sony Update Bricks Playstations
Stoobalou writes "A controversial update which was seeded by Sony in order to remove the ability to run Linux on the Playstation 3 games console has caused a storm of complaints.
The 3.21 firmware upgrade, which removes the security hole provided by the 'Install Other OS' widget used by lots of educational institutions and hackers alike, also removes the console's ability to play games... turning it into a very expensive doorstop."
Yes, every single system update brings out dozens of "complaints" how it bricked their system. You'll note the very low number of posts against each of these user in the forums too, creating their account to troll or complain is the question? You get the same thing when major games are released. Trolls or genuine reports has never been determined because no one ever follows up the complaints with real people to determine validity, but nevertheless, people write these problems "stories".
Ever since the update I've had issues with games freezing up on me. I haven't noticed any real slow down of the net connection or any issues with PSN. But if this is a ploy by Sony to get me to give up my thick PS3 that has the ability to play PS2 games then they better add that functionality to the slim PS3 because I'm not about to go out and buy 2 consoles just to have the same functionality as the one I have now.
The article doesnt describe bricking. It barely describes real problems. It describes (rather vaguely) sluggish internet and third party controllers not working. And it never actually shows or links to actual complaints. The only real information in the article is that people who dont install the update can't connect to PSN, which is standard for these updates.
D
The first, last, and only tech news site on the net
I wonder whether the intentional removal of a major feature which was present at time of purchase, and which for many was the primary reason for said purchase, is in any way actionable.
Yes. In addition to a PS3, X360, and Wii there's also the iPhone and iPad that can be bricked via forced updates. Also certain DVRs and Bluray/HDDVD gadgets. I've also heard complaints about DTVpals being bricked by the Dish Company's updates.
And my response?
- Call Sony to demand restitution for the PS3 they broke.
- Wait.
- If no response to repair or replace the broken PS3, then I'd buy a new PS3 from some store (like amazon or walmart), put the bricked one inside the box, then return it as defective ("It just won't turn on. No I don't want an exchange; I want a refund."). The store would eventually return it to Sony who would have to deal with the property THEY destroyed.
"I disapprove of what you say, but I will defend to the death your right to say it." - historian Evelyn Beatrice Hall
The problem is that Sony cares way more about locking down and commoditizing their media content with DRM and "security meseasures" than they do about their customers (one of the inherent problems of having a hardware maker who is also a media producer). They're not alone on that (MS and Nintendo are hardly open themselves), but they do seem much more obsessed about it than just about anyone else--short of maybe Apple.
The problem is that Sony doesn't seem to be thinking much about the fact that their media is only worth something in the first place BECAUSE of their customers. And, if they're not careful, they could very easily lose their balance and fall. After all, the perfect way to produce a piracy-proof blu-ray of a movie or videogame is to simply release it as a blank disc. But no one is going to buy it then, are they?
SJW: Someone who has run out of real oppression, and has to fake it.
If you are in the UK you don't need to worry about warranty; I have recently discovered the Sale of Goods Act, which means with or without warranty they would have to replace it because it is less than 6 years old.
It is archaic definition bricked or "inconvenient to repair" bricked, as is the new usage.
Given that "literally" is the new figuratively it's hard to tell what people mean these days.
No, there are two words to explain that: Other OS. Check out this table (slightly outdated, it's a year old or so) by console hacker Michael Steil (or watch him talk about it on any of his talks). Every console post-PS2 was hacked for homebrew, and then those hacks were abused for piracy. The PS3 comes with homebrew, therefore there is little motivation to crack the native system. Pro-piracy people are rarely good hackers, and need homebrew to piggyback on. In fact, the reason the PS3 was recently attacked was neither homebrew nor piracy; instead, geohot attacked it solely as an ego boost and to get media coverage (note how he hasn't even tried to develop a useful application for his exploit, such as GPU access under Linux).
Blu-ray is a minor inconvenience. There are a myriad potential ways of copying PS3 games that don't involve blu-ray discs.
Sony are shooting themselves in the foot by removing Other OS, and pissing off legitimate customers on top of it.
And yet the PS3 isn't tougher to hack in the way geohot has (certainly not given Other OS). Look at geohot's hack: it's a simple RAM glitch, much like the one tmbinc pioneered over 2 years ago on the Wii ("twiizer attack"). Now that hacks are out for all consoles, we can compare the relative difficulty. Compare the PS3 (plaintext hypervisor in RAM, no hashing) to the Xbox 360 (encrypted hypervisor in RAM, hashing, encrypted executables). Both consoles have good security, but the PS3 hack is significantly simpler than 360 hacks from a technical perspective (drive hacks notwithstanding - that's a whole different ballgame). That's also confirmed given how little time it took geohot to get it to work, even though he was completely unfamiliar with the PS3 when he started a few months earlier. Even the Xbox1 LDT bus tap by Andrew "bunnie" Huang was orders of magnitude more complicated, and yet he pulled it off in 2001.
As a console hacker myself, I know quite a few others, and I can definitely say that interest in hacking the PS3 was near nonexistent before the Slim came out (sans Other OS), except for a couple Linux folks trying to poke holes in the hypercall interface to get access to the GPU.
Recently, as a reward for getting straight 'A's I took my son to a CompUSA and told him he could have any computer he wanted. Imagine my disgust when he selected a mac mini. It's as if I took him to a whorehouse for his first lay and he wound up giving head to the bouncer. Where did I fail as a father?
Yes, that part of the table is wrong (IMO it should read 12 months or whatever). However, this warrants some explanation.
Since the advent of drive modifications and consoles with signed executables, piracy has split into two camps: drive modification, and software modification. The latter implies homebrew and always piggybacks on homebrew, and is mostly what I refer to in my GP post. However, drive modifications are a different story. They mostly appeared when drive firmware patches delivered via homebrew on the GameCube were ported by modchip manufacturers to be delivered via an alternate serial port on the drive. The GC/Wii's drives are outsourced to Matshita, and they didn't bother to fix the hole in the GameCube. Paraphrasing tmbinc, "The GameCube had a connector on the drive board that might as well have been labeled 'insert modchip here'. With the Wii, they fixed this problem by removing the old connector... and replacing it with a new one".
Therefore, it is safe to say that DVD (drive) piracy on the Wii was there from the very beginning - not because the modchip makers are good, but because modchips were trivially ported over from the GameCube. On the other hand, softmod piracy on the Wii started, as usual, by piggybacking on homebrew.
The reason that drive mods are popular is because manufacturers have neglected that part of console security - they made their software secure, but didn't properly secure the drive. If you can convince a drive that a burned game is legit, then there's nothing that the console software can do about it. In order to fix this, you need to improve drive security and couple it to system security.
The Wii is the worst example - the drive bus is in plaintext and unauthenticated. This is why HDD-to-drive physical adapters are coming out from modchip makers.
The 360 is better, but the drives are essentially off-the-shelf PC drives. Although they're trying hard to detect and ban mods, and there's some crypto going on, the drives are still pretty insecure.
The PS3 is different; as far as I know, the BD drive is custom, secure, and much better coupled to the system.
So, to conclude and better explain things: the PS3 avoided commercial drivechips by having good drive security (something sorely lacking on other consoles), and avoided noncommercial software piracy by removing the incentive for homebrewers to hack the system (which will inevitably happen otherwise, as has been proven time and time again).
Where did I fail as a father?
Taking your son to CompUSA...or a whorehouse.
There are two types of people in the world: Those who crave closure