Hi Toledo, I'm glad to find you here! I'm going to use time based tokens that need to be in sync with the radius server's clock, and from time-to-time the module need to resync the token and store a time-offset information. That's why the module need to store information. Unfortunately the motp is not compatible with the token I'm going to use. Thanks anyway! On Sat, Mar 12, 2011 at 12:52, Toledo, Luis Carlos <lscrlstld@gmail.com>wrote:
Hi,
I'm kinda new to Freeradius and at the same time I'm learning it, I'm seeing I gonna need to develop a new module for it.
This module will do OTP two way authentication. It will extract part of the password (ex.: latest 6 digits) to verify and the remaining "password" will be returned to Freeradius to test against another module (LDAP for example).
In this module I need to store user information on some place, including usernames, keys, secrets, last OTP, offset, etc.
Would you like freeradius act as a token? The principle of operation of OTP is to not store nothing, it just returns a temporary password based an some one-way algorithm, this temporary password is basically the result of PIN received from user.
Look at this project, maybe it can help you. It´s works jointly with radius. http://motp.sourceforge.net/
Toledo
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/devel.html