← Back to context

Comment by rhubarbtse

3 days ago

I gave it a go (A1200+AmiTCP 4.3), doesn't seem to work unfortunately and I can't seem to find any issue tracker on the website.

3.RAM Disk:bebbossh> bebbossh user@10.0.0.1

[2025.11.26-09:10:01.280] [INFO ] can't open `envarc:.ssh/ssh_config`

[2025.11.26-09:10:01.640] [ERROR] can't read 4 uint8_t header, got 0

[2025.11.26-09:10:01.647] [ERROR] can't read SSH_MSG_KEX_ECDH_REPLY

ERROR: 16 - tcp read failed

4 comments

rhubarbtse

Reply
indigo945  3 days ago

The program seems to call gethostbyname() on the supplied host, so you may want to try providing a DNS name instead.

Also, call with -v8 to get more detailed logging.

  • rhubarbtse  3 days ago

    Hostname is not the issue, it can connect and then fails some handshake or whatever. Adding verbosity just seems to hexdump the packets in addition to logging an error.

    [2025.11.26-09:10:21.460] [FINE ] got server SSH_MSG_KEX_ECDH_INIT

    sending: length = 48

    0000 00 00 00 2C 06 1E 00 00 00 20 D0 91 2C 8F 57 AF ...,..... ..,.W.

    0010 91 B2 F9 C5 77 42 30 D1 2E A5 A0 B2 C6 C8 76 4C ....wB0.......vL

    0020 5F 32 27 E7 1F 0D A2 32 C0 3A 00 00 00 00 00 00 _2'....2.:......

    [2025.11.26-09:10:21.520] [FINE ] sent server SSH_MSG_KEX_ECDH_INIT

    [2025.11.26-09:10:21.533] [ERROR] can't read 4 uint8_t header, got 0

    [2025.11.26-09:10:21.540] [ERROR] can't read SSH_MSG_KEX_ECDH_REPLY

    [2025.11.26-09:10:21.554] [FINE ] bye bye

    ERROR: 16 - tcp read failed