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

All FIDO2 credentials gone #1233

Open
nekromant opened this issue Jul 28, 2024 · 3 comments
Open

All FIDO2 credentials gone #1233

nekromant opened this issue Jul 28, 2024 · 3 comments
Assignees

Comments

@nekromant
Copy link
Contributor

nekromant commented Jul 28, 2024

Expected behavior

No added FIDO2 credentials vanish from the database, unless explicitly deleted

Actual behavior

After a day or two migrating to mooltipass and adding credentials, FIDO2 and credentials tab went empty. Credentials were brought back via running an integrity check, but not FIDO2. I had to manually reset keys and re-add them for all accounts.

Step by step guide to reproduce the problem

Add data for vk social network. It uses vk.com, vk.ru, vkontakte.com, id.vk.ru and id.vk.com domains at the same time weirdly redirecting duing login. Link credentials for id.vk[.com,.ru] and vkontakte.com, add the FIDO2 key. At some moment you'll add up with a broken database.

WARNING: (2024-07-28T17:08:45.770) :0 - Orphan child found: "+XXXXXXXXX" at address: "6c02"
DEBUG: (2024-07-28T17:08:45.770) :0 - Number of parent orphans: 0
DEBUG: (2024-07-28T17:08:45.770) :0 - Number of children orphans: 1
DEBUG: (2024-07-28T17:08:45.770) :0 - Number of data parent orphans: 0
DEBUG: (2024-07-28T17:08:45.770) :0 - Number of data children orphans: 0
INFO: (2024-07-28T17:08:45.770) :0 - Errors were found in the database
CRITICAL: (2024-07-28T17:08:45.770) :0 - Error in our local DB (algo PB?)

Moolticute Version

1.04.0 / 1.03.0

Operating System

Mention if you are using either:

  • Debian Stable

Mooltipass Device

  • The Mooltipass Mini BLE
@deXol
Copy link
Collaborator

deXol commented Jul 30, 2024

@nekromant: I was trying to reproduce the issue based on step by step, but unfortunately I am unable to do that.
Can you reproduce the issue? If yes, can you please attach the log when you are first encountering the issue. (During entering/exiting MMM)
Based on that I would like to investigate what can trigger this problem.

@nekromant
Copy link
Contributor Author

nekromant commented Jul 30, 2024

Got it. Should wiping a profile clean and starting with a new spare smartcard be enough to reset thre device's state?

@limpkin
Copy link
Collaborator

limpkin commented Jul 30, 2024

a blank card will be enough to initialize a new profile :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants