Frequently Asked Questions (FAQ)
Mindbreeze InSpire Appliances on Hyper Scalers

General

Which SSH Clients can be used to connect?

The support for insecure ciphers has been removed from Mindbreeze InSpire.
This means that you need a recent enough SSH Client to connect:

PuTTY >= 0.74
PuTTY >= 0.78 if RSA keys are used
OpenSSH >= 6.2
OpenSSH >= 6.5 if ed25519 keys are used

Why is the configured SSH Key not working?

Most Cloud Platforms require password authentication to be disabled for SSH access.
Therefore, you need to supply a SSH Public Key on VM creation to be able to access the VM using SSH.

The supported key types are:

RSA with a key length of at least 4096 bits
ED25519

For connecting via SSH, the user “core” has to be used.

Microsoft Azure

Marketplace listings

Mindbreeze InSpire

Mindbreeze InSpire 10M

Why is the configured SSH Key not working?

Due to a change in the API on Azure, the initially configured SSH keys are no longer automatically configured as authorized_keys.

You can use the option Help->Reset Password->Reset SSH public key to set an authorized public key for the user core. The same can be achieved using the Azure CLI:

azure vm reset-access --resource-group myResourceGroup --name myVM --user-name core --ssh-key-file ~/.ssh/id_rsa.pub

How can I get back sudo access after using the Reset Password actions?

Due to a bug in the VMAccess Extension of the Azure Linux Agent the actions Reset Password, Reset Configuration only and Reset SSH public key will remove the user core from its groups.

To address this issue starting from Mindbreeze InSpire 25.3 the user core gets its sudoers rules directly and not just via its groups.

Please update to at least 25.3 before using any of these options.