"Server does not support diffie-hellman-group1-sha1 for keyexchange"

[matthew-dews]

trafficstars

Does Terminals only have support for diffie-hellman-group1-sha1 keyexchange? It is considered a less secure legacy option and is rarely enabled by default on modern distributions. Having to enable the keyexchange on remote servers seems like a bad approach because it is less secure.

[goncalvesc]

Maybe is a good way release putty integration?

[skewty]

Is 4.1 going to be a target Milestone for putty.exe integration?

We cannot enable this on our servers so the SSH feature is essentially useless. I would expect any servers deployed in the last few years would also be configured in a way that the current SSH integration would not work.

[orware]

I was just trying to connect to a newer Ubuntu 16.04 VM and ran into this same issue when testing out Terminals a few moments ago.

This seemed like it'd be a great tool, but it does limit its utility if the SSH stuff doesn't work automatically out of the box.

It might potentially be a good replacement for Microsoft's Remote Desktop Connection Manager for me too, but I haven't tested out the RDP functionality yet.

[skewty]

Is the putty integration as commited in 0377d3466d71ec79d175f35fa30233d12086743d ready for testing yet?

[pauloacsilva68]

Hello. Any news on this issue?

[brendantay]

Is there any update to this?

[pauloacsilva68]

@brendantay. I had to go back to mRemoteNG because if this.

[matthew-dews]

Duplicate issue: #83

Solution being worked on in #46

[vmario89]

i am looking forward too to see PuTTY / KiTTY integration. This may cause that i switch over from mRemoteNG to Terminals

[EurekaChen]

when will this problem resolved?

[MaoX17]

any update?

[aswzen]

any update? its a simple ssh connection though

[Yamakasi]

any update? its a simple ssh connection though

The reason why I switched to mRemoteNG back the days and I think I need to do again... :(