Martin Algesten
Martin Algesten
and juggle a bunch of cookie stores. hm. could be done. there probably is a better way though... the actual "logging in" to multiple accounts is likely to be straightforward....
Personally I don't store passwords in the keychain, so it would make sense for me to just have the tokens automatically synchronizing that way. But I may be the odd...
> Solutions to 2 _should not_ use The Cloud™. Encrypted backups as they work now do this. A potential other solution is exporting a PGP encrypted file of the secrets...
Great! I googled a bit on keychain on the watch, and it seems that previously you shared keychain with your host app, but now it's a "normal" keychain with icloud...
Right now I'm working on using the exact same keychain persistence in the watch app as on the iPhone. I.e. local keychain based (local, as in local to the watch)....
Here's a quick work in progress. The work is mostly done. Just going to alpha test it myself for a couple of days, and then tidy up my commits. One...
Pull request is in https://github.com/mattrubin/Authenticator/pull/154 This is probably enough for a first release. Worth to note: - It doesn't do HOTP since that would require a round trip to the...
I made the entry screen have the circle countdown animation. Updated the screen grabs above.
my code is in that PR. it's mostly done. the synchronization may need some love.
@PatTheMav It's not a fork. It uses some of Matt's excellent OTP code to generate codes on the watch, but the iOS is (for better or worse) written in react...