<?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=3&amp;t=208" />

<title>Yubico Forum</title>
<subtitle>...visit our web-store at</subtitle>
<link href="https://forum.yubico.com/index.php" />
<updated>2009-01-19T11:25:19+01:00</updated>

<author><name><![CDATA[Yubico Forum]]></name></author>
<id>https://forum.yubico.com/feed.php?f=3&amp;t=208</id>
<entry>
<author><name><![CDATA[Erik]]></name></author>
<updated>2009-01-19T11:25:19+01:00</updated>
<published>2009-01-19T11:25:19+01:00</published>
<id>https://forum.yubico.com/viewtopic.php?t=208&amp;p=933#p933</id>
<link href="https://forum.yubico.com/viewtopic.php?t=208&amp;p=933#p933"/>
<title type="html"><![CDATA[Re: problems with reprogrammed yubikeys: BAD_OTP]]></title>

<content type="html" xml:base="https://forum.yubico.com/viewtopic.php?t=208&amp;p=933#p933"><![CDATA[
found the problem : there was a WARN in the catalina log :<br />2009-01-16 15:02:24,426 [http-8180-Processor24] WARN  com.yubico.wsapi.Database - java.sql.SQLException: Value '0000-00-00' can not be represented as java.sql.Date<br />and after a<br />mysql&gt; update yubikeys set accessed = '1970-01-01 00:00:00';<br />everything worked ...<br /><br />h=57IAu98PWuhub7fcowqPGWVdRis=<br />t=2009-01-19T12:12:45Z0343<br />status=OK<br /><br />The error reporting could be better here, I would expect a config error message in the response from the wsapi.<p>Statistics: Posted by <a href="https://forum.yubico.com/memberlist.php?mode=viewprofile&amp;u=371">Erik</a> — Mon Jan 19, 2009 11:25 am</p><hr />
]]></content>
</entry>
<entry>
<author><name><![CDATA[network-marvels]]></name></author>
<updated>2009-01-16T18:40:18+01:00</updated>
<published>2009-01-16T18:40:18+01:00</published>
<id>https://forum.yubico.com/viewtopic.php?t=208&amp;p=926#p926</id>
<link href="https://forum.yubico.com/viewtopic.php?t=208&amp;p=926#p926"/>
<title type="html"><![CDATA[Re: problems with reprogrammed yubikeys: BAD_OTP]]></title>

<content type="html" xml:base="https://forum.yubico.com/viewtopic.php?t=208&amp;p=926#p926"><![CDATA[
We would appreciate if you can provide us some logs and debugging information. This will help us to identify the exact cause and to provide a solution for it.<p>Statistics: Posted by <a href="https://forum.yubico.com/memberlist.php?mode=viewprofile&amp;u=280">network-marvels</a> — Fri Jan 16, 2009 6:40 pm</p><hr />
]]></content>
</entry>
<entry>
<author><name><![CDATA[Erik]]></name></author>
<updated>2009-01-16T14:06:13+01:00</updated>
<published>2009-01-16T14:06:13+01:00</published>
<id>https://forum.yubico.com/viewtopic.php?t=208&amp;p=923#p923</id>
<link href="https://forum.yubico.com/viewtopic.php?t=208&amp;p=923#p923"/>
<title type="html"><![CDATA[Re: problems with reprogrammed yubikeys: BAD_OTP]]></title>

