<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en-gb">
<link rel="self" type="application/atom+xml" href="https://forum.yubico.com/feed.php?f=16&amp;t=211" />

<title>Yubico Forum</title>
<subtitle>...visit our web-store at</subtitle>
<link href="https://forum.yubico.com/index.php" />
<updated>2008-12-05T15:30:33+01:00</updated>

<author><name><![CDATA[Yubico Forum]]></name></author>
<id>https://forum.yubico.com/feed.php?f=16&amp;t=211</id>
<entry>
<author><name><![CDATA[Simon]]></name></author>
<updated>2008-12-05T15:30:33+01:00</updated>
<published>2008-12-05T15:30:33+01:00</published>
<id>https://forum.yubico.com/viewtopic.php?t=211&amp;p=817#p817</id>
<link href="https://forum.yubico.com/viewtopic.php?t=211&amp;p=817#p817"/>
<title type="html"><![CDATA[How does YubiKey compare to OATH HOTP?]]></title>

<content type="html" xml:base="https://forum.yubico.com/viewtopic.php?t=211&amp;p=817#p817"><![CDATA[
We've been asked how the YubiKey compares to OATH's HOTP.<br /><br />The main answer is that OATH HOTP only uses a hashed counter as the OTP whereas YubiKey OTPs contains the time differences compared to the last OTP.  Thus, the YubiKey mitigates some attacks where several OTP's are harvested and then replayed at a different time.  The attack that OATH HOTP is vulnerable against but YubiKey is not is a passive phishing attacker.<br /><br />Link to OATH HOTP specification: <!-- m --><a class="postlink" href="http://www.ietf.org/rfc/rfc4226.txt">http://www.ietf.org/rfc/rfc4226.txt</a><!-- m --><br /><br />Our current chip/RAM/ROM size of our CPU is likely too limited to fit the OATH HOTP algorithm, but please contact Yubico to discuss this if you are interested.<br /><br />/Simon<p>Statistics: Posted by <a href="https://forum.yubico.com/memberlist.php?mode=viewprofile&amp;u=2">Simon</a> — Fri Dec 05, 2008 3:30 pm</p><hr />
]]></content>
</entry>
</feed>