Authentication #61
Open
Authentication #61
Conversation
This file contains 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
… sort of db-like storage
…n easily be faked
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hi,
I have implemented a simple authentication scheme; for unauthenticated users index.php shows the LCD display and the Graph. Any request other than getting graph or LCD data is not be allowed if user is not logged in.
The password checking is very crude (a single username and password pair can be specified in user config file).
The lockout mechanism (after too many failed password attempts) is also crude. I save the number of failed attempts and the lock-out expiry time in a file (this file can be accessed by anyone but not edited).
Cheers