Well, as a smartphone user, I'm not quite sure whether this article is supposed to benefit me as a consumer or is targetting phone manufacturers. I have a friend who used to own an iPhone. He found an article online that provided a method to "unlock" it and he was able to customize his iPhone with personalized tones and wallpapers. Thus, from his point of view as a consumer, such articles have benefited him in a way that he is able to use his phone the way he wants the phone to work, and not be restricted to only the default phone features. However, if this article is about ensuring that your phone is safe enough from hackers who wish to invade your privacy, then I'm definitely looking forward to the upcoming subsequent articles to tell me how to be on my guards.
Thanks Steve, you are correct. Part 3 is going to cover all sort of secure bootloader options while Part 4 is going to extend it further covering ideal security platform that leverages the concepts from mobile world and apply on embedded/Industrial devices that need best in class security.
The whole idea was to take Smarphone as this as example so people could relate it better to the applications they know and then apply the concepts to embedded world.
Part 3 will include more details on secure bootloaders while Part 4 will extend it to cover idea security platform inherits capabilities from the mobile world and can be incorporated in future embedded devices.
Would be happy to receive any further feedback.
Let me clarify. By "if you use the lousy "security" approaches he's describing", I meant in part 2. Part 3 looks like he's going to describe a trusted boot sequence. Pay close attention, it's table-stakes if you want to play this game ;-).
Look at the titles of Part III and IV. It's clear that if you use the lousy "security" approaches he's describing, your products are easily cracked. Want to bet me that future parts will describe something better? Something made by Freescale? ;-)
I used to work in this area. Cellphone security is complicated, and many chip and phone manufacturers are still on the steep part of the learning curve of how to do it. Phone hackers are extremely clever, and any half-hearted "security" system is going to be hacked - count on it.
It sounds weird to me an freescale specialist, giving away hints about ways to unlock smartphones...If I was a smatphone manufacturer, I'm not sure if I would be happy reading such articles.. for sure not the ones coming from the guins wo will be probably supporting new devs...
A Book For All Reasons Bernard Cole1 Comment Robert Oshana's recent book "Software Engineering for Embedded Systems (Newnes/Elsevier)," written and edited with Mark Kraeling, is a 'book for all reasons.' At almost 1,200 pages, it ...