Hello, i just Pwned my iPhone. Made a custom firmware which i set to install BSD subsystems, OpenSSH and Installer. Everything works great except SSH'ing into the iPhone. When i connect to phone by Transmit(on my mac) it just says:

After i click "OK" the message just pops up again after a couple of seconds.

Then i tried installing openSSH from install hoping it would overwrite the Pwnage OpenSSH installation, but no...Still the same message. Any tips that might solve the problem?

Originally Posted by tarque

Hello, i just Pwned my iPhone. Made a custom firmware which i set to install BSD subsystems, OpenSSH and Installer. Everything works great except SSH'ing into the iPhone. When i connect to phone by Transmit(on my mac) it just says:

After i click "OK" the message just pops up again after a couple of seconds.

Then i tried installing openSSH from install hoping it would overwrite the Pwnage OpenSSH installation, but no...Still the same message. Any tips that might solve the problem?

Dont know why Transmit is not kicking it out. It`s a left over from your SSH/SFTP connection before.
Fire up Terminal on your Mac and type

sudo rm ~/.ssh/known_hosts

to remove the old hosts list. then start Transmit again, should work then.

volkspost

Thank you!! Worked great, repped!

Originally Posted by tarque

Thank you!! Worked great, repped!

Thx. Just to explain. The file that prevented Transmit from working correct is sitting on your Mac. It has listed "trusted" connection partners (host, iPhone) with a unique kind of id (host key).
After you changed your iPhone (pwnged it) Transmit, terminal and other apps get the information, that the (old) host key changed (is setup by openSSH on the iPhone on first connection with your Mac).
Thats the information Transmit provided about the file "known_hosts" on your Mac. Thats why installing OpenSSH on the iPhone does not help. Usually when hitting "OK" in Transmit the program deletes the old host key entry and accepts the new one. I am using transmit for ever, never had it popping up the message again.
So the solution was to delete the file on the Mac. A new one is generated when you sucessfully loged into the iPhone from your Mac.

Best,
volkspost