Hi-
In my classic ASP application, submission to A.net seemed to grind to halt when they "retired" 3DES. Some on this forum apparently fixed the problem by disabling 3DES. I tried that approach but when I did that, I couldn't access any SSL pages on my site.
Thoughts on this?
Thanks
Dave
09-30-2017 10:23 AM
What version of Windows are you running? How did you disable 3DES?
For 2003 - 2008, check out the post at: https://community.developer.authorize.net/t5/Integration-and-Testing/Underlying-connection-was-close...
09-30-2017 12:02 PM
@NexusSoftware wrote:What version of Windows are you running? How did you disable 3DES?
It's Server 2003 R2.
I used IISCrypto, the utility from Nartac software. Figured it was marginally safer than a direct edit of the Registry. I have heard that others have had success with it.
Thoughts?
10-01-2017 08:59 AM
IISCrypto can work pretty well. Do you have a live URL to check out?
There is a lack of support for the SHA2 family of hash algorithms on Windows Server 2003. A potential fix is: https://support.microsoft.com/en-us/help/938397/applications-that-use-the-cryptography-api-cannot-va...
10-01-2017 09:19 AM - edited 10-01-2017 09:31 AM
@NexusSoftware wrote:IISCrypto can work pretty well. Do you have a live URL to check out?
You mean an SSL page on our site for scanning purposes? Can I PM you?
Again, keep in mind that we never had an issue with A.net until thie 3DES retirement thing,
10-02-2017 07:00 AM
Yes, an SSL page on your site. Not necessarlity for scanning but to inspect and see what might be causing the issue. Yes, you can PM the URL.
10-02-2017 07:05 AM
I'm sorry -I feel dumb but I have looked at menus all over this forum and don't see how to send a PM
10-03-2017 04:39 PM
If you click on a user's profile, there is a link "Send this user a private message".
10-03-2017 04:43 PM - edited 10-03-2017 04:43 PM