Q: What is TLS 1.2?
A: TLS stands for "Transport Security Layer" and is how programs communicate over the internet. TLS 1.2 is the latest version of the protocol
Q: Why so much buzz around TLS 1.2 lately?
A: This is because there have been some high-profile vulnerabilities in the older version of TLS and its predecessor SSL. For that reason, various companies are changing their systems to only support TLS 1.2 and higher.
Q: So what is affected?
A: As there is no clear cut-off date on when companies are switching to TLS 1.2 so you need to check with any 3rd party supplier you use in email, payment gateway, bank, etc., but there is a list of companies that have already changed to TLS 1.2:
- Gateways for B1iPayment already require TLS 1.2 and have done so since at least 2017.
- Bank of Australia Exchange Rates switched as of 28th of August 2018 - More info
- (Other exchange rate providers have not publically announced dates)
- Microsoft Office 365 will only accept TLS 1.2 as of 31st of October 2018 - More info
- B1 Mailchimp had planned to go TLS 1.2 only as of June 2018 but have decided against it (seems the new date is 2020)
- SMTP Providers: Please ask your SMTP Provider
- European Central Bank switched to TLS1.2 as of 27th of September 2022.
Q: What do I need to do to be compatible when my provider switch to TLS 1.2?
A: Depends on the product:
- B1 Usability Package: Version 2018.08 and higher support TLS 1.2
- CRM for Outlook: Version 1.0.85 and higher support TLS 1.2
- B1 iPayment: Version 2017.06 and higher support TLS 1.2
Q: I'm on an older version than the above version and use a service that requires TLS 1.2 (or will soon switch) and I can't upgrade!
A: There is a registry "hack" that can be applied to the .NET Framework. It is not something we can guarantee work in all situations but you can try it out. Read how to apply it here
On older Windows Server Versions you also need to follow this guide to activate on OS Level: https://support.microsoft.com/en-us/help/3140245/update-to-enable-tls-1-1-and-tls-1-2-as-default-secure-protocols-in-wi