What cipher to offer for win 10 clients?

I am currently running v15.0 but back in October last year I upgraded to v15.1 which caused the Win 10 clients to be unable to connect with a "Policy mismatch" error which apparently was caused by Debian no longer offering the MODP_1024 which is what Windows 10 was requesting.

Untangle support pointed me to the following article which matched what I was seeing in the IPsec logs.
https://jrklein.com/2019/12/02/debia...ws-10-clients/

According to Untangle Support the issue was resolved in v16 with. I have setup a test Untangle and can see that there und IPsec VPN - > VPN Config that there is now the option to manually set the cipher and I can see that this give me the option to change from the default of "14 (modp2048)" to "2 (modp1024)". See attached screenshot.

What I don't know is what are the other values are the other values beyond "DH Key Group" that the Win 10 clients would be requesting such as "Encryption", "Hash" and "Lifetime" so that I can match this request with the manual choices I need to make.

Attachment 10987

Thanks

Windows and Java updates in the UT OS caused MD5 to be no longer accepted since it is not secure anymore. Use SHA-256.

Quote:

---

Originally Posted by jcoffin

MD5 ... is not secure anymore.

---

It hasn't been secure for at least 15 years now, if it even ever was :D

But as we've seen, warnings get ignored and things progress when someone says NO, you shall not be stupid anymore.

Quote:

---

Originally Posted by sky-knight

things progress when someone says NO

---

Speaking of, how's everybody's Flash situation? :D

Quote:

---

Originally Posted by jcoehoorn

Speaking of, how's everybody's Flash situation? :D

---

Flash was removed from all of my supported platforms via powershell script last November. So I suppose I don't care? ;)