Windows: login screen is skipped, cannot unlock private key #713
Labels
No labels
Blocked
Bug
Documentation
Duplicate
Enhancement
Good first issue
Help wanted
Idea
In progress
Invalid
Major feature set
Packaging
Question
Soon
UI/UX
Upstream
You're dreamin'
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
nostr/gossip#713
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
When I run on windows, it goes straight to the feed. The login screen is skipped, and there is no way I can unlock my private key.
So in my case, the database was storing under the key "encrypted_private_key" the value "0". I have no idea how that happened, but I think whatever bug did it also did it to another user I tried to support in my DMs.
We just need to treat this situation the same as if there was nothing under that key in all cases, not just in some cases, so that they can add a private key later.
Ok I intentionally corrupted my epk, and it behaves correctly. I can import the epk. I wonder why I didn't see that on windows.
Ok this is closed.