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

Nexus v.3.14 Linux Pin Lock Unlocks with at least 1 character #245

Open
NamecoinGithub opened this issue Oct 25, 2024 · 1 comment
Open
Assignees
Labels
bug Something isn't working

Comments

@NamecoinGithub
Copy link

NamecoinGithub commented Oct 25, 2024

Describe the bug

After logged in and Screen Lock enabled, the REAL Pin is Not required to unlock Nexus Wallet

To Reproduce
If applicable steps to reproduce the behavior:

I typed wrong password, but unlocked, than I just typed 1 character and it let me in without the Real Pin that is set in Nexus!

Expected behavior
I expected the Username Sign-On Pin to be required to Unlock if the Pin Screen calls for it!

But maybe if the intention is simple ease of use, with the 1 character Pin, I did verify that this doesn't allow sending any NXS using a 1 character Pin, this is ONLY regarding the Pin Screen Lock/Unlock "Pin" Function!

But if you could make this a Secondary Falcon Pin for the Screen Lock/Unlock Function using 1 time keys, that DON'T need to be stored on the Blockchain Disc Space but under a new Locked down subset under the Login User Blockchain State to manage the Falcon Keys for the Screen Lock and Unlock Function but maybe Limit the actual size to a simple 4-12 Pin Characters for EASE of Use for Simple Falcon Crypto Secured Screen Lock with Independent "Screen Lock Simple Pin"

This would require possibly new code to tie it together with the Falcon Pins, under a New Class called "Simple Pin" and completely different from the Regular "Spend Pin" Falcon Keys, but still all processed under the Same 1 Login User Blockchain State update!

Additional context
I still had to download the Database and failed to Sync the Blockchain from Scratch as it seems impossible to get passed a early certain known reported block already, and is still persistent!

@NamecoinGithub
Copy link
Author

But, I want to thank you guys for getting this feature done! Once it's working how it should, this is the Best Advancement for UI Staking IMO...........I love it from a Defensive Hacker perspective!

@KenCorma KenCorma self-assigned this Dec 12, 2024
@Qrysto Qrysto added the bug Something isn't working label Jan 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants