We are experiencing intermittent authentication failures with our Chisel server, specifically after updating the users.json file to add new users. This issue causes all clients to be unable to authenticate, displaying the error: "ssh: handshake failed: ssh: unable to authenticate, attempted methods [none password], no supported methods remain."
Steps to Reproduce
Run Chisel server with authentication enabled, using a users.json file for user management.
Update users.json by adding new user credentials.
After updating, Chisel clients experience authentication failures with the above error message.
Restarting the Chisel server resolves the issue temporarily.
Expected Behavior
Updating the users.json file should not disrupt the ongoing authentication process, and new users should be able to authenticate without requiring a server restart.
Actual Behavior
Upon updating the users.json file, all clients, including those with existing valid credentials, are unable to authenticate until the Chisel server is restarted.
Additional Information
Chisel server and client versions: 1.9.1
Server OS: Kubernetes Cluster in GCP (linux) (Kernel Version: 5.15.133+)
Client OS: Ubuntu 20.04.6 LTS
Frequency of the issue: Occurs randomly upon updating users.json.
Any patterns noticed: Issue persists even after reverting the users.json file to its previous state.
I am seeking guidance on why this issue occurs and how to prevent it from happening in the future. Any insights or suggestions from the community would be greatly appreciated.
Description
We are experiencing intermittent authentication failures with our Chisel server, specifically after updating the
users.jsonfile to add new users. This issue causes all clients to be unable to authenticate, displaying the error: "ssh: handshake failed: ssh: unable to authenticate, attempted methods [none password], no supported methods remain."Steps to Reproduce
users.jsonfile for user management.users.jsonby adding new user credentials.Expected Behavior
Updating the
users.jsonfile should not disrupt the ongoing authentication process, and new users should be able to authenticate without requiring a server restart.Actual Behavior
Upon updating the
users.jsonfile, all clients, including those with existing valid credentials, are unable to authenticate until the Chisel server is restarted.Additional Information
users.json.users.jsonfile to its previous state.I am seeking guidance on why this issue occurs and how to prevent it from happening in the future. Any insights or suggestions from the community would be greatly appreciated.
Thank you!