Similar to my question about RC4, are there any issues with version 2.5.5.0 of the eSELECTplus_dotNet_API.dll in regards to the removal of support of TLS 1.0 from the Moneris portals?
I see that a version 4.4 of the Dll is newly available from a GitHub repository. I haven't had the chance to play with it, but the "4" in the version number makes me nervous.
I have a dependency on .Net Framework 2.0, so I am hoping that if version 2.5.5.0 (of the .Net Framework 1.1 days) has a TLS 1.0 problem, that the version 4.4 Dll is at least still compatible with .Net Framework 2.0.
I would appreciate if someone could address these concerns, as I won't be able to determine whether I have a TLS 1.0 problem (by trial and error that is) myself until Feb 1, 2017.
In reply to ME_Moneris:
In reply to jonny:
In reply to IanThomas:
In reply to WaiverWireAddict:
Did you try manually setting the security protocols instead of using the constants, as such: ServicePointManager.SecurityProtocol = (SecurityProtocolType)3072; ---------------------------------------------------------
This is the definition of the Securityprotocoltype enum:
[System.Flags] public enum SecurityProtocolType { Ssl3 = 48, Tls = 192, Tls11 = 768, Tls12 = 3072, }
Could anyone point me to where I can find version 4.4 you mentioned? I see only version 2.5.6 on GitHub, which is the one I am currently using in production. Does it solve the issue with TLS 1.2, or is that forced default still required?
In reply to Herman: