Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Yubikey doesn't work with Brave #3558

Closed
jumde opened this issue Mar 4, 2019 · 12 comments · Fixed by brave/brave-core#1896
Closed

Yubikey doesn't work with Brave #3558

jumde opened this issue Mar 4, 2019 · 12 comments · Fixed by brave/brave-core#1896
Labels
priority/P1 A very extremely bad problem. We might push a hotfix for it. QA Pass-Linux QA Pass-macOS QA Pass-Win64 QA/Yes release/blocking release-notes/include webcompat/not-shields-related Sites are breaking because of something other than Shields.

Comments

@jumde
Copy link
Contributor

jumde commented Mar 4, 2019

Description

Login with U2F keys on Github or Google doesn't work
screen shot 2019-03-03 at 4 04 29 pm

Steps to Reproduce

  1. Setup U2F with Github/Google account using a yubikey
  2. Login with U2F keys

Actual result:

Login doesn't work

Expected result:

Login should work

Reproduces how often:

Easily

Brave version (brave://version info)

0.62.15 Chromium: 73.0.3683.39 (Official Build) dev (64-bit)

Reproducible on current release:

  • Does it reproduce on brave-browser dev/beta builds? Dev

Website problems only:

  • Does the issue resolve itself when disabling Brave Shields? No
  • Is the issue reproducible on the latest version of Chrome? Not on Chrome and Chrome Canary
@jumde jumde added the webcompat/not-shields-related Sites are breaking because of something other than Shields. label Mar 4, 2019
@bbondy bbondy added the priority/P1 A very extremely bad problem. We might push a hotfix for it. label Mar 5, 2019
@rebron rebron added this to the 0.61.x - Beta milestone Mar 5, 2019
@rebron
Copy link
Collaborator

rebron commented Mar 5, 2019

cc: @kjozwiak to reproduce

@kjozwiak
Copy link
Member

kjozwiak commented Mar 5, 2019

Reproducible on 0.61.x as well. I went through both GitHub/Google using macOS 10.14.3 with the following build:

Brave 0.61.45 Chromium: 73.0.3683.39 (Official Build) beta(64-bit)
Revision cc53b0e12fcaf42e4bab8d6c23bd4fb7aae99f6c-refs/branch-heads/3683@{#413}
OS Mac OS X

Examples of the issue occurring on Google when attempting to add a key as authentication:

Chrome Brave
screen shot 2019-03-05 at 5 30 18 pm screen shot 2019-03-05 at 5 33 55 pm

Examples of the issue occurring on Google when attempting to login using an account with a key:

screen shot 2019-03-05 at 5 31 34 pm

Examples of the issue occurring on GH when attempting to add a key as authentication:

screen shot 2019-03-05 at 6 06 00 pm

Examples of the issue occurring on GH when attempting to login using an account with a key:

screen shot 2019-03-05 at 6 08 49 pm

Looks like adding a key or attempting to login using a key isn't working under 0.61.x either. I went through Chrome BETA which is also on CR73 and couldn't reproduce the issue. Seems like this is Brave specific. I didn't have any issues registering a key/logging in using a key under GH/Google using the following build:

Google Chrome 73.0.3683.56 (Official Build) beta (64-bit)
Revision 303af44e2f2948869279f120021c778855d76ead-refs/branch-heads/3683@{#653}
OS Mac OS X

CCing @rebron @bbondy.

@kjozwiak
Copy link
Member

kjozwiak commented Mar 6, 2019

Something to keep in mind. Chrome BETA is currently on 73.0.3683.56 and we're on 73.0.3683.39. Entirely possible that the above issue might have been fixed between those two CR versions.

@bbondy should we bump to 73.0.3683.56 and see if it's resolved?

@kjozwiak
Copy link
Member

kjozwiak commented Mar 6, 2019

Bumping CR #3594. Will retest once we get new builds.

@kjozwiak
Copy link
Member

kjozwiak commented Mar 7, 2019

Bumping CR again via #3608. Will retest when we get new builds which includes 73.0.3683.67.

@corymcdonald
Copy link

Is this the same issue as #1875?

@kjozwiak
Copy link
Member

kjozwiak commented Mar 8, 2019

Is this the same issue as #1875?

Most likely related. Attempted to go through the case mentioned in #1875 and receiving an Operation Cancelled right off the bat. Looking into the console, I see the following:

getClientExtensionResults failed TypeError: Cannot read property 'getClientExtensionResults' of null main.js?e13936b19f427d7ade29:1 
    at main.js?e13936b19f427d7ade29:1
    at main.js?e13936b19f427d7ade29:1

Example of https://demo.yubico.com/webauthn/ under Brave:

screen shot 2019-03-07 at 7 53 56 pm

Example of https://demo.yubico.com/webauthn/ under Chrome BETA:

screen shot 2019-03-07 at 7 53 21 pm

I also tried using Google/Github and received the same results as before, example:

screen shot 2019-03-07 at 7 46 31 pm

Used the following build for the above checks:

Brave 0.61.49 Chromium: 73.0.3683.67 (Official Build) (64-bit)
Revision a83fd4f3207ae83412d329a9ca1239dd1e068345-refs/branch-heads/3683@{#760}
OS Mac OS X

@rebron @bbondy @bsclifton doesn't seem like the CR bump addressed the issue. We'll need to fix this ourselves.

@kjozwiak
Copy link
Member

kjozwiak commented Mar 11, 2019

Verification PASSED on macOS 10.14.3 x64 using the following build:

Brave 0.61.50 Chromium: 73.0.3683.67 (Official Build) (64-bit)
Revision a83fd4f3207ae83412d329a9ca1239dd1e068345-refs/branch-heads/3683@{#760}
OS Mac OS X
  • Added a yubikey under Gmail using 0.61.50 and logged in without issues using the same key
  • Added a yubikey under GitHub using 0.61.50 and logged in without issues using the same key
  • Went through https://demo.yubico.com/webauthn/ and ensured I can register and login using yubikey

Verification PASSED on Mint 19.1 x64 using the following build:

Brave 0.61.50 Chromium: 73.0.3683.67 (Official Build) (64-bit)
Revision a83fd4f3207ae83412d329a9ca1239dd1e068345-refs/branch-heads/3683@{#760}
OS Linux

Verification PASSED on Windows 10 x64 using the following build:

Brave 0.61.50 Chromium: 73.0.3683.67 (Official Build) (64-bit)
Revision a83fd4f3207ae83412d329a9ca1239dd1e068345-refs/branch-heads/3683@{#760}
OS Windows
  • Added a yubikey under Gmail using 0.61.50 and logged in without issues using the same key
  • Added a yubikey under GitHub using 0.61.50 and logged in without issues using the same key
  • Went through https://demo.yubico.com/webauthn/ and ensured I can register and login using yubikey

@aptly-io
Copy link

aptly-io commented Sep 26, 2020

I cannot get Onlykey to work with U2F
On MacOS 10.14.6, Brave V1.14.84, Chromium to 85.0.4183.121
OnlyKey Firmware v0.2-beta.8c
It is as if the device does not get recognised.
It works with Firefox (it does not work on safari) on MacOS
It did work after installing Google Chrome and continued to work after removing Google Chrome.

@jumde
Copy link
Contributor Author

jumde commented Sep 26, 2020

@aptly-io - Does the key work with Google Chrome?

@aptly-io
Copy link

@jumde Sorry, It started working without any obvious changes (I only installed Google Chrome to test as you asked)

@jumde
Copy link
Contributor Author

jumde commented Sep 28, 2020

@aptly-io - That's weird, glad it's working now. If you run into this issue again, feel free to file a new issue. In the meantime, I'll try getting a OnlyKey to test.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority/P1 A very extremely bad problem. We might push a hotfix for it. QA Pass-Linux QA Pass-macOS QA Pass-Win64 QA/Yes release/blocking release-notes/include webcompat/not-shields-related Sites are breaking because of something other than Shields.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants