2 ms·
Why would I want to use this instead of using Google Authenticator with RFC4226 or TOTP (http://tools.ietf.org/id/draft-mraihi-totp-timebased-06.txt http://tool
by drivebyacct2 15y ago
Why would I want to use this instead of using Google Authenticator with RFC4226 or TOTP (http://tools.ietf.org/id/draft-mraihi-totp-timebased-06.txt http://tools.ietf.org/id/draft-mraihi-totp-timebased-06.txt) ?
Looks like Duo has more options for receiving the code as well as the ability to enable manual approve/deny for another user role. It also looks like a private service I have to rely on though.
- tptacek 15y agoIt's not tied to a Google account, it has a better end-user experience, a better developer experience, and an extremely credible team behind it. That said, if you were using Google Auth and I assessed your application, I wouldn't ding you for using it.
- drivebyacct2 15y agoWell the Google Authenticator application is just an implementation. I can use any TOTP generator to get access to my Google Account, or alternatively if I use the PAM module they've provided, I can use whatever I want to generate my codes to log in to my Linux machine. It just so happens that they use this mechanism for their two factor auth for Google Accounts. I definitely hear you on the better user/dev experience. That's very clear from the variety of methods and slick screenshots they've got.
- ceejayoz 15y agoGoogle Authenticator isn't tied to a Google account, and developing for it involves implementing a single algorithm.
- based2 15y agohttp://www.rcdevs.com/products/openotp/compare.php http://www.rcdevs.com/products/openotp/compare.php https://tiqr.org/ https://tiqr.org/