We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
README.md says:
README.md
FIRST_USER_PASS (Default: unset) Password for the first user. If unset, the account is locked.
FIRST_USER_PASS (Default: unset)
FIRST_USER_PASS
Password for the first user. If unset, the account is locked.
However, when I enable DISABLE_FIRST_BOOT_USER_RENAME while not setting FIRST_USER_PASS, it says:
DISABLE_FIRST_BOOT_USER_RENAME
Not setting FIRST_USER_PASS makes your system vulnerable and open to cyberattacks
This doesn't make any sense to me, since disabling login via password (which is what locking the account actually seems to mean in the context of this project - however even if the account would actually be locked, I don't see any vulnerability) should only increase the security of the system.
Proposal:
build.sh
The text was updated successfully, but these errors were encountered:
No branches or pull requests
README.md
says:However, when I enable
DISABLE_FIRST_BOOT_USER_RENAME
while not settingFIRST_USER_PASS
, it says:This doesn't make any sense to me, since disabling login via password (which is what locking the account actually seems to mean in the context of this project - however even if the account would actually be locked, I don't see any vulnerability) should only increase the security of the system.
Proposal:
README.md
to accurately describe what happensbuild.sh
to mention the actual reason for requiring a passwordThe text was updated successfully, but these errors were encountered: