I've reported both threads as that's a common spammer technique - take an ancient post and re-post it. It would be odd to have two users with identical failures in /etc/rc.local causing their machine to fail to boot.
Thank you very much for your help and support! I appreciate it very much! I will try what you suggest. Have a great and happy 2018. Cheers.jojopi wrote: ↑Sat Dec 30, 2017 12:04 pmThe pictures are not identical, and I do not see how this could possibly be spam.
Clearly both posters have very similar stuff added to rc.local, though. Maybe this is the result of a compromise, as suggested in the original post.
If you do not recognise why the system is attempting to run ssh at boot, then you need to do a fresh Raspbian install. If there are files you want to recover from the existing install, do the fresh install on a new SD card and then mount the old one in a USB card reader.
Also me have identical problem....Juggernoud1 wrote: ↑Sat Dec 30, 2017 9:03 amHi there,
It seems that I have been hacked on my Rapsberry Pi I am unable to login into my Raspberry Pi. I can't typ anything while starting up the Rapsberry Pi.
It keeps sending me new text over and over again while trying to reconnect. It says Connection timed out during banner exchange and then it says lost connection.
Also it tries it connect to different SSH ports without success. In attachment there is a picture of my issue:
I also tried to reset the Pi in the cdmline text file with this: dwc_otg.lpm_enable=0 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait init=/bin/sh
But the main issue is that I can't typ anything while starting up the Raspberry Pi. Also I tried to connect via MyPutty but it's impossible to make connection with the Raspberry Pi.
I hope there is someone with suggestions how to tackle this issue.
Many many thanks in advance!!
Code: Select all
ssh -v [email protected] OpenSSH_6.6.1, OpenSSL 1.0.1f 6 Jan 2014 debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * debug1: Connecting to 192.168.178.38 [192.168.178.38] port 22. debug1: Connection established. debug1: identity file /home/ricman/.ssh/id_rsa type 1 debug1: identity file /home/ricman/.ssh/id_rsa-cert type -1 debug1: identity file /home/ricman/.ssh/id_dsa type -1 debug1: identity file /home/ricman/.ssh/id_dsa-cert type -1 debug1: identity file /home/ricman/.ssh/id_ecdsa type -1 debug1: identity file /home/ricman/.ssh/id_ecdsa-cert type -1 debug1: identity file /home/ricman/.ssh/id_ed25519 type -1 debug1: identity file /home/ricman/.ssh/id_ed25519-cert type -1 debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.8 debug1: Remote protocol version 2.0, remote software version OpenSSH_7.4p1 Raspbian-10+deb9u2 debug1: match: OpenSSH_7.4p1 Raspbian-10+deb9u2 pat OpenSSH* compat 0x04000000 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client aes128-ctr [email protected] none debug1: kex: client->server aes128-ctr [email protected] none debug1: sending SSH2_MSG_KEX_ECDH_INIT debug1: expecting SSH2_MSG_KEX_ECDH_REPLY debug1: Server host key: ECDSA 06:6b:84:c5:ed:63:90:21:31:7b:b8:94:b0:20:f1:a6 debug1: Host '192.168.178.38' is known and matches the ECDSA host key. debug1: Found key in /home/ricman/.ssh/known_hosts:52 debug1: ssh_ecdsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,password debug1: Next authentication method: publickey debug1: Offering RSA public key: /home/ricman/.ssh/id_rsa debug1: Authentications that can continue: publickey,password debug1: Trying private key: /home/ricman/.ssh/id_dsa debug1: Trying private key: /home/ricman/.ssh/id_ecdsa debug1: Trying private key: /home/ricman/.ssh/id_ed25519 debug1: Next authentication method: password [email protected]'s password: debug1: Authentications that can continue: publickey,password Permission denied, please try again. [email protected]'s password: