[discuss] Asymmetric authentication#812
Open
ozsay wants to merge 6 commits intoaccounts-js:masterfrom
Open
Conversation
ozsay
commented
Sep 23, 2019
| @@ -0,0 +1,30 @@ | |||
| # @accounts/password | |||
Contributor
Author
|
@pradel I don't see the circleci check or the github check. is something not working? |
Member
|
Can you try to pull the account-js master branch into yours? (I think you are behind so you don't have the latest github ci config) |
Contributor
Author
|
I'm only ahead of master and i can see the files: https://github.com/ozsay/accounts/tree/asymmetric-authentication/.github/workflows |
Member
I wrote to the GitHub support, looks like this is happening in every pr submitted from a fork... |
Member
darkbasic
force-pushed
the
master
branch
9 times, most recently
from
bdf442b to
3e57ec8
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
this is a new authenticator that will utilize asymmetric cryptography for authenticating users.
The main use case is biometric authentication, following this method.
Another use case may be authenticating by PIN where you don't want to expose the PIN to the server (the PIN is being treated as a private key).
@davidyaha