Sony, Security, and Consumer’s Rights

Posted by kc on Apr 3rd, 2010

Many of you saw my recent tweets complaining about the Sony PlayStation 3 firmware update version 3.21 that cripples the second operating system “OtherOS” feature of the PS3. Since then, I’ve received several questions as to why I thought Sony would remove such a feature, and why I cared so much.

The answers to both questions require more than 140 characters. Here, I will try to explain.

The PlayStation 3 as a Computing Platform

Briefly, the PS3 is an amazing computing platform. It boasts a 7-core 3.2GHz IBM PowerPC cell processor architecture unlike pretty much anything available at even twice the price. It works with USB and Bluetooth Wireless input devices (mouse, keyboard, gamepads, &etc), has HDMI, Composite, and Component video outputs, digital audio output, an internal SATA hard drive, 802.11b/g wireless, and a Blu-ray DVD-ROM drive.

Sony has, from the start, marketed the fact that this amazing “game console” also supports the ability to run Linux for those power-users who wanted to also use it as a computing platform. This included feature is known as “OtherOS” support.
[Reference: http://www.playstation.com/ps3-openplatform/index.html ]

FWIW, this feature was a deciding factor in my choice of the Sony PlayStation 3 as a game / media / computing platform when I purchased it.

The DRM Arms Race

Without writing yet another long blog about DRM, let me just state a couple of canons about Intellectual Property that I believe to be true:

I: Companies that own intellectual property rights have the right to protect themselves from illegitimate copying, use, or distribution of said intellectual property.

I want to state this up front, because I believe it’s important. Far from the “Information Wants To Be Free!” rally cry of the pirates, I understand and acknowledge that media and entertainment production is a business. And those businesses have the right to not have their products stolen from them.

II. All technological measures to prevent unauthorized reproduction or distribution of media will ultimately fail.

We all need to acknowledge this as well. Every software copy protection scheme, every cable transmission encryption scheme, every satellite distribution set-top-box authorization scheme, every music anti-ripping scheme has eventually been broken by those who want to copy the media.

It has happened, it will continue to happen. You cannot present media to a person and yet prevent that person from ultimately being able to reproduce it without your authorization. That is a certainty – almost a law of information, if you will.

So, with these two points acknowledged, all DRM and anti-copying measures come down to this:

What can be done to make illegitimate copying or distribution of media more difficult, without infringing on the legitimate use by the consumer?

That question, my friends, is what the entire DRM side of the media industry does for a living.

The second half of that question is the line that Sony just crossed with the PS3.

Geohot and the PlayStation 3 Hack

A very talented, well known hacker named George Hotz, or “geohot”, discovered some bugs in the hardware / firmware implementation of the PS3. These bugs allowed him to write an exploit that provided access to parts of the PS3 hardware that Sony had previously restricted from the OtherOS support. In short, this put the security measures that Sony had implemented to protect their platform and its copy protection schemes at risk.

Geohot’s hack is not a way to copy games or movies. It is, however, a way to start tinkering with the protected parts of the system that prevent you from doing so. His hack has a number of beneficial features too, like providing a higher level of customization to power users. Or the ability to include more of the hardware features in custom developed applications for the PS3 OtherOS platform.

A parallel between geohot’s PS3 hack and his iPhone hack that made “jailbreaking” possible has been drawn, and for a good reason. They are very similar hacks. They both “open up” a restricted platform so that the consumer has more abilities than the corporation that created it intended.

If you’re interested, you can read more on geohot’s PS3 blog: http://geohotps3.blogspot.com/

Sony’s Reaction to Geohot’s Hack

Sony’s reaction to Geohot’s hack was swift and fascist in nature.

1. Sony has removed ALL “OtherOS” support from ALL Playstation 3 devices as of the mandatory firmware update 3.21 on April 1st, 2010.

2. If a PlayStation 3 owner chooses not to install update 3.21:

a. Access to the PlayStation 3 Network is disabled
b. Access to online features of purchased games are disabled.
c. Blu-ray movie playback is disabled.
d. Many newer (purchsed) games are disabled.

[Reference: http://blog.us.playstation.com/2010/03/28/ps3-firmware-v3-21-update/ ]

So Sony is giving its users a choice. Give up OtherOS support, or give up pretty much all the other uses of the PlayStation 3.  Whether or not you think what George Hotz did by finding and exploiting the PS3 vulnerabilities was right or wrong, I assert one thing:

Sony’s reaction to geohot’s hack is wrong.

They have removed a major feature that was a selling point of the product as a knee-jerk reaction to something that was not only predictable, but inevitable. This “We’re going to take our ball and go home” attitude towards their customers is deplorable.

I ask you, Sony, if you want to retain a modicum of respect from the technical community, please reconsider.  Reinstate OtherOS support on the PlayStation 3.

It’s just the Right Thing To Do(tm).

- Kenneth “K.C.” Budd, CISSP

Freeside Atlanta – Speculative Spaces

Posted by kc on Jun 13th, 2009

Metropolitan Industrial:

The “Metro” is a large warehouse space divided into three main partitioned areas. The first area has an enclosed space occupying roughly 60% of the width of the space. That enclosed area has a couple of single-office sized rooms (one of which is psychadelic painted with glow-in-the-dark stars) and a bathroom with a working shower in it.

The second partitioned area has a kitchen built in it, complete with counter space, a kitchen sink, a range, a dishwasher, and an “island” counter with electrical power and storage space. At the back of the second partition is another enclosed space with two small office-style rooms, another closed-sized bathroom, and a weird small unfinished alcove-like room (not photographed).

The third partitioned area is open warehouse space, with a small semi-wall dividing it from the two large roll-up garage doors in the back.

My photos do not include the front area’s enclosed rooms because they had dark painted walls and no light whatsoever. My attempts to photograph them did not result in anything of use. I’m also missing some of the “nook and cranny” rooms/spaces for the same reason. I think I captured the majority of the space fairly well though.

I also didn’t photograph the bathrooms in either site.

Photos of the Metro:


Green Industrial:
Green Industral site is a fairly standard office/warehouse combo. The front consists of two foyer rooms with tile floors. From there, there’s a standard single-office sized room, a strange “alcove room” (again!), a conference / presentation room, and then the warehouse. There are two small bathrooms as well, one of which I’m told can be converted to a shower instead at possibly no additional cost.

I photographed one of the two foyers, but not the other. (They’re roughly the same, save for the front door.) I also did not photograph the small alcove room or the bathrooms.

Photos of Green:

New Hosting Provider, mysql & Wordpress Unicode Issues

Posted by phreakmonkey on Jun 10th, 2009

Hi folks!

Just a quick note – I’ve moved to a new hosting provider. If you see anything wonky, broken links, or other such weirdness shoot me an email.

When I first migrated the database (a few days ago) I ended up with some spurious Unicode characters scattered throughout the website. (E.g. lots of strange à characters stuck in around words, &etc.) Turns out the problem was mysql. Wordpress was correctly backing up the database as utf8, but when I re-imported it, it was re-encoding it for some reason. The solution was to add “–default_character_set=utf8″ on the mysql command line during the database restore/import.

E.g.:

# mysql --default_character_set=utf8 -u{username} -p{password} {dbname} -h {hostname} < db-backup-file.sql

Deleting and re-importing the database with the --default_character_set option fixed it right up! (I'm posting this as a reminder to myself as well.)

Cheers!
- K.C.

1964 Livermore Data Systems Model A modem – followup

Posted by kc on May 31st, 2009

Alright, here’s some photos of the beast:

And, in no particular order, some answers to the questions I’ve received:

1. This modem uses Bell 103A modulation, in “Originate Mode” only. Unfortunately, that means you probably couldn’t have two Livermore Data Systems Model A modems talk to each other. The “Model C” seems to be the first one that also supported “Answer Mode” modulation.

2. This modem is solid state; it uses transistors (albeit early, metal canister ones.) It doesn’t have vacuum tubes in it. (Whew!) It functions exactly as I received it twenty years ago – I haven’t modified or repaired it in any way. Yes, I am as amazed as you are! :-)

3. The host used in the video, as well as all the accounts, credentials, &etc, were set up in my lab specifically for testing the modem and were taken down the next day. Hence, I didn’t have to worry about obscuring my typing or login credentials, &etc. Thank you to all the concerned people out there who warned me that someone might be able to deduce what I was typing.

4. We didn’t do PPP or SLIP across dial-up modems prior to 9600 baud because the protocol overhead would saturate the line. In my mind, it doesn’t matter at which point in the communications path each layer of the OSI model gets peeled back, the data from the host still made it to the client. Dialing in to terminal servers (or directly into UNIX boxes or mainframes) is how “we did it back then.” I did subsequently get a very relaxed-protocol PPP connection to work through the modem, but it barely functioned. 56-byte pings took between 3000 and 5000 ms. DNS saturated the lines. TCP connections failed (handshake timeout) most of the time due to the latency. A browser simply wouldn’t load a page.

5. Yes, that’s a beer on the table behind the counter. Specifically, it’s a home-brewed clone of Sweetwater 420 IPA. If you like IPAs, Sweetwater makes a darned tasty one. ;)

Thanks for all the comments, feedback, tweets, emails, &etc! I found the modem inspiring, and hoped others would too. More to come! My gmail address is also phreakmonkey

Cheers!
– K.C.
aka phreakmonkey

Next »