two_factor_authentication

13 Tags

466 KiB

Tree: e136495836

Author	SHA1	Message	Date
baarkerlounger	e136495836	Hard fork and rename project	3 years ago
Sam Clegg	2df6fa2481	Prevent reuse of TOTP codes (#94 ) This change updates the rotp version which now includes support for preventing TOTP code reuse via tracking the timestamp of the last used code.	8 years ago
Sam Clegg	eed1bf62a1	Add support for directly delivered OTP codes Direct OTP codes are ones that are delivered directly to the user (e.g. SMS) via send_two_factor_authentication_code. These are randomly generated, short lived, and stored directly in the database. TOTP (and the rotp gem) is now only enabled for those user that have a shared secret (user.create_otp_secret).	9 years ago
Moncef Belyamani	d2b6d39d24	Add support for OTP secret key encryption Why: To provide an additional layer of security. The TOTP spec (RFC 6238) recommends encrypting the keys. http://tools.ietf.org/html/rfc6238 How: Borrow the encryption code from the `attr_encrypted` gem and use it to encrypt and decrypt the `otp_secret_key` attribute. Allow users to add encryption by passing in `encrypted: true` to `has_one_time_password`. This provides backwards-compatibility for existing users of the gem. See the README updates for more detailed instructions for both new and existing users.	9 years ago
Matt Mueller	3e501a30b2	Misc renames for otp secret key.	11 years ago
Carlos Vilhena	bf9f970cb6	refactor the schema	13 years ago
Dmitrii Golub	e4c812ad6d	first commit	13 years ago