Tickets :: Comment on [#11076] One Time Password Module Implementation

* Your Email Address
* Spam protection	Enter the letters below: .___._.._.. ,.__. [__ \| \| \./ \| \| \| _\|__\|_ \| \|__\|
Comment	> Dear Dev-Team, > > as announced in #10980, I am trying to provide a first version of a > hash-chain implementation for one time passwords. This is my personal > reason why I would need the Dual_Auth module described previously. > Nevertheless the modules are both fully functional on their own. > > With this otp module a user can log in to horde with another password > every time and thus protect his credentials if he has to log in from > an untrusted location such as an airport internet terminal. > > ATM this uses the same table as Auth_Sql (horde_users) with two > additional fields. If requested this can of course be changed to use > its own table. > ALTER TABLE `horde_users` ADD `hash_chain_pwd` VARCHAR( 60 ) NOT NULL > ALTER TABLE `horde_users` ADD `hash_chain_index` INT( 50 ) NOT NULL > > I am posting this at this state mainly to get feedback on the idea > and the implementation. I am by all means willing to improve it from > a security, architectural, or even style point of view. > > Further additions in terms of support in the passwd application, > warnings when the password list runs empty and integration in the > configuration page are planned if this is of common interest. > > Any comment is appreciated. > Best regards, > Carl
Attachment
Watch this ticket