Xolphin News RSS

Browsers alter the display and notifications for SSL certificates

15 August 2019

A lot is happening with regard to the display of HTTP and HTTPS by the different browsers. They are working on improving the recognisability of secure websites and the strive to HTTPS by default for some time now. Warnings for HTTP become more serious From version 70, the widely used web browser Mozilla Firefox will mark all webpages without HTTPS ...

Read more

Resign Java code by expired Sectigo timestamping certificate

22 May 2019

The Sectigo timestamping certificate expires on July 9, 2019, and has been replaced. After this date Java-code signed with this certificate will cause warnings. These warnings can be resolved by signing and timestamping the code again. What are the consequences? The expiry of the timestamping certificate only has consequences for Java-code signed before March 4, 2019. This may ...

Read more

Expected increase of HTTPS in 2018 realized

22 January 2019

Many developments have happened in the international SSL market as well as at Xolphin. 2018 was a turning point for the use of SSL: for the first time ever, there are more secure websites than insecure websites. Early last year, a large increase of HTTPS use was expected, leading to secure connections being the new standard. One year later, this ...

Read more

Comodo CA continues as Sectigo

31 October 2018

From November 1st, Comodo CA is called Sectigo. This applies to the company name, but also to all brand- and productnames. To ensure a smooth transition, the coming year 'Sectigo, formerly known as Comodo CA', will be used. Why this change? Last year Comodo's certificate division was acquired by Fransisco partners. Since then, the certificate division is called Comodo ...

Read more

End support for TLS 1.0 and TLS 1.1

19 October 2018

Apple, Microsoft and Google announced they will cease support of the encryption protocols TLS 1.0 and 1.1 from early 2020.  Because the use of these protocols for setting up a secure connection is minimal, the impact will probably be low. What will change exactly? From early 2020 the internet protocols TLS 1.0 and 1.1 won’t ...

Read more

Final exchange deadline Symantec, Thawte and GeoTrust certificates approaches fast

25 September 2018

As previously communicated, the browsers slowly cease their trust in Symantec SSL certificates. For all Symantec, Thawte and GeoTrust certificates issued before 1 December 2017, the final exchange deadline of 23 October is now approaching fast. You can renew your certificates free of charge so that they remain trusted by the browsers. What's the planning? Google Chrome ceases trust ...

Read more

Chrome now warns for all unsecured websites

16 August 2018

The popular Google Chrome browser version 68 was released at the end of July. From this version, all websites without an HTTPS connection show an 'unsafe' message informing visitors that the connection is not secure - a change that can have a lot of impact when we look at the current situation.   Warning becomes more serious This change is a turning ...

Read more

Chrome removes secure notification

6 June 2018

From early 2017 Chrome shows a green ‘Secure’ notification for all websites that have an HTTPS connection. They recently announced that this notification will not be shown anymore as of September this year. By then, only EV certificates will show a positive indicator. Research from the Dutch news organisation NOS shows that the current notifications cause confusion and that malicious ...

Read more

Changes caused by new European privacy law

17 May 2018

On May 25th, 2018 the new European privacy law takes effect,  called the General Data Protection Regulation (GDPR). Exactly what will change for you as a customer, and in terms of SSL? Why this new law? A lot has been written about it: the GDPR, which replaces the seperate national Data Protection laws from all European member states based on ...

Read more

Vulnerability found in email encryption technique

14 May 2018

Researchers have found a vulnerability in the most common techniques for email encryption: PGP and S/MIME. This announcement was published under the name EFAIL. You can continue to use S/MIME for encrypted email, but it is advisable to adjust a number of settings in your email software and to update as soon as possible. What does the vulnerability ...

Read more

point up