Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"no suitable key exchange algorithm could be agreed" when connecting to server via SFTP #367

Open
MoralCode opened this issue Apr 5, 2016 · 12 comments

Comments

@MoralCode
Copy link

mac OSX version 10.11.3
Astana studio build: 3.6.1.201410201044

i get this error whenever I try to connect to an SFTP server using an SSH key that has already been setup (and tested through the terminal application). i tried unchecking the "Use public key authentication" box (under properties for the SFTP server) but when i save and reopen properties, it just goes back to what it was set to before...

@MoralCode
Copy link
Author

screen shot 2016-04-05 at 2 34 25 pm
i just tried creating a test sftp connection with just a regular password, no ssh key and it gave me the same error, so i don't think its an ssh key issue...

@MoralCode MoralCode changed the title no suitable key exchange algorithm could be agreed "no suitable key exchange algorithm could be agreed" when connecting to server via SFTP Apr 5, 2016
@tristan128
Copy link

Aptana only carries support for 1 (?) cipher, the diffie-hellman one. Most SSH servers don't support this cipher anymore.

@MoralCode
Copy link
Author

so how do i fix this?

@schulzj01
Copy link

I'm wondering about this as well. I'm no longer able to connect to some remote systems as those old ciphers are obsolete and have security patches have disabled them on many machines. Will this ever be fixed, or is Aptana basically an abandoned project, and we need to look for a different IDE?

@MoralCode
Copy link
Author

I already abandoned it long ago in favor of brackets (brackets.io) by Adobe.

Im using the synapse plugin for Sftp access to my website...

@johndekroon
Copy link

Any update?

@MoralCode
Copy link
Author

@johndekroon haven't tested this recently.

@vasc0x
Copy link

vasc0x commented Oct 12, 2016

This worked for me: https://nikinuryadin.wordpress.com/2015/05/19/aptana-studio-3-sftp-key-exchange/

@willruss1
Copy link

I've used aptana for years, since v2.something. I really liked it... until this broke it for me.

I'm not going to re-introduce outdated, insecure KEX protocols to my webservers just because the sFTP / ssh libs can't be updated in the IDE.

Sad to see you go, Aptana but I guess it's time for a full-time switch to Atom.

@cyrilbkr
Copy link

Update ?

@vientosdepoder
Copy link

i have tried what user vasc0x sugested, but didn' t worked for me... then I deleted /home/federico/.ssh/known_host file, and stablished an sftp connection from the terminal : sftp user@host . it created the file again... then i could connect to my server in aptana correctly... i do not recomend you to do what i did... you may loose other server keys... buy they easily can be recover doing sftp from the terminal when prompted
The authenticity of host '[XXX]' can't be established.
ECDSA key fingerprint is XX:XX:XX...
Are you sure you want to continue connecting (yes/no)?
answering yes....

@laxmikantra
Copy link

Hey @vasc0x - It worked like a charm. Can you tell me what it does exactly?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

9 participants