Ssh -R keygen 192.168.1.1 solved my problem with the terminal. This is from 2013, so they could have updated. That states cyberduck does not have a real scp mode and thus fails to connect to dropbear ssh. I also noticed that there is a cyberduck ticket:
Where (hostname) is the ip-address or computer name that you are connecting to (which looks to be 192.168.1.1)Īs our friends over in openwrt specified: If the key has changed and you need to fix this in a terminal on your Mac run: It will have to fall back to scp, which is doing an ssh copy, which under the hood opens an ssh session and then does a copy (cp) to the remote/local machine. proftp does not have ssh wrapping so either way you cannot use SFTP to connect to the router or even FTPS (which is FTP but encrypted)
#Cyberduck ssh terminal how to
This dropbear will not know how to understand the ssh secured ftp protocol. This means that either Cyberduck has removed/deprecated the algorithms that dropbear has enabled or vise versa.Įven if you get this algorithm to agree and the keys exchanged, the DD-WRT version of dropbear does not contain the sftp subsystem. I am not a Mac user but a Linux and BSD user, since is a derivative from FreeBSD, there are similarities.įrom Cyberduck is specifying that between the dropbear on the router and its software, the algorithm for exchanging ssh keys was not agreed upon.
0 kommentar(er)
