Windows: login screen is skipped, cannot unlock private key #713

Closed
opened 2024-04-15 11:11:42 +12:00 by mikedilger · 2 comments
mikedilger commented 2024-04-15 11:11:42 +12:00 (Migrated from github.com)

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.

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.
mikedilger commented 2024-04-16 13:42:26 +12:00 (Migrated from github.com)

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.

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.
mikedilger commented 2024-04-16 13:50:40 +12:00 (Migrated from github.com)

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.

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.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
nostr/gossip#713
No description provided.