# SSH Legacy Crypto Login Compatibility

- **URL:** https://hackindex.io/services/ssh/exploitation/ssh-legacy-crypto-login-compatibility
- **Path:** SSH > Exploitation
- **Up:** [Exploitation](https://hackindex.io/services/ssh/exploitation.md)
- **Published:** 2026-01-03
- **Updated:** 2026-01-03

When you have valid creds or a valid key but modern clients won't negotiate, force the legacy algorithms explicitly and keep the session controlled.

The modern OpenSSH client removed `diffie-hellman-group1-sha1` and `ssh-rsa` from its defaults. Connecting to a server that only offers them produces an error such as `no matching key exchange method found` or `no matching host key type found`. That error names the algorithm the server wants. Note it before you add flags.

## When this matters

This shows up on old appliances, unmanaged Linux builds, and “frozen” environments where SSH policy never got updated. The finding is usually not “you exploited SSH”. The finding is “the server requires or still accepts deprecated crypto”.

Common targets requiring legacy crypto overrides:

- Embedded routers and network appliances
- Legacy IPMI and BMC controllers
- Old CI/CD servers with frozen SSH configs
- Network gear running OpenSSH older than 7.0

The server may negotiate perfectly well on its own terms while rejecting every modern cipher your client tries by default.

Keep this tight: prove negotiation, grab what you need, document the accepted algorithms.

## Force legacy KEX and ssh-rsa to establish a session

Use this when you see group1 and ssh-rsa in enumeration, or when your client refuses to connect without overrides.

The `+` prefix on each algorithm value appends to the default list rather than replacing it. Your client still negotiates modern algorithms first and falls back to legacy only when the server requires it.

```bash
ssh -p $PORT -o KexAlgorithms=+diffie-hellman-group1-sha1 -o HostKeyAlgorithms=+ssh-rsa -o PubkeyAcceptedAlgorithms=+ssh-rsa $USERNAME@$TARGET_IP
```

If you only need proof of access without an interactive session, run a benign command and exit:

The three commands give you user context, hostname, and kernel version in one shot. Check the UID field: `uid=0` means root access. Any other UID confirms access under a standard or service account. Record the full output as evidence. Running commands this way avoids an interactive session and generates fewer log entries on the target.

```bash
ssh -p $PORT -o KexAlgorithms=+diffie-hellman-group1-sha1 -o HostKeyAlgorithms=+ssh-rsa -o PubkeyAcceptedAlgorithms=+ssh-rsa $USERNAME@$TARGET_IP 'id; hostname; uname -a'
# uid=1000(user) gid=1000(user) groups=1000(user)
# target-host
# Linux target-host 5.10.0-... x86_64 GNU/Linux
```

## If you're using key-based auth on a legacy-only server

Same problem, different credential type. Combine the identity controls with legacy algorithm flags.

Without `IdentitiesOnly=yes`, the SSH client offers every key in your agent and in `~/.ssh/`. A server with a low `MaxAuthTries` value counts each rejected key as a failed attempt. After enough failures, the server drops the connection before your target key is tried. Adding `IdentitiesOnly=yes` limits the client to the key you specified with `-i`.

```bash
ssh -p $PORT -i id_rsa -o IdentitiesOnly=yes -o KexAlgorithms=+diffie-hellman-group1-sha1 -o HostKeyAlgorithms=+ssh-rsa -o PubkeyAcceptedAlgorithms=+ssh-rsa $USERNAME@$TARGET_IP
```

If you see “Too many authentication failures”, `IdentitiesOnly=yes` is mandatory.

If negotiation still fails after adding KEX and host key flags, the server may restrict additional parameters. Add `-o Ciphers=+aes128-cbc,3des-cbc` to include legacy symmetric ciphers. Some very old servers only accept CBC-mode ciphers and reject all modern AEAD options.

When you still cannot connect, check what the server actually advertises. Run the Nmap `ssh2-enum-algos` script against the target first. Match your `-o` flags to the advertised list exactly. If the key format is the blocker, regenerate it in PEM format. Run `ssh-keygen -p -m PEM -f id_rsa` to convert in place.

Phase boundary: once you're executing payload delivery or persistence actions, stop and put it in a Post-Exploitation or Persistence page. This page is only about establishing access when negotiation blocks you.

## References

- [ssh(1) manual page](https://man.openbsd.org/ssh) - Client algorithm forcing and remote command execution syntax.
- [ssh_config(5) manual page](https://man.openbsd.org/ssh_config) - KexAlgorithms, HostKeyAlgorithms, PubkeyAcceptedAlgorithms.