Two Loon Software & Web Development
  541.708.1488
The Issue at Hand

On June 30th, PayPal will stop supporting TLS 1.0 and 1.1 and start requiring TLS 1.2+ for all connections to their servers. Authorize.net do the same on September 18th.

Unfortunately .Net versions prior to 4.5 do not support the newly required security features. This means that AspDotNetStorefront versions prior to 9.5 (which run on .Net 3.5) are going to need to do something to continue using PayPal, Authorize.net, and any other secure payment processor in the industry.

The Solution

AspDotNetStorefront is not offering a patch; Upgrading is the only official solution. However, modifying 9.x versions of AspDotNetStorefront so that they run on .Net 4.5 and support the required security features is relatively easy.

If you have invested heavily into customizing your platform and upgrading is not an option, please contact us to talk about how we can help support your legacy version of AspDotNetStorefront.

Legacy Support for AspDotNetStorefront

Custom software platforms should provide legacy support.
In lieu of official support, we are here to help.

Our Philosophy

AspDotNetStorefront is an open source development platform designed for heavy customization. "Staying on the upgrade path" is extremely limiting and simply not the best option for vendors who need heavy customization.

Our primary goal is to give you confidence in the reliability and maintainability of the customizations that you invest in.

We will do everything in our power to minimize the cost to upgrade and maintain your eCommerce software.

Contact us if you'd like to chat about your project.

TLS 1.2 Misconceptions

Client/Server vs. Server/Processor

There are two communications that need to be secured with TLS 1.2: (1) the connection from the browser to your server and (2) the connection from your server to the payment processor. Your SSL certificate should take care of #1, but the TLS issue described on this page refers to #2 and is still relevant for your website.

pre-9.5 cannot be efficiently patched

This simply is not true. The patch cannot be easily packaged and is highly project specific, but most projects can be patched for TLS compliance relatively quickly.

logo

Welcome to Two Loon Software

Sorry, our website doesn't support your web-browser.
Maybe something more modern would do the trick.

download chrome