users.server_admin.password is configured in plain text, but it would be better to have it as a hash. This would typically use bcrypt or some other algo if pangolin uses something different under the hood.
For backwards compatibility, maybe introduce users.server_admin.passwordHash? Also make this the default installer behavior, and document how to generate the hash (work factor, etc.) for manual installation.
Reason: Plain text passwords are readable by anyone who gains access to the config file. If the file is leaked or compromised, the attacker immediately knows the password. On the other hand, since bcrypt is a one-way hashing algo, the original password cannot be directly recovered from the hash.
Originally created by @dystopiandev on GitHub (Jun 26, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/974
`users.server_admin.password` is configured in plain text, but it would be better to have it as a hash. This would typically use bcrypt or some other algo if pangolin uses something different under the hood.
For backwards compatibility, maybe introduce `users.server_admin.passwordHash`? Also make this the default installer behavior, and document how to generate the hash (work factor, etc.) for manual installation.
Reason: Plain text passwords are readable by anyone who gains access to the config file. If the file is leaked or compromised, the attacker immediately knows the password. On the other hand, since bcrypt is a one-way hashing algo, the original password cannot be directly recovered from the hash.
@oschwartz10612 commented on GitHub (Jun 27, 2025):
This will be resolved in the next release! Thanks for your issue!
<!-- gh-comment-id:3013028607 -->
@oschwartz10612 commented on GitHub (Jun 27, 2025):
This will be resolved in the next release! Thanks for your issue!
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @dystopiandev on GitHub (Jun 26, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/974
users.server_admin.passwordis configured in plain text, but it would be better to have it as a hash. This would typically use bcrypt or some other algo if pangolin uses something different under the hood.For backwards compatibility, maybe introduce
users.server_admin.passwordHash? Also make this the default installer behavior, and document how to generate the hash (work factor, etc.) for manual installation.Reason: Plain text passwords are readable by anyone who gains access to the config file. If the file is leaked or compromised, the attacker immediately knows the password. On the other hand, since bcrypt is a one-way hashing algo, the original password cannot be directly recovered from the hash.
@oschwartz10612 commented on GitHub (Jun 27, 2025):
This will be resolved in the next release! Thanks for your issue!