fix: Human-Friendly Kiosk Passwords #556
Open
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
It is a lot easier for someone to enter 16 characters of base64 than 64 characters of hex, for kiosks that cannot be deployed by an automated platform. This is just as secure.
|
So the way it was designed for the techroom tablet (which I don't know where that ended up) is that this password is stored in an HTML file for a browser in kiosk mode. This HTML file logs in the user by going to a login URL. That way it logs itself in at boot but the user never sees or types the key. If this is for the TV in techroom (which is not locked in a kiosk mode), then this authentication scheme is not the right one because someone could easily find and copy this key and take it elsewhere. For the case of a shared machine (not dissimilar to SM box, etc.) short-lived user sessions may make more sense? Or maybe we need IP address filtering. |
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.
It is a lot easier for someone to enter 16 characters of base64 than 64 characters of hex, for kiosks that cannot be deployed by an automated platform. This is just as secure.