<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Demo on Colin O'Flynn</title><link>https://colinoflynn.com/tag/demo/</link><description>Recent content in Demo on Colin O'Flynn</description><generator>Hugo</generator><language>en-ca</language><lastBuildDate>Sat, 18 Feb 2023 02:07:09 +0000</lastBuildDate><atom:link href="https://colinoflynn.com/tag/demo/index.xml" rel="self" type="application/rss+xml"/><item><title>Side-Channel Power Analysis of AES Core in Project Vault</title><link>https://colinoflynn.com/2015/05/side-channel-power-analysis-of-aes-core-in-project-vault/</link><pubDate>Sun, 31 May 2015 17:13:37 +0000</pubDate><guid>https://colinoflynn.com/2015/05/side-channel-power-analysis-of-aes-core-in-project-vault/</guid><description>&lt;h1 id="what-is-project-vault"&gt;What is Project Vault&lt;/h1&gt;
&lt;p&gt;You can read a quick overview on &lt;a href="http://techcrunch.com/2015/05/29/googles-project-vault-is-a-secure-computing-environment-on-a-micro-sd-card-for-any-platform/"&gt;various news sites&lt;/a&gt;, but basically project vault gives you a cryptographic module that you have complete control over. This means *you* decide to trust the module - even to the point of being able to access to implementation details of the crypto cores.
Basically Project Vault is a solution to how you can avoid having unknown backdoors in your hardware. Rather than having to trust some vendor of security modules, you can make sure things are done correctly.&lt;/p&gt;</description></item></channel></rss>