Fix SSH key install on RouterOS 6 (v0.24.42)
Key deployment sent /user/ssh-keys/import, the v7 menu-path form. RouterOS 6
answers it with "expected command name", imports nothing, and exits 0. The
output check only looked for failure/error/no such, so the missing key
surfaced later as a failed proof login ("can't find matching key").
- Use space-separated paths (/user ssh-keys import, /file remove,
/system identity print), which v6 and v7 both accept. - importRejection() treats CLI parse errors as a failed import.
- Docs: v6 silently drops Ed25519 keys, so the RSA choice from 0.24.40 stays.
Checked on a RouterOS 6.49.22 CHR (import + key login) and on the v7 TEST
switch (deploy, verify, revoke).
Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com
Container images (published once CI passes):
ghcr.io/2gt-media-group-llc/mikrotik-manager-backend:0.24.42-betaghcr.io/2gt-media-group-llc/mikrotik-manager-nginx:0.24.42-beta
Documentation: https://2gt-media-group-llc.github.io/mikrotik-manager/