<content type="html" xml:base="https://forum.yubico.com/viewtopic.php?t=208&amp;p=923#p923"><![CDATA[
I have the same problem, however I do not use the php stuff, I use the wsapi.war file with tomcat, the self created key tests out fine with the sdk tool , but fails if you use the OTP server<br />In the documentation was mentioned the aes-field in the database is Base64 coded, is this correct ?<br /><br />$ sdk/tool ecececececececececececececececec ececececececcdbtrcjudbcdukigjbvfudtifkjfrnin<br />warning: overlong token, ignoring prefix: ecececececec<br />Input:<br />  token: cdbtrcjudbcdukigjbvfudtifkjfrnin<br />          02 1d c0 8e 21 02 e9 75 81 f4 e2 d7 49 84 cb 7b<br />  aeskey: ecececececececececececececececec<br />          30 30 30 30 30 30 30 30 30 30 30 30 30 30 30 30<br />Output:<br />          30 30 30 30 30 30 0b 00 e1 e8 ab 00 e2 94 a1 d4<br /><br />Struct:<br />  uid: 30 30 30 30 30 30<br />  counter: 11 (0x000b)<br />  timestamp (low): 59617 (0xe8e1)<br />  timestamp (high): 171 (0xab)<br />  session use: 0 (0x00)<br />  random: 38114 (0x94e2)<br />  crc: 54433 (0xd4a1)<br /><br />Derived:<br />  cleaned counter: 11 (0x000b)<br />  modhex uid: ecececececec<br />  triggered by caps lock: no<br />  crc: F0B8<br />  crc check: ok<br /><br /><!-- m --><a class="postlink" href="http://10.x.x.x:8180/wsapi/verify?id=2&amp;otp=ececececececcdbtrcjudbcdukigjbvfudtifkjfrnin">http://10.x.x.x:8180/wsapi/verify?id=2&amp; ... tifkjfrnin</a><!-- m --><br />h=waZsxFc9JQGqvT5i2f2c09j5F9g=<br />t=2009-01-16T15:02:24Z0453<br />status=BAD_OTP<br /><br />Currently you seem to be unable to download stuff from <!-- m --><a class="postlink" href="http://code.google.com/p/yubikey-server-j/">http://code.google.com/p/yubikey-server-j/</a><!-- m --><p>Statistics: Posted by <a href="https://forum.yubico.com/memberlist.php?mode=viewprofile&amp;u=371">Erik</a> — Fri Jan 16, 2009 2:06 pm</p><hr />
]]></content>
</entry>
<entry>
<author><name><![CDATA[peku]]></name></author>
<updated>2009-01-16T12:36:44+01:00</updated>
<published>2009-01-16T12:36:44+01:00</published>
<id>https://forum.yubico.com/viewtopic.php?t=208&amp;p=922#p922</id>
<link href="https://forum.yubico.com/viewtopic.php?t=208&amp;p=922#p922"/>
<title type="html"><![CDATA[Re: problems with reprogrammed yubikeys: BAD_OTP]]></title>

<content type="html" xml:base="https://forum.yubico.com/viewtopic.php?t=208&amp;p=922#p922"><![CDATA[
I reprogrammed the yubikey with the new personalization tool for Windows using the same settings (afaik) that I used for the Linux personalization tool and now it works, so probably something I missed in the Linux version.<p>Statistics: Posted by <a href="https://forum.yubico.com/memberlist.php?mode=viewprofile&amp;u=353">peku</a> — Fri Jan 16, 2009 12:36 pm</p><hr />
]]></content>
</entry>
<entry>
<author><name><![CDATA[Simon]]></name></author>
<updated>2009-01-16T10:08:08+01:00</updated>
<published>2009-01-16T10:08:08+01:00</published>
<id>https://forum.yubico.com/viewtopic.php?t=208&amp;p=921#p921</id>
<link href="https://forum.yubico.com/viewtopic.php?t=208&amp;p=921#p921"/>
<title type="html"><![CDATA[Re: problems with reprogrammed yubikeys: BAD_OTP]]></title>

<content type="html" xml:base="https://forum.yubico.com/viewtopic.php?t=208&amp;p=921#p921"><![CDATA[
The AES key in the database appears to match.  But aren't the AES keys in the database supposed to be encrypted?  I recall that the validation server internally encrypts/decrypts the database contents using a static AES key.  The PHP google code project doesn't seem available right now so I can't check the source, but just an idea to let you move debug things further.<br /><br />/Simon<p>Statistics: Posted by <a href="https://forum.yubico.com/memberlist.php?mode=viewprofile&amp;u=2">Simon</a> — Fri Jan 16, 2009 10:08 am</p><hr />
]]></content>
</entry>
<entry>
<author><name><![CDATA[peku]]></name></author>
<updated>2009-01-14T14:46:31+01:00</updated>
<published>2009-01-14T14:46:31+01:00</published>
<id>https://forum.yubico.com/viewtopic.php?t=208&amp;p=914#p914</id>
<link href="https://forum.yubico.com/viewtopic.php?t=208&amp;p=914#p914"/>
<title type="html"><![CDATA[Re: problems with reprogrammed yubikeys: BAD_OTP]]></title>

