Comments on: obov v1.1.0 released http://ricardozuasti.com/2008/obov-v110-released/ Random thoughts about programming Fri, 31 May 2013 22:49:00 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Raffaele P. Guidi http://ricardozuasti.com/2008/obov-v110-released/comment-page-1/#comment-28985 Raffaele P. Guidi Wed, 26 Sep 2012 20:12:00 +0000 http://www.spartanjava.com/?p=17#comment-28985 Pretty useful work, and obovweb is a nice complement for testing purposes, but... what happened to the product page? /obov link is broken! I would like to know if obov supports both time based and event based passwords Pretty useful work, and obovweb is a nice complement for testing purposes, but… what happened to the product page? /obov link is broken! I would like to know if obov supports both time based and event based passwords

]]> By: Simon http://ricardozuasti.com/2008/obov-v110-released/comment-page-1/#comment-980 Simon Fri, 10 Jul 2009 14:07:28 +0000 http://www.spartanjava.com/?p=17#comment-980 I've got a working setup which might be of interest to others. I'm using a ZyXEL hardware token. You find the details here: http://www.zyxel.com/web/product_family_detail.php?PC1indexflag=20040908175941&CategoryGroupNo=96C9CDE6-F2AA-4D84-9D62-311A7CCD996C They are shipped with a CD containing the seeds. Look for a file called data01.sql located in ASAS\import. Using the following parameters you should get the token running together with oboc in just a few minutes: * secret = the seed you found in data01.sql next to your token's ESN id within the insert into the table OTP * codeDigits = 6 * addChecksum = false * truncationOffset = 16 (this enforces dynamic truncation) The token is event based. This means that the moving factor (or counter) is increased every time you push the button to get a new password. You can use resyncMovingFactor if you don't know the counter of your token. The ZyXEL tokens come from Authenex and are identical with their A-Key 3600 token. Though, I don't know how they supply the seeds in the same way. See http://www.authenex.com/authenex-products/akey-token-3600.html I’ve got a working setup which might be of interest to others.

I’m using a ZyXEL hardware token. You find the details here: http://www.zyxel.com/web/product_family_detail.php?PC1indexflag=20040908175941&CategoryGroupNo=96C9CDE6-F2AA-4D84-9D62-311A7CCD996C

They are shipped with a CD containing the seeds. Look for a file called data01.sql located in ASAS\import.

Using the following parameters you should get the token running together with oboc in just a few minutes:
* secret = the seed you found in data01.sql next to your token’s ESN id within the insert into the table OTP
* codeDigits = 6
* addChecksum = false
* truncationOffset = 16 (this enforces dynamic truncation)

The token is event based. This means that the moving factor (or counter) is increased every time you push the button to get a new password. You can use resyncMovingFactor if you don’t know the counter of your token.

The ZyXEL tokens come from Authenex and are identical with their A-Key 3600 token. Though, I don’t know how they supply the seeds in the same way. See http://www.authenex.com/authenex-products/akey-token-3600.html

]]>