freeotp-devel August 2015

freeotp-devel@lists.fedorahosted.org

10 participants
6 discussions

iOS app not using Keychain?
by Leonardo Brondani Schenkel 31 Aug '15

31 Aug '15

Hi, Is there any reason why the iOS app the NSUserDefaults mechanism to store the secrets instead of the Keychain? It's not really considered a good practice to use the former to store secrets. If there is no strong reason, would a patch that uses the Keychain be considered for inclusion into a future release? Thanks, Leonardo.

2 6

Patch to fix https://fedorahosted.org/freeotp/ticket/51
by Kresten P. Vester 20 Aug '15

20 Aug '15

This patch copies icons to internal storage. That makes it possible to load icons again. It creates a copy of the icon and is therefore no longer dependent on the original source file.

1 0

FreeOTP
by capitan.pronin＠gmail.com 20 Aug '15

20 Aug '15

Hello there! Firstly I want to say you thanks for your app. Well, why only Base 32 secret input? Is it possible to add enter secret in HEX and ASCII? If yes, then when you'll do it? :) Also protect app with pin is nice feature too ;) Have a nice day!

1 0

FreeOTP
by capitan.pronin＠gmail.com 20 Aug '15

20 Aug '15

1 0

FreeOTP Backup
by Jonathan Brown 19 Aug '15

19 Aug '15

I use the IOS of FreeOTP and love the app but would it be possible to add a backup option in case the phone gets lost or stolen? That is the only thing missing with this great app. Thanks

6 8

Android Wear integration?
by Timothy Aveni 03 Aug '15

03 Aug '15

Some apps have awful OAuth sign-in interfaces where leaving the app to get an OTP causes the login cycle to restart, so I need to re-enter my (long) email and (longer) password before I can log in. When my phone lags or I start to mistype my credentials, this starts to become a real problem. This isn't a problem with the design of FreeOTP, of course; it's a problem with the applications that don't have persistent sign-in setups. But if FreeOTP had an Android Wear interface, people with watches connected to their phones could just open up the watch application when they need a code and never have to start a new intent on their phone. This would involve an optional Google Play Services dependency (which is already required by Android Wear). My biggest concern would be sending data over to the watch without exposing the private key to Google's cloud, because many of the messaging APIs allow watch data to sync using Google's servers. Perhaps a better solution would be to send individual OTPs as they are requested by the watch app. I'm not sure how, exactly, this should be implemented, but I would love to see it included in the app. I'd be willing to start development if no one else is interested. Timothy Aveni

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

freeotp-devel August 2015