We’ve encountered an issue regarding SSH access in development mode. Our setup involves using devices in development mode with SSH keys added in the
config.json file. This approach is intended to streamline the transition to production mode while still providing SSH access to non-Balena users on production devices.
Issue Encountered: From our understanding, when a device is in development mode, SSH access should not require SSH keys. However, we’ve found that even in development mode, if an SSH key is specified in the
config.json file, the device seems to ignore the
developmentMode flag and continues to enforce SSH key authentication.
- Is this behaviour expected, i.e., does specifying an SSH key in the
config.jsonoverride the development mode’s typical non-key SSH access?
- If this is expected, are there any recommended workarounds to maintain easy SSH access in development mode while still preparing for a seamless switch to production mode?