In our case, all the three system they're running, they are in, they do not have the GUI.
So this is optional video just for your knowledge purposes.
I have given you the screenshot and we will not be giving the practical demo of that.
So if you have got any GUI client available with you, whether it is Windows system or linux system
in which GUI is running and you have a Web browser, is there, then please give the system some
address.
Like in our case, we are showing that the address of that system is a 172.24.0.31.
Then let's check about the entry in hostile also whether that entry is there 172.24.0.1
www.example.com www, then we will have to make sure that Firefox browser is there.
So we will go to the Firefox browser and there we are going to type https://www.example.com.
Now when you are going to type in this browser, what it is going to show?
This connection is uninterested because it is not able to find the source of that certificate because
in our case it is self-signed certificate.
So what we have to do, it will we have to click on I understand the risk and then we have to add exception.
So we have to confirm the security exception.
Then what will happen?
your Web page will get displayed when you are going to click on this icon.
What will happen?
It will show you various parameters, like a website name.
Is this verified by U-Net solution
And when we are going to click on view certificates, you will find that it is giving you a lot of information,
www.example.com U-Net Solution.
This is the organization Unet when it was issued, when it was valid.
So this is optional just for knowledge purposes that mean if you have got any Graphic client for different
browser, different option.
is there in our case we are not concerned with the client side, our https server is running
properly.
And if you have got any GUI client in our case, I'm just showing you the screenshot.
But in our case, we will limit our lab to master C10 and C20 system.
In your case, any GUI system you can test.
So now in our case, we were able to properly implement your secure http server.
that mean we were able to implement https.
for that we use this lab.
So what we exactly did, we created that, first private key file.
Then we created self-signed certificate.
Then we made entry in ss.conf file and then we restarted the server.
Then we tested it with openSSL s_client then with curl browser also then with elinks also.
So our https is working perfectly.