OTP Feature Implementation#503
Open
Sentinel-Android wants to merge 1 commit intolakinduakash:masterfrom
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
One-Time Password (OTP) mode
Tick the new checkbox under the Password field → a cryptographically-random 12-character passphrase is generated every time Create Hotspot is pressed.
The OTP is displayed, copied to the QR dialog, and used for that session only.
Password-restore logic
The user’s original passphrase is cached in memory.
Unticking One-time password restores that original value automatically, so clicking Create Hotspot afterwards never writes an OTP to create_ap.conf.
UI/UX refinements
Password entry is read-only while OTP is active.
Validation and QR-generation paths work transparently with either fixed or one-time passwords.