Netcatty supports legacy SSH algorithms for compatibility with older network equipment like switches, routers, and embedded systems that don’t support modern cryptographic standards.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/binaricat/Netcatty/llms.txt
Use this file to discover all available pages before exploring further.
Overview
Modern SSH implementations disable weak algorithms for security. However, many network devices (especially older Cisco, HP, Juniper equipment) only support these legacy algorithms. Netcatty provides a per-host toggle to enable these algorithms when needed.Enabling Legacy Algorithms
Per-Host Configuration
In the host details panel:- Open the host you want to configure
- Scroll to Advanced Settings
- Enable Legacy SSH Algorithms
- Save the host configuration
Host model:
Supported Algorithms
When legacy algorithms are enabled, Netcatty adds the following to the SSH handshake:Key Exchange Algorithms
Standard (always enabled):curve25519-sha256,curve25519-sha256@libssh.orgecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521diffie-hellman-group14-sha256diffie-hellman-group16-sha512,diffie-hellman-group18-sha512diffie-hellman-group-exchange-sha256
diffie-hellman-group14-sha1- Widely supported on older equipmentdiffie-hellman-group1-sha1- Very old equipment (weak, use only if necessary)
Cipher Algorithms
Standard (always enabled):aes128-gcm@openssh.com,aes256-gcm@openssh.comaes128-ctr,aes192-ctr,aes256-ctr
aes128-cbc- Common on older Cisco devicesaes256-cbc- Legacy encryption3des-cbc- Very old equipment (slow, use only if necessary)
Host Key Algorithms
Legacy (when enabled):ssh-rsa- RSA with SHA-1 (deprecated but widely supported)ssh-dss- DSA keys (very weak, use only if no alternative)
ssh-ed25519,ecdsa-sha2-nistp256/384/521rsa-sha2-512,rsa-sha2-256
Implementation
The legacy algorithm support is implemented inelectron/bridges/sshBridge.cjs:
buildAlgorithms() function:
When to Enable
Network Equipment
Network Equipment
Common scenarios:
- Older Cisco switches and routers (IOS versions before 15.x)
- HP ProCurve switches
- Legacy Juniper devices
- Dell PowerConnect switches
- Older F5 load balancers
- “no matching key exchange method found”
- “no matching cipher found”
- “no matching host key type found”
Embedded Systems
Embedded Systems
Common scenarios:
- Older Linux-based appliances
- Serial console servers
- KVM-over-IP devices
- PDU (Power Distribution Units)
- Environmental monitoring systems
- Devices running BusyBox with dropbear SSH
- Firmware that hasn’t been updated in years
- Documentation mentioning “SSH v2 only” without algorithm details
Industrial Equipment
Industrial Equipment
Common scenarios:
- Industrial PLCs with SSH
- Building automation systems
- SCADA systems
- Legacy server management cards (iLO, DRAC, iDRAC)
Security Considerations
Risks
- Weak encryption: CBC mode ciphers are vulnerable to certain attacks
- SHA-1 weaknesses: Key exchange using SHA-1 is considered weak
- DSS keys: DSA is cryptographically weak compared to modern algorithms
- 3DES performance: Very slow and provides limited security
Mitigation Strategies
- Use per-host configuration: Only enable legacy algorithms for specific hosts, not globally
- Network isolation: Keep legacy equipment on isolated management networks
- Upgrade when possible: Update device firmware to support modern algorithms
- VPN tunneling: Use a VPN to add an extra encryption layer
- Limit exposure: Don’t expose legacy SSH services to the internet
- Monitor connections: Keep connection logs for security audits
Troubleshooting
Connection Fails Even with Legacy Algorithms
If you still can’t connect after enabling legacy algorithms:-
Check the error message carefully:
- “no matching MAC found” - MAC algorithm issue (rare)
- “connection reset” - May be authentication, not algorithm issue
- “timeout” - Network/firewall problem, not algorithm issue
-
Verify device SSH configuration:
-
Test with OpenSSH manually:
-
Check known_hosts conflicts:
- Clear old host keys if device was reinstalled
- See Security Best Practices
Performance Issues
Legacy algorithms can be slower:- 3DES is particularly slow (avoid if possible)
- Use AES-CBC instead if the device supports it
- DH-group1 is faster than group14 but weaker (use group14 if possible)
Common Device-Specific Settings
Cisco IOS (older versions)
HP ProCurve (older firmware)
Dropbear SSH (embedded Linux)
Upgrading Devices
When possible, upgrade device firmware to support modern algorithms:Cisco IOS
Linux (OpenSSH Server)
Further Reading
- Mozilla SSH Guidelines - Modern SSH hardening
- NIST SP 800-52 - Guidelines for TLS/SSH
- Cisco SSH Configuration Guide
