Google’s Chrome Browser To Remove ‘Secure’ HTTPS Indicators

From September, Chrome will gradually eliminate messages showing a site uses HTTPS – while adding stronger warnings for those that aren’t encrypted

Google is set to change the way websites secured with the HTTPS protocol appear to users of its Chrome browser, in the next step of its ongoing campaign to promote the use of encrypted communications on the web.

HTTPS was initially used by the likes of e-commerce or banking sites, typically to protect the security of sensitive data, such as the entry account credentials or payment details, but has recently become more widespread, in part thanks to Google’s efforts to shame sites that don’t use it.

Browsers have been marking HTTPS-secured sites with a green padlock for more than a decade, and last year Chrome began marking sites that handle transactions, but don’t use the protocol, as “Not Secure”.

Safe by default

The next step, Google has said, is to eliminate the “Secure” label from HTTPS sites, since HTTPS should be the norm, the company said.

“Users should expect that the web is safe by default, and they’ll be warned when there’s an issue,” Chrome security product manager Emily Schechter wrote in a blog post.

Version 69 of Chrome, coming in September, will change the way web data entry fields protected with HTTPS are marked, replacing the green padlock and the word “Secure” with a simple grey padlock.

At some point after that, Chrome will eliminate the padlock altogether, Google said.

“Since we’ll soon start marking all HTTP pages as ‘not secure’, we’ll step towards removing Chrome’s positive security indicators so that the default unmarked state is secure,” Schechter wrote.

With Chrome version 70, in October, Chrome will also change the way data-entry fields on non-HTTPS websites are marked.

‘Not secure’

They will be marked as “Not secure” in the address bar, and when a user begins entering information on the page, the warning will turn red, with a red triangle.

The use of HTTPS was initially limited in part due to the complexity of managing the security systems and certificates involved, but Google said the technology is now “cheaper and easier than ever before”.

Security experts, however, have said the spread of HTTPS can lull users into a false sense of security since there’s nothing to stop malicious sites from deploying it.

And while it protects information passed to a web page, it does nothing to ensure websites protect that data once it’s in their possession – a fact that has led to a number of massive security breaches in recent years.

Sources: silicon

ALL SRI LANKANS BLOG

Hey My Readers and Visitirs If You Like Us or Our Web Site Please Share and Link back To My Site ... Take Care .,.,.

<a href="http://sltechnozone.blogspot.com/2018/06/googles-chrome-browser-to-remove-secure.html">Google’s Chrome Browser To Remove ‘Secure’ HTTPS Indicators</a>

HTTP Status Codes

HTTP status codes are standard response codes given by web site servers on the Internet.

The codes help identify the cause of the problem when a web page or other resource does not load properly.

The term HTTP status code is actually the common term for the HTTP status line that includes both the HTTP status code and the HTTP reason phrase.

HTTP status codes are sometimes called browser error codes or internet error codes.

For example, the HTTP status line 500: Internal Server Error is made up of the HTTP status code of 500 and the HTTP reason phrase of Internal Server Error.

Two major groups of HTTP status code errors exist:

4xx Client Error

This group of HTTP status codes includes those where the request for a web page or other resource contains bad syntax or cannot be filled for some other reason, presumably by the fault of the client (the web surfer).

Some common client error HTTP status codes include 404 (Not Found), 403 (Forbidden), and 400 (Bad Request).

5xx Server Error

This group of HTTP status codes includes those where the request for a web page or other resource is understood by the website's server but is incapable of filling it for some reason.

Some common server error HTTP status codes include the ever popular 500 (Internal Server Error), along with 503 (Service Unavailable) and 502 (Bad Gateway).

Other HTTP status codes exist in addition to 4xx and 5xx codes. There are also 1xx, 2xx, and 3xx codes that are informational, confirm success or dictate a redirection, respectively. These additional types of HTTP status codes aren't errors so you shouldn't be alerted about them in the browser.

Important: An HTTP status code is not the same as a Device Manager error code or a system error code.

Some system error codes share code numbers with HTTP status codes but they are different errors with completely different associated error messages and meanings.

Sources: lifewire

ALL SRI LANKANS BLOG

Hey My Readers and Visitirs If You Like Us or Our Web Site Please Share and Link back To My Site ... Take Care .,.,.

<a href="http://sltechnozone.blogspot.com/2017/07/http-status-codes.html">HTTP Status Codes</a>

How to Install SSL Certificate on Your VPS or Dedicated Server

We may sound a bit speculative here, but before we put you to the steps on how to install SSL certificate on your VPS or your dedicated server, it is important for you to know an overview of VPS or Dedicated server and a brief understanding on SSL certificate. So let’s read:

