iOS app not using Keychain?
by Leonardo Brondani Schenkel
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.
8 years, 3 months
FreeOTP
by capitan.pronin@gmail.com
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!
8 years, 3 months
FreeOTP
by capitan.pronin@gmail.com
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!
8 years, 3 months
FreeOTP Backup
by Jonathan Brown
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
8 years, 3 months
Android Wear integration?
by Timothy Aveni
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
8 years, 4 months