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.

Sign up for GitHub

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

Jump to bottom

The tool cannot connect to ASM on Android 11+ #680

Open
5 of 17 tasks
aregs opened this issue Jul 28, 2022 · 0 comments
Open
5 of 17 tasks

The tool cannot connect to ASM on Android 11+ #680

aregs opened this issue Jul 28, 2022 · 0 comments
Labels
BLOCKED Cannot be reproduced or lacks critical information to proceed

Comments

@aregs
Copy link

aregs commented Jul 28, 2022 •
edited by iirachek
Loading

By submitting this issue you are acknowledging that any information regarding this issue will be publicly available.

If you have privacy concerns, please email [email protected]

FIRST PRE CHECK

  • I SOLEMNLY SWEAR THAT I HAVE SEARCHED DOCUMENTATION AND WAS NOT ABLE TO RESOLVE MY ISSUE

What protocol are you implementing?

  • FIDO2 Server
  • CTAP2.0
  • CTAP2.1
  • UAF 1.1
  • U2F 1.1
  • U2F 1.2

NOTE: UAF 1.0 certification have been officially sunset. U2F 1.2 only supported version of U2F.

What is your implementation class?

  • Security Key / FIDO2 / U2F authenticators
  • Server
  • UAF Client-ASM-Authenticator combo
  • UAF Client
  • UAF ASM-Authenticator

If you are platform authenticator vendor, please email [email protected]

What is the version of the tool are you using?

What is the OS and the version are you running?

For desktop tools

  • OSX
  • Windows
  • Linux

For UAF mobile tools

  • iOS
  • Android

Issue description

Starting from Android 11 it is required to specify with intent filters in the application AndroidManifest file. That parameter is missing in tool's manifest file, so it cannot connect to ASM on devices running Android 11+. Tests pass on older versions of Android.
@yackermann yackermann added the BLOCKED Cannot be reproduced or lacks critical information to proceed label Sep 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
BLOCKED Cannot be reproduced or lacks critical information to proceed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@yackermann @aregs