A virtual private server is also called as VPS – It is technically a virtual machine that is sold as a service by the Internet hosting service providers to businesses, software developers, and other computing industries. A VPS operates its own copy of operating system due to this its customers may experience a superuser-level access to that existing operating system. To gain better understanding let’s take an example – The users of VPS get a high level of access to the operating systems, because of this they can even install almost any software that runs on the current or any other operating system.

By definition virtual private servers, VPS are altogether different from its dedicated servers. This is because instead of running/operating on one hosting account on only one computer or server, the virtual private servers share a single server. Now, we know you might be in the dilemma that, what is the difference between a virtual private server solution and a shared web host? Let’s have a look: Virtual Private Server (VPS) Hosting basically is similar to living in a simplex or half-plex where you can tailor-made all your needs as per your tastes and budget. It is usually utilized for shared hosting and is also the most common method used for hosting the websites. Moreover, VPS is great for customers as well, because it comes in packages or they can use it on trial basis or there are low-cost hosting packages as well meeting all your needs.

Steps to follow on how to install SSL certificate on Your VPS or Dedicated Server

This article will further take you to some important steps that you must take when you are installing an SSL certificate on your VPS or dedicated server. These steps will also cover the essence of how to install SSL certificate for the hostname via WHM or cPanel. This type of SSL certificate will secure the access to the server services like – webmail, cPanel, FTP, etc. Here please note that at times certain clients require the use of your server’s hostname and which port # to contact or look-up to for these server services with enhanced security.

Another important factor that shall not be missed when installing SSL certificate is that when you are on the verge of installing an SSL certificate via WHM, you will certainly need a ROOT access to the server. So what does this mean? It indicates that only VPS and Dedicated Server clients can efficiently access and install an SSL certificate via their WHM. In case if you share the business hosting package or have a reseller you should contact the sales team of the service provider, they will be certainly helping you out with the installation.

Step 1:

Log on to WHM: The very first step here to set up your SSL certificate is that you need to log in to the WHM on your server or dedicated server. For this knowing your root password for the server is very important. Well, if you don’t know the root password don’t worry, it can taken for the service provider or in case you forgot the password and thinking this is even worse, no worries, set up a new one by asking your service provider to send you a link to reset the password (https://my.BlueHost.com/hosting/help/whm-login#root-password – in case we can keep it as this URL is from the ref you have given).

Step 2:

Next, once you are done with the password and have logged into your account, then you will have to Login to the WHM – this you can do by going to yourdomain.com or WHM in a browser. Then you can replace yourdomain.com with your domain address. Then, of course, you have to enter your username and password on the log-in page. Here your username will be the root.

Also, remember that your password will be the root password for your server. In case you still don’t have a root password then please set-up a new one or check out this URL. https://my.BlueHost.com/hosting/help/whm-login#root-password.

Step 3:

In case you are using the log-in a feature into WHM for the first time then you may see a page titled “Feature Showcase” (In a window). If it does then click on Exit to WHM at the bottom of the page.

Accessing the Install SSL Tool: Here when you logged into the WHM, for the installation of SSL certificate you need the SSL installer to install, upload and activate a certificate on the respective domain. So how to find it: you will find it through the WHM search tool.

• Right in the WHM Search box you will find a “Install an SSL Certificate” on the left side

Now, click on the button “Install an SSL Certificate on a Domain” this is a link that will appear.

• Now it is simple, you will be able to install an SSL Certificate on the Domain page in the WHM.

Step 4:

Just install the SSL certificate

Please remember one important thing, when you have purchased the SSL certificate you should have received some files for your certificate authenticity, or a key or a Certificate Authority bundle. Now, these files are really important, in case you don’t have these files yet please ask your company from which they have you have purchased the certificate from.

• On the page “Install an SSL Certificate on a Domain” you will have to enter your domain your certificate was already issued for and this you will have to enter in the “Domain:” box.

• Here you will have to paste the Certificate, Key and the CA – Certificate Authority Bundle which you received in the appropriate boxes.

• Click on the Install box right at the bottom. You are done with the installation!

Hope these steps will help you to install your SSL certificate on your VPS or dedicated server.

Sources: blogsaays

ALL SRI LANKANS BLOG

Hey My Readers and Visitirs If You Like Us or Our Web Site Please Share and Link back To My Site ... Take Care .,.,.

<a href="http://sltechnozone.blogspot.com/2017/06/how-to-install-ssl-certificate-on-your.html">How to Install SSL Certificate on Your VPS or Dedicated Server</a>