<content type="html" xml:base="https://forum.yubico.com/viewtopic.php?t=208&amp;p=914#p914"><![CDATA[
I have the same problem, after reprogramming the yubikey (on Linux), ykdebug gives OK but PHP validation server says &quot;Bad CRC&quot;. Has anyone solved this?<p>Statistics: Posted by <a href="https://forum.yubico.com/memberlist.php?mode=viewprofile&amp;u=353">peku</a> — Wed Jan 14, 2009 2:46 pm</p><hr />
]]></content>
</entry>
<entry>
<author><name><![CDATA[bert64]]></name></author>
<updated>2008-12-09T15:46:51+01:00</updated>
<published>2008-12-09T15:46:51+01:00</published>
<id>https://forum.yubico.com/viewtopic.php?t=208&amp;p=818#p818</id>
<link href="https://forum.yubico.com/viewtopic.php?t=208&amp;p=818#p818"/>
<title type="html"><![CDATA[Re: problems with reprogrammed yubikeys: BAD_OTP]]></title>

<content type="html" xml:base="https://forum.yubico.com/viewtopic.php?t=208&amp;p=818#p818"><![CDATA[
I have a very similar problem....<br /><br />ykdebug says:<br /><br />$ ./ykdebug uubgvivdgkuebejhkhtjuufrebjvftrc hbhdhehfhghhlbhctufkdbkglclthjrdrhvnvvhnlhbu<br />warning: overlong token, ignoring prefix: hbhdhehfhghh<br />Input:<br />  token: lbhctufkdbkglclthjrdrhvnvvhnlhbu<br />          a1 60 de 49 21 95 a0 ad 68 c2 c6 fb ff 6b a6 1e <br />  aeskey: uubgvivdgkuebejhkhtjuufrebjvftrc<br />          ee 15 f7 f2 59 e3 13 86 96 d8 ee 4c 31 8f 4d c0 <br />Output:<br />          61 62 63 64 65 66 01 00 c9 68 ce 01 48 74 41 98 <br /><br />Struct:<br />  uid: 61 62 63 64 65 66 <br />  counter: 1 (0x0001)<br />  timestamp (low): 26825 (0x68c9)<br />  timestamp (high): 206 (0xce)<br />  session use: 1 (0x01)<br />  random: 29768 (0x7448)<br />  crc: 38977 (0x9841)<br /><br />Derived:<br />  cleaned counter: 1 (0x0001)<br />  modhex uid: hbhdhehfhghh<br />  triggered by caps lock: no<br />  crc: F0B8<br />  crc check: ok<br /><br />so everything seems ok from ykdebug....<br />yubikey-val-server/validate_debug.php says:<br /><br />&lt;p&gt;Debug&gt; OTP validation req:<br />Sess ctr=56262<br />TS lo=64964<br />TS hi=32<br />Use=158<br />Rand=41782<br />CRC=62650<br />Timestamp=2162116<br />Calculated CRC=50232<br />Bad CRC<br />&lt;p&gt;Debug&gt; 2<br />status=BAD_OTP<br />info=hbhdhehfhghhlbhctufkdbkglclthjrdrhvnvvhnlhbu<br />t=2008-12-09T14:44:27<br />&lt;p&gt;Debug&gt; SIGN: info=hbhdhehfhghhlbhctufkdbkglclthjrdrhvnvvhnlhbu&amp;status=BAD_OTP&amp;t=2008-12-09T14:44:27<br />h=WdW8Fxj9u7a3SAFfDyAICGS+ADQ=<br /><br />So seems to be a CRC error...<br /><br />The database contains:<br /><br />mysql&gt; select * from clients;<br />+----+---------+--------+---------------------+------------------+--------------------------+-------+---------+-----------+----------+<br />| id | perm_id | active | created             | email            | secret                   | notes | chk_sig | chk_owner | chk_time |<br />+----+---------+--------+---------------------+------------------+--------------------------+-------+---------+-----------+----------+<br />|  1 |       1 |      1 | 1970-01-01 00:00:00 | bert64@test.com | YCY7zeftvHh13s52Xs6H1w== | NULL  |       0 |         0 |        0 | <br />+----+---------+--------+---------------------+------------------+--------------------------+-------+---------+-----------+----------+<br />1 row in set (0.00 sec)<br /><br />mysql&gt; select * from yubikeys;<br />+----+-----------+--------+---------------------+---------------------+----------+----------+--------------------------+---------+------+------+-------+<br />| id | client_id | active | created             | accessed            | tokenId  | userId   | secret                   | counter | low  | high | notes |<br />+----+-----------+--------+---------------------+---------------------+----------+----------+--------------------------+---------+------+------+-------+<br />|  1 |         1 |      1 | 2007-10-03 16:11:50 | 2007-10-22 22:08:18 | YWJjZGVm | iU+jIRru | 7hX38lnjE4aW2O5MMY9NwA== |       0 |    0 |    0 |       | <br />+----+-----------+--------+---------------------+---------------------+----------+----------+--------------------------+---------+------+------+-------+<br />1 row in set (0.00 sec)<br /><br />mysql&gt; select * from admin;<br />+----+-------+----------+--------------------------+---------------------+----------------+---------------------+--------+---------+<br />| id | keyid | note     | pin                      | last_access         | ip             | creation            | client | timeout |<br />+----+-------+----------+--------------------------+---------------------+----------------+---------------------+--------+---------+<br />|  1 |     1 | Root Key | OlEMemiArMptNPXxSlG1Nw== | 2008-08-07 21:27:51 | 192.168.200.20 | 2008-08-07 21:27:51 |      1 |    3600 | <br />+----+-------+----------+--------------------------+---------------------+----------------+---------------------+--------+---------+<br />1 row in set (0.00 sec)<br /><br />which would all seem to be correct... any ideas? I've been looking at this for a few days now and am completely stumped.<br /><br />Incidentally RBD, i believe you are supposed to base64 encode the aes secret key within the database, which you didn't seem to do in the posting above.<p>Statistics: Posted by <a href="https://forum.yubico.com/memberlist.php?mode=viewprofile&amp;u=327">bert64</a> — Tue Dec 09, 2008 3:46 pm</p><hr />
]]></content>
</entry>
<entry>
<author><name><![CDATA[Simon]]></name></author>
<updated>2008-11-27T12:03:34+01:00</updated>
<published>2008-11-27T12:03:34+01:00</published>
<id>https://forum.yubico.com/viewtopic.php?t=208&amp;p=810#p810</id>
<link href="https://forum.yubico.com/viewtopic.php?t=208&amp;p=810#p810"/>
<title type="html"><![CDATA[Re: problems with reprogrammed yubikeys: BAD_OTP]]></title>

