![]() On the plus side, the smartcard industry put a lot of effort over the past decades to design isolation layers in the GlobalPlatform standard, even going to partial formal proofs, making sure that applications can’t interfere with each others and that a product can keep existing certifications when third party applications are installed post issuance using the Composition Model. The industry standard for this interpreted code is Java Card - which offers an extremely limited version of the Java platform (no String support, poor dynamic memory management …). The state of the art today when considering interaction with a Secure Element is rather poor: open applications live as non native code on an island in a sea of proprietary code with undefined boundaries. Secure Hardware and Open Source: state of the art today While we agree on the most important points raised in this article (basically that Secure Elements are a critical part of a security architecture to provide protection against physical attacks and device interdiction), we’d like to offer our perspective on how we’re trying to improve the status quo. A few weeks ago Yubico published an interesting piece on their security architecture illustrating conflicts between Open Source and Secure Hardware.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |