Conflict between vimium and double authentication
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 27k
- Forks
- 2.6k
- PR merge metrics
- No merged PRs in 30d
Description
Hello !
On github/google with chrome the double authentication by usb key is not a simple form field. As a result the input of the key is handle by viumium. IDK how they deal with chrome (because this doesn't work on firefox according to github) to make their magic happen but looks like issue of vimium !
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source files or tests are identified. Start by reproducing USB-key two-factor authentication on GitHub or Google in Chrome with Vimium enabled, then trace how Vimium handles the authentication interaction; done means the USB-key flow works without breaking normal Vimium behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- authentication, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100