search for: ssh_old_dhgex

On Fri, May 22, 2015 at 12:27:01, Darren Tucker <dtucker at zip.com.au> wrote: > Note that PuTTY does do Diffie-Hellman Group Exchange, but until very > recently (ie after their 0.64 release) they didn't do the one that was > actually standardized in RFC4419. OpenSSH recently removed support for > that non-standard one and as a result we don't offer DHGEX to PuTTY >

Hi All, I am trying to decode the message received from openssh client 3.1.0 Following is the third message which I received. length = 0000 008c padding length = 06 messagetype = 1e (SSH2_MSG_KEX_DH_GEX_REQUEST_OLD) padding = b8 218e c680 and the next four byte should have the n which is 0000 0080 which is less than 1024. 0000 008c 061e 0000 0080 2a19 a9e4 05fb aee2 b107 4fa9 f0c1 83d3 3bf0

...; "WinSCP_release_5.7," "WinSCP_release_5.7.1," "WinSCP_release_5.7.2," "WinSCP_release_5.7.3," "WinSCP_release_5.7.4", SSH_OLD_DHGEX }, Unfortunately the "WinSCP_release_5.1*" mask inadvertently matches even the latest branch of WinSCP 5.10 with version string like "WinSCP_release_5.10.4". Can you please change the masks to require a dot? { "WinSCP_release_4*," &...

...nSCP_release_5.1* > > WinSCP_release_5.2* > > WinSCP_release_5.5* > > WinSCP_release_5.6* > > WinSCP_release_5.7 > > WinSCP_release_5.7.1 > > WinSCP_release_5.7.2 > > WinSCP_release_5.7.3 > > WinSCP_release_5.7.4 We need to add these to compat.c with SSH_OLD_DHGEX -- You are receiving this mail because: You are watching the assignee of the bug. You are watching the reporter of the bug.

Hello, I'd like to inform you that the next release of WinSCP SFTP client (version 5.7.5) will support Diffie-Hellman group exchange as specified by RFC 4419. http://winscp.net/tracker/show_bug.cgi?id=1345 So I'd like to ask you to kindly update the check in compat_datafellows() to WinSCP_release_4* WinSCP_release_5.0* WinSCP_release_5.1* WinSCP_release_5.2* WinSCP_release_5.5*

On Sun, Feb 11, 2018 at 11:27 PM, Darren Tucker <dtucker at dtucker.net> wrote: > Sigh. If you could provide the server's identity string (eg from "ssh > -v yourthing") we could add a bug bit to stop it from being sent. $ ssh -v nathan at 10.0.0.1 OpenSSH_7.4p1, LibreSSL 2.5.0 [snip] debug1: Local version string SSH-2.0-OpenSSH_7.4 debug1: Remote protocol version

On Sun, Apr 15, 2018 at 06:38:37PM +1000, Damien Miller wrote: > On Sat, 14 Apr 2018, Colin Watson wrote: > > This isn't an OpenSSH bug, but just in case anyone else is ambitious > > enough to automatically run interoperability tests against other SSH > > implementations, here's a heads-up: > > > > https://twistedmatrix.com/trac/ticket/9422 > >

...OS: Linux Status: NEW Severity: enhancement Priority: P5 Component: sshd Assignee: unassigned-bugs at mindrot.org Reporter: jrouman at gmail.com Please consider adding "PuTTY_Local*" to the PuTTY versions allowed to use SSH_OLD_DHGEX in compat.c. This is the ID for iSSH and the PuTTY distributed with Ubuntu and Mint Linux. Sadly, iSSH is no longer being maintained so a fix on that end is unlikely. -- You are receiving this mail because: You are watching the assignee of the bug.

...12 Jan 2014 08:13:13 -0000 1.15 +++ kexgexc.c 25 Jan 2014 10:04:23 -0000 @@ -55,7 +55,7 @@ kexgex_client(Kex *kex) int min, max, nbits; DH *dh; - nbits = dh_estimate(kex->we_need * 8); + nbits = dh_estimate(kex->dh_need * 8); if (datafellows & SSH_OLD_DHGEX) { /* Old GEX request */ -- You are receiving this mail because: You are watching the assignee of the bug.