LexiConn – June 2018 Newsletter

Forum Forums Newsletters LexiConn – June 2018 Newsletter

This topic contains 0 replies, has 1 voice, and was last updated by  lexiconn 5 years, 8 months ago.

Viewing 1 post (of 1 total)
  • Author
    Posts
  • #49455

    lexiconn
    Keymaster

    *********************************************************************
    JUNE 2018 NEWSLETTER
    *********************************************************************

    In this Month’s Newsletter…

    * Upcoming TLS 1.0 Deadline
    * Featured Client: theforeverrose.com
    * From the Blog…

    Upcoming TLS 1.0 Deadline
    —–
    The payment card industry (PCI) council has set a deadline of June 30, 2018 to no longer have support for TLS 1.0.

    TLS stands for Transport Layer Security and it is a security protocol that allows connections to be encrypted and secure. TLS 1.0 has been deemed an insecure version of this protocol. The PCI council is requiring that websites disable TLS 1.0 by June 30 in order to be PCI compliant.

    TLS 1.0 was first released back in 1999. Many vulnerabilities have since been discovered in this very old protocol, including man-in-the-middle attacks. Due to these discoveries, the PCI council has determined that TLS 1.0 should no longer be supported on any system that handles sensitive data, such as credit card details.

    If you choose to disable TLS 1.0 for your website, people using older computers / browsers would no longer be able to access secure pages on your site. This includes Internet Explorer v10 and earlier, Google Chrome v29 or lower, Firefox v27 or lower, as well as Safari 6, Android v4.4, iOS 4, and their earlier versions. This would most likely impact a small portion of your users (likely less than 1%). If you run Google Analytics you can view the Browser & OS report on the Audience –> Technology screen to see what your customers use for their browsers.

    Many third party providers such as Authorize.net and UPS have already abandoned support for TLS 1.0 and are requiring that connections are made via TLS 1.2. All of our servers support TLS 1.2 natively, and as long as the software you are using on your site is TLS 1.2 compatible, no action is required. If you are running older software, you may need to upgrade in order to support TLS 1.2. Note that the PayPal deadline for TLS 1.2 is right around the corner on June 30:

    https://www.paypal.com/stories/us/paypal-merchants-less-than-30-days-to-upgrade-to-tls-12

    TLS 1.0 will not be disabled by default on any LexiConn hosted account. Rather, if you would like TLS 1.0 disabled, just drop us an email (support@lexiconn.com) and we’ll do so.

    Featured Client: theforeverrose.com
    —–
    This month’s featured client is theforeverrose.com. The Forever Rose is the world’s leading manufacturer and supplier of preserved real roses.

    https://www.theforeverrose.com/

    For more detailed information on this month’s featured client as well as a listing of all past featured clients, please go to:

    http://support.lexiconn.com/news/forums/forum/featured-clients/

    From the Blog…
    —–
    Here are some recent posts from The LexiConn Blog:

    MySQL and Magento – Proper Sizing is Important – A quick look at how MySQL can be optimized to improve performance.

    https://www.lexiconn.com/blog/2018/06/mysql-and-magento-proper-sizing-is-important/

    ShopSite Version 14 – Lots of Great New Features – A must have upgrade, containing a number of new features.

    https://www.lexiconn.com/blog/2018/03/shopsite-version-14-lots-of-great-new-features/

    Like what you’re reading? Subscribe by Email to our blog and receive an email when a new post is published.

    As always, feel free to contact us with any questions you may have. Complete contact and support options can be found at:

    https://support.lexiconn.com/

    Sincerely,

    - The LexiConn Team

    If you have a moment, please let us know how we’re doing!

    https://www.shopperapproved.com/surveys/full.php?id=3552

Viewing 1 post (of 1 total)

You must be logged in to reply to this topic.