
"Hacking the Xbox" is a fascinating book about exactly what it says. If you have no interest in gory details of JTAG probe points, cryptography, so called "trusted computing" and "digital rights management" and the technical issues at stake in trying to implement and/or attack them... then this book will bore you to tears. If you do have such interests, then you are in for a treat. The book opens with 5 chapters of fairly broad physical overview, walking through the hardware systems in Xbox consoles and some (relatively) simple projects to get your hands dirty with a soldering iron. Then on to some meaty chapters introducing you to the security model of the platform, and the attacks that the author and others developed to ultimately succeed at running arbitrary code on these systems. These chapters provide a fascinating blow-by-blow account of the process of developing the attacks. Then, we wrap up with some practical material regarding how to use these attacks to run, for instance, Xbox-Linux on a hacked machine, and some bigger picture information on the legal environment facing US hackers interested in these matters.
Thanks man!
I like this monthly comp — it’s a good way to see: a) what electronics exist b) what makes them distinctive enough to be identified
The feeling lost bit is probably common but when that's the case focus on your end goal. Here's my general approach so far.
- I got a personal project that I have no choice but to see through to the end. Having this as an end goal helps direct my focus.
- I avoid most rabbit holes - especially when it comes to learning theory. The rabbit holes are endless. I focus only on the rabbit holes that help me meet my end goal even if that means skipping fundamental stuff. This is really hard sometimes but if it's fundamental it'll come up again and again until ignoring it is not an option or maybe you just become curious enough to explore. My curiosity is dangerous here so I try to curb it the best I can. (maybe I should block time off specifically for exploring my curiosities and go deeper on concepts that may not be immediately relevant)
- I work on some aside prototypes to build an understanding of fundamental circuit components/concepts e.g. LEDs, resistors, voltage, current, resistance. Once I put something together I read a little bit of theory behind the components. Or sometimes it's the other way around - I read the theory then I put a simple circuit together using a breadboard and some wires.
- I bought tools based on advice I found in Books, YouTube, HN, and Reddit. For me this meant buying passive components, a breadboard, pre-cut wires, 22-gauge wire spools, soldering station (and various soldering equipment), hand-held tools (e.g. wire cutters, multimeter, tape measure), a power supply, safety equipment, and a 3d printer. I went on a spree. With that said I bought tools aligned with my goals.
- It also helps when I recognize that it takes time. Picking up and mastering a skill or at least becoming competent is a multi-year process. More importantly - I have that time. I have today, tomorrow, next week, next year to keep getting better. So there's no pressure. Man what a gift.
- I look to people that have the expertise and listen to what they have to say. That either means watching youtube lectures by people like bunnie, dave jones, authors of books. And just reading books like the Art of Electronics, Hacking the Xbox. Or finding material online and reading some more.
What an awesome time to be alive. Resource are endless - it's just a matter of paring stuff down based on your goal. Good luck on the projects.