<content type="html" xml:base="https://forum.yubico.com/viewtopic.php?t=208&amp;p=810#p810"><![CDATA[
This looks like a rather low-level problem and possibly an incorrect AES key?  Try using our command line tools to decrypt OTPs:<br /><br /><!-- m --><a class="postlink" href="http://code.google.com/p/yubico-c/">http://code.google.com/p/yubico-c/</a><!-- m --><br /><br />/Simon<p>Statistics: Posted by <a href="https://forum.yubico.com/memberlist.php?mode=viewprofile&amp;u=2">Simon</a> — Thu Nov 27, 2008 12:03 pm</p><hr />
]]></content>
</entry>
<entry>
<author><name><![CDATA[network-marvels]]></name></author>
<updated>2008-11-24T15:22:42+01:00</updated>
<published>2008-11-24T15:22:42+01:00</published>
<id>https://forum.yubico.com/viewtopic.php?t=208&amp;p=799#p799</id>
<link href="https://forum.yubico.com/viewtopic.php?t=208&amp;p=799#p799"/>
<title type="html"><![CDATA[Re: problems with reprogrammed yubikeys: BAD_OTP]]></title>

<content type="html" xml:base="https://forum.yubico.com/viewtopic.php?t=208&amp;p=799#p799"><![CDATA[
We are working on a new version of the personalization tool which is scheduled to be released by mid next week that will probably make it easier to program the YubiKeys. We will test the exact configuration and will update you asap.<p>Statistics: Posted by <a href="https://forum.yubico.com/memberlist.php?mode=viewprofile&amp;u=280">network-marvels</a> — Mon Nov 24, 2008 3:22 pm</p><hr />
]]></content>
</entry>
<entry>
<author><name><![CDATA[rbd]]></name></author>
<updated>2008-11-20T18:53:58+01:00</updated>
<published>2008-11-20T18:53:58+01:00</published>
<id>https://forum.yubico.com/viewtopic.php?t=208&amp;p=797#p797</id>
<link href="https://forum.yubico.com/viewtopic.php?t=208&amp;p=797#p797"/>
<title type="html"><![CDATA[problems with reprogrammed yubikeys: BAD_OTP]]></title>

