Open merikan opened 7 years ago
Thanks for reporting. I have a U2F key sat on my desk in anticipation for getting this to work!
This is a bug with Electron, I do not believe you can fix this, @Thomas101.
I have the same problem. The weird thing that Google was showing me a couple of other options when the MFA times out. Now, I keep stuck in the login screen and I cannot log in to my Gmail
@mabdelfattah I've pushed a fix out to the beta channel (4.10.7)(https://wavebox.io/kb/beta-channel) which will cause it to timeout as it did previously. We do have a permanent fix for this allowing sign-in with a security key and are expecting it to land late summer/early august.
Any fix for this in non beta?
It's shipped in stable versions 4.11.0 - 4.11.3 so if you're running the latest version it should be in there.
It still only times out and offers an alternative method. We've got a fix for U2F keys coming early autumn
Oh okay I will check my version. It does timeout, it is just the length that is of concern. The timeout use to be nearly 10 seconds about 6 months ago, now it feels like 60 seconds.
On Wed., Aug. 28, 2019, 7:09 a.m. Thomas Beverley, notifications@github.com wrote:
It's shipped in stable versions 4.11.0 - 4.11.3 so if you're running the latest version it should be in there.
It still only times out and offers an alternative method. We've got a fix for U2F keys coming early autumn
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/wavebox/waveboxapp/issues/196?email_source=notifications&email_token=ABMJBTPHJ5CPIT3RYA3H7GDQGZ2JRA5CNFSM4DMDBB32YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5LB6LI#issuecomment-525737773, or mute the thread https://github.com/notifications/unsubscribe-auth/ABMJBTNDYITARYLZMZLGTATQGZ2JRANCNFSM4DMDBB3Q .
Unfortunately that's the length that Google has set, it doesn't surprise me that they've changed it over recent months.
We do support the standards implementation of the U2F protocol, but Google sign-in uses a built in extension that's baked into Chrome
Oh okay, that makes sense
On Wed., Aug. 28, 2019, 7:40 a.m. Thomas Beverley, notifications@github.com wrote:
Unfortunately that's the length that Google has set, it doesn't surprise me that they've changed it over recent months.
We do support the standards implementation of the U2F protocol, but Google sign-in uses a built in extension that's baked into Chrome
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/wavebox/waveboxapp/issues/196?email_source=notifications&email_token=ABMJBTIEGUDGLAMHOXKLLOTQGZ54LA5CNFSM4DMDBB32YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5LE5PY#issuecomment-525749951, or mute the thread https://github.com/notifications/unsubscribe-auth/ABMJBTMK3CILJIQG6REWSFTQGZ54LANCNFSM4DMDBB3Q .
I still have this issue and it is painfully disruptive to workflow.
I am using a Security Key (YubiKey) to protect my Google Account but it doesn't work with Wavebox, see image below. I can use another method to login but it fails when trying to use a Security Key.