[Bug]: HASHED_PASSWORD vs SUDO_PASSWORD_HASH; Same hash string provided but only the HASHED_PASSWORD works...

Is there an existing issue for this?

• I have searched the existing issues

OS/Web Information

• Web Browser: Chrome
• Local OS: windows 10
• Remote OS Debian 11:
• Remote Architecture: amd64
• local build from dockerFile.

Steps to Reproduce

1. define both has environment fields to the same value using $$ rather than $ and no enclosing “”
2. access web portal and used initial value to login- successfully
3. run sudo apt update using the same value - Fails

Expected

Should perform an apt update

Actual

3 attempts then kicks out due to excessive password attempts

Logs

No response

Screenshot/Video

No response

Does this issue happen in VS Code or GitHub Codespaces?

• I cannot reproduce this in VS Code.
• I cannot reproduce this in GitHub Codespaces.

Are you accessing code-server over HTTPS?

• I am using HTTPS.

Notes

No response

[CtheCondor]

Absolutely sorry about the confusion! For what it’s worth I found if I used an openssl hashing algorithm; it’s output worked in the sudo_hash field but not the one using the argon2-cli hashing like your code server base image uses. P.S. do you have any documentation on doing local builds from a dockerfile on your page? If not there may be some benefit of adding those details; just mentioned since this was tagged as documentation related xD

[jsjoeio]

argon2-cli hashing like your code server base image uses

Ah darn…argon2 has been troublesome these days 😂

P.S. do you have any documentation on doing local builds from a dockerfile on your page

I don’t think so 🤔 You could look at this. Haha fair! PRs welcome 😉 (you know better than me what you wish were in the docs)