The challenge with an open system is that security features can be added - which is great - but they can also be disabled or recoded to be non-functional. How would an employer confirm that the intended security features are all installed and intact as employees entered the facility?
you know android is linux, right? adding such features to any linux box merely demonstrates basic understanding of how *nix works, not some kind of breakthrough or heroic act of uber-coding.
also what is this about "trumping" android? the title implies a trap (trojan?) that overmatches (breaks into?) android. which if anything is the opposite of the article...
Battar: good idea. I believe that all these security issues are being, and will be, addressed by DOD and contractors. What I'm curious about is how do the security issues translate to the commercial world, in medical, and industrial applications. Any ideas?
Heres an idea - certain defence contractors do not allow cameras in their facilities, and employees must use cell-phones without cameras. A contractor could give their employees smartphones and automatically disable the camera when they swipe the badge at the entry gate.
Drones are, in essence, flying autonomous vehicles. Pros and cons surrounding drones today might well foreshadow the debate over the development of self-driving cars. In the context of a strongly regulated aviation industry, "self-flying" drones pose a fresh challenge. How safe is it to fly drones in different environments? Should drones be required for visual line of sight – as are piloted airplanes? Join EE Times' Junko Yoshida as she moderates a panel of drone experts.