<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en-us" xmlns="http://www.w3.org/2005/Atom"><title>Simon Willison's Weblog: keyczar</title><link href="http://simonwillison.net/" rel="alternate"/><link href="http://simonwillison.net/tags/keyczar.atom" rel="self"/><id>http://simonwillison.net/</id><updated>2010-01-04T15:23:32+00:00</updated><author><name>Simon Willison</name></author><entry><title>Timing attack in Google Keyczar library</title><link href="https://simonwillison.net/2010/Jan/4/timing/#atom-tag" rel="alternate"/><published>2010-01-04T15:23:32+00:00</published><updated>2010-01-04T15:23:32+00:00</updated><id>https://simonwillison.net/2010/Jan/4/timing/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://rdist.root.org/2009/05/28/timing-attack-in-google-keyczar-library/"&gt;Timing attack in Google Keyczar library&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
An issue I also need to fix in the proposed Django signing code. If you’re comparing two strings in crypto (e.g. seeing if the provided signature matches the expected signature) you need to use a timing independent string comparison function or you risk leaking information. This kind of thing is exactly why I want an audited signing module in Django rather than leaving developers to figure it out on their own.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/cryptography"&gt;cryptography&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/django"&gt;django&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/keyczar"&gt;keyczar&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/python"&gt;python&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/security"&gt;security&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/signing"&gt;signing&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/timing-attack"&gt;timing-attack&lt;/a&gt;&lt;/p&gt;



</summary><category term="cryptography"/><category term="django"/><category term="keyczar"/><category term="python"/><category term="security"/><category term="signing"/><category term="timing-attack"/></entry><entry><title>Keyczar</title><link href="https://simonwillison.net/2008/Aug/13/keyczar/#atom-tag" rel="alternate"/><published>2008-08-13T13:20:59+00:00</published><updated>2008-08-13T13:20:59+00:00</updated><id>https://simonwillison.net/2008/Aug/13/keyczar/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://www.keyczar.org/"&gt;Keyczar&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
New open source cryptography toolkit from Google, designed to get algorithm selection, key rotation and versioning right so you don’t have to. Java and Python versions are available; the Python version depends on PyCrypto.

    &lt;p&gt;&lt;small&gt;&lt;/small&gt;Via &lt;a href="http://www.links.org/?p=374"&gt;Ben Laurie&lt;/a&gt;&lt;/small&gt;&lt;/p&gt;


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/ben-laurie"&gt;ben-laurie&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/encryption"&gt;encryption&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/google"&gt;google&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/java"&gt;java&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/keyczar"&gt;keyczar&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/keyrotation"&gt;keyrotation&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/pycrypto"&gt;pycrypto&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/python"&gt;python&lt;/a&gt;&lt;/p&gt;



</summary><category term="ben-laurie"/><category term="encryption"/><category term="google"/><category term="java"/><category term="keyczar"/><category term="keyrotation"/><category term="pycrypto"/><category term="python"/></entry></feed>