Summary
Please add support for deploying DagShell without requiring a password, similar to the implementation used in the RayHunter repository.
Motivation
For many deployments, especially lab environments, appliances, and isolated networks, requiring a password during initial setup adds unnecessary complexity. There are valid use cases where the device is physically controlled or operates on a trusted network.
RayHunter already supports this workflow, and having the same option in DagShell would improve consistency between the projects.
Proposed Solution
Add a configuration option to disable password authentication during deployment.
For example:
- Allow an empty password during provisioning.
- Add a build-time or configuration flag such as DISABLE_AUTH or NO_PASSWORD.
- Mirror the existing implementation from the RayHunter repository.
Benefits
- Faster deployment and testing.
- Better support for isolated lab environments.
- Consistent behavior across DagShell and RayHunter.
- Gives users the choice between convenience and authentication based on their deployment requirements.
Authentication should remain the default behavior, with the passwordless option available only when explicitly selected by the user.
Summary
Please add support for deploying DagShell without requiring a password, similar to the implementation used in the RayHunter repository.
Motivation
For many deployments, especially lab environments, appliances, and isolated networks, requiring a password during initial setup adds unnecessary complexity. There are valid use cases where the device is physically controlled or operates on a trusted network.
RayHunter already supports this workflow, and having the same option in DagShell would improve consistency between the projects.
Proposed Solution
Add a configuration option to disable password authentication during deployment.
For example:
Benefits
Authentication should remain the default behavior, with the passwordless option available only when explicitly selected by the user.