The SSL4Less.mx brand has been merged with cyber_Folks. Login to services: cyberfolks.pl.
For more information see.
Secure Hash Algorithm (SHA) is a signing algorithm used for identity validation during the SSL process. SHA calculates a persistent and unique value (so called "hash") each time during use. Thanks to this hash function if any part of the string is changed the signature will fail to verify and the message will not be authenticated.
SHA-1 is slowly being phased out because there is a chance it will no longer be able to perform accurate identification due to its vulnerability of "collisions". "Collisions" take place when two different strings produce the same hash value; the result is a "forged" certificate which allows the client's browser to falsely verify a server's identity.
Due to the weaknesses of SHA-1 caused by its short hash length (160-bit), the National Institute of Standards and Technology (NIST) and the National Security Agency (NSA) developed SHA-2 as its successor. SHA-2 has four variants: SHA-224, SHA-256, SHA-384, and SHA-512 (The previous SHA-names according to the number of output bits).
Some major developers including Microsoft have planned full SHA-2 implantation in 2017. Google however has taken steps to do this much sooner.
On 26 September 2014
Sites with end-entity ("leaf") certificates that expire on or after 1/1/17 and which include a SHA-1-based signature as part of the certificate chain, will be treated as "secure, but with minor errors".
On 7 November 2014
Sites with end-entity certificates that expire between 6/1/16 to 12/31/16 (inclusive), and which include a SHA-1-based signature as part of the certificate chain, will be treated as "secure, but with minor errors".
Sites with end-entity certificates that expire on or after 1/1/17, and which include a SHA-1-based signature as part of the certificate chain, will be treated as "neutral, lacking security".
In Q1 2015
Stron z certyfikatem wygasającym pomiędzy 1 stycznia 2016 a 31 grudnia 2016 (włącznie) i zawierające podpis oparty o SHA-1 jako cześć łańcucha, będą traktowane jako „bezpieczne z mniejszymi błędami”.
Sites with end-entity certificates that expire on or after 1/1/17, and which include a SHA-1-based signature as part of the certificate chain, will be treated as "affirmatively insecure". Sub-resources from such a domain will be treated as "active mixed content".
Note:
SHA-1-based signatures for trusted root certificates are not a problem because TLS clients trust them by their identity, rather than by the signature of their hash.
If your SSL certificate meets one of these points:
To prevent future inconveniences users whose SSL certificates are using SHA-1 should contact SSLGURU for more information and guidance through the reissuance process. Certificate reissuance is a simple and effective way to fix the affected SSL certificate(s). Remember when you reissue your certificate you should also update the intermediates certificates to the new SHA-2 versions as well.
SSLGURU will be taking all necessary steps to identify the SSL certificates that are using SHA-1 and inform their users on how to avoid the consequences of SHA-1 sunsetting.
On the Chrome project official blog Google announced it will start the process of sunsetting SHA-1 in November 2014. After this point HTTPS sites whose certificate chains use SHA-1 and are valid past 1 January 2017 will no longer appear to be fully trustworthy in Chrome's user interface.
It’s a good time for a change.
Now you can get SSL certificate from DigiCert. Keep the validity period and the level of validation.
Get the 5-star quality!
cyber_Folks S.A. – Cookie settings
Do you like good cookies? We too! Some cookies are required for the website to function properly. Also accept additional cookies related to service performance, social networking and marketing. Cookies are also used to personalize ads. Thanks to them, you will get the best experience of our website, which we are constantly improving. The consent granted voluntarily may be withdrawn or modified at any time. More information about the cookies used can be found in our privacy policy. If you prefer to specify your preferences precisely - see the types of cookies below.