Chris Severance

2048 is the highest it goes. This is really wierd. With `SFTPDHParamFile` not present you get 1024. With it present and garbage like `SFTPDHParamFile /dev/null` you get 2048. For `SFTPDHParamFile...

gex is garbage. Adjustable is it's downfall. Of course there would be clients that only support the lowest possible value. Having to include the lowest possible value means the rest...

That could work. Also log both the chosen bits and the client range so I know if they support recommended sizes but are intentionally choosing below. There's a problem if...

It's barely worth fooling with adding DH size to SFTPClientMatch. `diffie-hellman-group-exchange-sha256` is a deprecated algorithm anyways and as far as I'm concerned the entire RSA suite needs to be deprecated....

I made a quick patch to show the min max values. ``` JSCH-0.1.50,JSCH-0.1.51 + Session original client DHgex group exchange min 1024, pref 1024, max 1024 + Session effective client...

Unfortunately I get minimal control of the clients, and no control of the Mirth clients using jsch. If it were up to me they'd all be running jsch 0.2.1 and...

A single option is fine. More like `SFTPDHGroupLimits min pref [max]`. Make it clear that it's rare that anyone would want to reduce the max. `SFTP_DH_MIN_LEN` is the server pref,...

What I'd like to do is raise the server minimum and set the preferred across the board. ``` SFTPDHGroupLimits 3072 4096 SFTPDHGroupLimits 3072 ``` Then drop the server min for...

Didn't work for me either. LAN to same LAN connections worked most of the time but Internet connections rarely connected. Got rendezvous, offline, and deadline errors. All working and fast...

After adding more peers and more testing I ended up with a few pairs on different LAN that wouldn't connect. Error is "deadline has elapsed." Seems to be routers specific...