<content type="html" xml:base="https://forum.yubico.com/viewtopic.php?t=208&amp;p=797#p797"><![CDATA[
Hi guys,<br /><br />I'm evaluating Yubikeys for our organization. The price is right, and we use open source widely so it fits right in there. However I must say that we've been a bit....disappointed on the software and documentation side....on pushing Yubikeys into organizations, the whole thing still seems to be in a very early phase (seems like it's written by programmers for programmers <img src="https://forum.yubico.com/images/smilies/icon_e_smile.gif" alt=":)" title="Smile" />. Besides that the solution looks very simple and very solid. I think that once all of this is done I can contribute a guide to how we got it all set up (if that does happen  <img src="https://forum.yubico.com/images/smilies/icon_cry.gif" alt=":cry:" title="Crying or Very Sad" /> )....<br /><br />Which leads me to the problem. We've set up a server, installed Ubuntu 8.10, Apache2, php5, yubiphpbase, pubico-php-lib, the php webservices and the YMS. The docs were a bit confusing but I think we got this figured out.<br /><br />So next, we downloaded the personalization utility, and tried using it (used both the MFC version and the HTML version). It took some time to figure out what was what, but the included PDF was somewhat helpful (not nearly enough examples). For the static ID and UID we used the device ID of the key converted into hex (&quot;9725b3ed678e&quot;, we also tried with a randomly generated hex number...as the docs made it seem like either would work). Then we entered in a generated AES key (&quot;c7038b85de5f8bc0760c016741e3a23d&quot;). We had debugging on and everything looked good. We pressed the ykProgram button and got the text &quot;Program completed. Kill=0, rc=0&quot;. Looking at the code, RC of 0 looks like the OK code. So it looks like the reprogramming went through (at the very least, changes to the flags seemed to stick).<br /><br />So, next we had to hack YMS a bit as it had &quot;api.yubico.com&quot; hardcoded a few places, etc. Once that was done, we go to our OTP server web service: <!-- m --><a class="postlink" href="http://otp.corp.XXXX.XXX/wsapi/verify_debug.php?id=1&amp;otp=kidgneuthijulgrhkveidkcnrcncgtbcdubvcntcigdg">http://otp.corp.XXXX.XXX/wsapi/verify_d ... bvcntcigdg</a><!-- m --><br /><br />After I added some custom debug printouts, we get the following:<br /><div class="codetitle"><b>Code:</b></div><div class="codecontent">&lt;p&gt;Debug&gt; aes key in modhex = ienteivbnvekiguugvvbniefuvltbrtegunnueginihnhttt<br />&lt;p&gt;Debug&gt; aes key in hex = &#91;s½7ñ¿9uî_ñ·4ï­Ó^»ãW·kmÝ&#93;, length = 24  &lt;&lt;&lt;MY NOTE: This isn't hex...typo? We enabled this debug print in the code.&gt;&gt;&gt;<br />&lt;p&gt;Debug&gt; From the OTP validation request:<br />array(10) {<br />  &#91;&quot;public_id&quot;&#93;=&gt;<br />  string(12) &quot;kidgneuthiju&quot;<br />  &#91;&quot;token&quot;&#93;=&gt;<br />  string(32) &quot;7735f9a3ca8fe3862bc18afba91ef0c3&quot;<br />  &#91;&quot;private_id&quot;&#93;=&gt;<br />  string(12) &quot;7735f9a3ca8f&quot;<br />  &#91;&quot;session_counter&quot;&#93;=&gt;<br />  int(34531)<br />  &#91;&quot;low&quot;&#93;=&gt;<br />  int(49451)<br />  &#91;&quot;high&quot;&#93;=&gt;<br />  int(138)<br />  &#91;&quot;session_use&quot;&#93;=&gt;<br />  int(251)<br />  &#91;&quot;crc&quot;&#93;=&gt;<br />  int(50160)<br />  &#91;&quot;timestamp&quot;&#93;=&gt;<br />  int(9093419)<br />  &#91;&quot;counter&quot;&#93;=&gt;<br />  int(8840187)<br />}<br />&lt;p&gt;Debug&gt; decoded array: <br /><br />&lt;p&gt;Debug&gt; 2<br />status=BAD_OTP<br />info=kidgneuthijulgrhkveidkcnrcncgtbcdubvcntcigdg<br />t=2008-11-20T17:27:27Z0<br />&lt;p&gt;Debug&gt; SIGN: info=kidgneuthijulgrhkveidkcnrcncgtbcdubvcntcigdg&amp;status=BAD_OTP&amp;t=2008-11-20T17:27:27Z0<br />h=kX+T2pOMHOaQKQ5wzAoRtazeZew=<br /></div><br /><br />Ok so it looked like things failed at CRC validation.<br /><br />Not really sure what is going on here. If the key was reprogrammed correctly this should work. I believe we entered in everything correctly into the DB when setting up the yubiphpbase library. Here's what we have:<br /><br />After running util.php:<br /><br />root@otpauth1:/var/www/yubiphpbase# php utils.php <br /><br /><div class="codetitle"><b>Code:</b></div><div class="codecontent">API Key: nox8sOeQ/IbfiX+qX60yT/k6lyk=<br />PIN: 2323, Encrypted PIN: b6CsxYb7CGrVkLagsglQlA==<br />TokenID (b64-encoded): lyWz7WeO<br />PIN: 2323<br /></div><br /><br />Here's our dump of the database:<br /><br /><div class="codetitle"><b>Code:</b></div><div class="codecontent">-- MySQL dump 10.11<br />--<br />-- Host: localhost    Database: yubico<br />-- ------------------------------------------------------<br />-- Server version       5.0.67-0ubuntu6<br /><br />/*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */;<br />/*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */;<br />/*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */;<br />/*!40101 SET NAMES utf8 */;<br />/*!40103 SET @OLD_TIME_ZONE=@@TIME_ZONE */;<br />/*!40103 SET TIME_ZONE='+00:00' */;<br />/*!40014 SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0 */;<br />/*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */;<br />/*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */;<br />/*!40111 SET @OLD_SQL_NOTES=@@SQL_NOTES, SQL_NOTES=0 */;<br /><br />--<br />-- Table structure for table `admin`<br />--<br /><br />DROP TABLE IF EXISTS `admin`;<br />SET @saved_cs_client     = @@character_set_client;<br />SET character_set_client = utf8;<br />CREATE TABLE `admin` (<br />  `id` int(10) unsigned NOT NULL auto_increment,<br />  `keyid` int(11) NOT NULL default '0',<br />  `note` varchar(45) default NULL,<br />  `pin` varchar(120) default NULL,<br />  `last_access` datetime default NULL,<br />  `ip` varchar(45) default NULL,<br />  `creation` datetime default NULL,<br />  `client` int(11) NOT NULL default '0',<br />  `timeout` int(10) unsigned NOT NULL default '3600',<br />  PRIMARY KEY  (`id`),<br />  KEY `FK_admin_2` (`keyid`),<br />  KEY `FK_admin_1` (`client`),<br />  CONSTRAINT `FK_admin_1` FOREIGN KEY (`client`) REFERENCES `clients` (`id`) ON DELETE CASCADE ON UPDATE CASCADE,<br />  CONSTRAINT `FK_admin_2` FOREIGN KEY (`keyid`) REFERENCES `yubikeys` (`id`) ON DELETE CASCADE ON UPDATE CASCADE<br />) ENGINE=InnoDB AUTO_INCREMENT=33 DEFAULT CHARSET=latin1;<br />SET character_set_client = @saved_cs_client;<br /><br />--<br />-- Dumping data for table `admin`<br />--<br /><br />LOCK TABLES `admin` WRITE;<br />/*!40000 ALTER TABLE `admin` DISABLE KEYS */;<br />INSERT INTO `admin` VALUES (1,1,'Root Key','b6CsxYb7CGrVkLagsglQlA==','2008-08-07 21:27:51','192.168.1.100','2008-08-07 21:27:51',1,3600);<br />/*!40000 ALTER TABLE `admin` ENABLE KEYS */;<br />UNLOCK TABLES;<br /><br />--<br />-- Table structure for table `buyers`<br />--<br /><br />DROP TABLE IF EXISTS `buyers`;<br />SET @saved_cs_client     = @@character_set_client;<br />SET character_set_client = utf8;<br />CREATE TABLE `buyers` (<br />  `id` int(10) unsigned NOT NULL auto_increment,<br />  `email` varchar(100) default NULL,<br />  `created` datetime default NULL,<br />  `addr` varchar(200) default NULL,<br />  `qty` int(10) unsigned default NULL,<br />  `client_id` int(11) NOT NULL default '0',<br />  `name` varchar(45) default NULL,<br />  PRIMARY KEY  (`id`),<br />  KEY `FK_client_id_1` USING BTREE (`client_id`),<br />  CONSTRAINT `FK_client_info_1` FOREIGN KEY (`client_id`) REFERENCES `clients` (`id`) ON DELETE CASCADE ON UPDATE CASCADE<br />) ENGINE=InnoDB AUTO_INCREMENT=2201 DEFAULT CHARSET=latin1;<br />SET character_set_client = @saved_cs_client;<br /><br />--<br />-- Dumping data for table `buyers`<br />--<br /><br />LOCK TABLES `buyers` WRITE;<br />/*!40000 ALTER TABLE `buyers` DISABLE KEYS */;<br />/*!40000 ALTER TABLE `buyers` ENABLE KEYS */;<br />UNLOCK TABLES;<br /><br />--<br />-- Table structure for table `clients`<br />--<br /><br />DROP TABLE IF EXISTS `clients`;<br />SET @saved_cs_client     = @@character_set_client;<br />SET character_set_client = utf8;<br />CREATE TABLE `clients` (<br />  `id` int(11) NOT NULL auto_increment,<br />  `perm_id` int(11) default NULL,<br />  `active` tinyint(1) default NULL,<br />  `created` datetime NOT NULL default '0000-00-00 00:00:00',<br />  `email` varchar(255) NOT NULL default '',<br />  `secret` varchar(60) NOT NULL default '',<br />  `notes` varchar(100) default NULL,<br />  `chk_sig` tinyint(1) NOT NULL default '0',<br />  `chk_owner` tinyint(1) NOT NULL default '0',<br />  PRIMARY KEY  (`id`),<br />  UNIQUE KEY `email` (`email`),<br />  KEY `perm_id` (`perm_id`),<br />  CONSTRAINT `clients_ibfk_1` FOREIGN KEY (`perm_id`) REFERENCES `perms` (`id`)<br />) ENGINE=InnoDB AUTO_INCREMENT=1678 DEFAULT CHARSET=latin1;<br />SET character_set_client = @saved_cs_client;<br /><br />--<br />-- Dumping data for table `clients`<br />--<br /><br />LOCK TABLES `clients` WRITE;<br />/*!40000 ALTER TABLE `clients` DISABLE KEYS */;<br />INSERT INTO `clients` VALUES (1,1,1,'1970-01-01 00:00:00','robbyd@corp.XXXX.XXX','xzRQUxLdkjnJrJ8ycHsT1/OEjXw=','Robby Dermody',0,0);<br />/*!40000 ALTER TABLE `clients` ENABLE KEYS */;<br />UNLOCK TABLES;<br /><br />--<br />-- Table structure for table `history`<br />--<br /><br />DROP TABLE IF EXISTS `history`;<br />SET @saved_cs_client     = @@character_set_client;<br />SET character_set_client = utf8;<br />CREATE TABLE `history` (<br />  `id` int(10) unsigned NOT NULL auto_increment,<br />  `usrid` int(10) unsigned NOT NULL default '0',<br />  `note` varchar(45) NOT NULL default '',<br />  `ip` varchar(45) NOT NULL default '',<br />  `creation` datetime NOT NULL default '0000-00-00 00:00:00',<br />  `keyid` int(10) unsigned NOT NULL default '0',<br />  PRIMARY KEY  (`id`),<br />  KEY `FK_hist_1` (`usrid`)<br />) ENGINE=InnoDB AUTO_INCREMENT=347 DEFAULT CHARSET=latin1;<br />SET character_set_client = @saved_cs_client;<br /><br />--<br />-- Dumping data for table `history`<br />--<br /><br />LOCK TABLES `history` WRITE;<br />/*!40000 ALTER TABLE `history` DISABLE KEYS */;<br />/*!40000 ALTER TABLE `history` ENABLE KEYS */;<br />UNLOCK TABLES;<br /><br />--<br />-- Table structure for table `perms`<br />--<br /><br />DROP TABLE IF EXISTS `perms`;<br />SET @saved_cs_client     = @@character_set_client;<br />SET character_set_client = utf8;<br />CREATE TABLE `perms` (<br />  `id` int(11) NOT NULL auto_increment,<br />  `verify_otp` tinyint(1) default '0',<br />  `add_clients` tinyint(1) default '0',<br />  `delete_clients` tinyint(1) default '0',<br />  `add_keys` tinyint(1) default '0',<br />  `delete_keys` tinyint(1) default '0',<br />  PRIMARY KEY  (`id`)<br />) ENGINE=InnoDB AUTO_INCREMENT=4 DEFAULT CHARSET=latin1;<br />SET character_set_client = @saved_cs_client;<br /><br />--<br />-- Dumping data for table `perms`<br />--<br /><br />LOCK TABLES `perms` WRITE;<br />/*!40000 ALTER TABLE `perms` DISABLE KEYS */;<br />INSERT INTO `perms` VALUES (1,1,1,1,1,1),(2,1,0,0,1,1),(3,1,0,0,0,0);<br />/*!40000 ALTER TABLE `perms` ENABLE KEYS */;<br />UNLOCK TABLES;<br /><br />--<br />-- Table structure for table `yubikeys`<br />--<br /><br />DROP TABLE IF EXISTS `yubikeys`;<br />SET @saved_cs_client     = @@character_set_client;<br />SET character_set_client = utf8;<br />CREATE TABLE `yubikeys` (<br />  `id` int(11) NOT NULL auto_increment,<br />  `client_id` int(11) NOT NULL default '0',<br />  `active` tinyint(1) default NULL,<br />  `created` datetime NOT NULL default '0000-00-00 00:00:00',<br />  `accessed` datetime default NULL,<br />  `tokenId` varchar(60) character set latin1 collate latin1_bin default NULL,<br />  `userId` varchar(60) NOT NULL default '',<br />  `secret` varchar(60) NOT NULL default '',<br />  `counter` int(11) default NULL,<br />  `low` int(11) default NULL,<br />  `high` int(11) default NULL,<br />  `notes` varchar(100) default NULL,<br />  PRIMARY KEY  (`id`),<br />  UNIQUE KEY `userId` (`userId`),<br />  UNIQUE KEY `tokenId` (`tokenId`),<br />  KEY `client_id` (`client_id`)<br />) ENGINE=InnoDB AUTO_INCREMENT=4541 DEFAULT CHARSET=latin1;<br />SET character_set_client = @saved_cs_client;<br /><br />--<br />-- Dumping data for table `yubikeys`<br />--<br /><br />LOCK TABLES `yubikeys` WRITE;<br />/*!40000 ALTER TABLE `yubikeys` DISABLE KEYS */;<br />INSERT INTO `yubikeys` VALUES (1,1,1,'2008-10-03 16:11:50','2008-10-22 22:08:18','lyWz7WeO','hX+j1RaP','c7038b85de5f8bc0760c016741e3a23d',0,0,0,'Robby Dermody');<br />/*!40000 ALTER TABLE `yubikeys` ENABLE KEYS */;<br />UNLOCK TABLES;<br />/*!40103 SET TIME_ZONE=@OLD_TIME_ZONE */;<br /><br />/*!40101 SET SQL_MODE=@OLD_SQL_MODE */;<br />/*!40014 SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS */;<br />/*!40014 SET UNIQUE_CHECKS=@OLD_UNIQUE_CHECKS */;<br />/*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */;<br />/*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */;<br />/*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */;<br />/*!40111 SET SQL_NOTES=@OLD_SQL_NOTES */;<br /><br />-- Dump completed on 2008-11-20 17:46:16<br /></div><br /><br /><br />Any help would be GREATLY appreciated. We'd really like to start using Yubikeys.<br /><br />Robby<p>Statistics: Posted by <a href="https://forum.yubico.com/memberlist.php?mode=viewprofile&amp;u=307">rbd</a> — Thu Nov 20, 2008 6:53 pm</p><hr />
]]></content>
</entry>
</feed>