1
00:00:00,630 --> 00:00:07,310
In our case, all the three system they're running, they are in, they do not have the GUI.

2
00:00:07,590 --> 00:00:12,150
So this is optional video just for your knowledge purposes.

3
00:00:12,660 --> 00:00:16,950
I have given you the screenshot and we will not be giving the practical demo of that.

4
00:00:17,220 --> 00:00:24,210
So if you have got any GUI client available with you, whether it is Windows system or linux system

5
00:00:24,210 --> 00:00:30,480
in which GUI is running and you have a Web browser, is there, then please give the system some

6
00:00:30,480 --> 00:00:30,880
address.

7
00:00:30,930 --> 00:00:38,910
Like in our case, we are showing that the address of that system is a 172.24.0.31.

8
00:00:39,330 --> 00:00:46,860
Then let's check about the entry in hostile also whether that entry is there 172.24.0.1

9
00:00:47,160 --> 00:00:55,320
www.example.com www, then we will have to make sure that Firefox browser is there.

10
00:00:55,920 --> 00:01:03,090
So we will go to the Firefox browser and there we are going to type https://www.example.com.

11
00:01:03,600 --> 00:01:07,470
Now when you are going to type in this browser, what it is going to show?

12
00:01:07,530 --> 00:01:15,930
This connection is uninterested because it is not able to find the source of that certificate because

13
00:01:15,930 --> 00:01:18,440
in our case it is self-signed certificate.

14
00:01:18,840 --> 00:01:26,840
So what we have to do, it will we have to click on I understand the risk and then we have to add exception.

15
00:01:27,600 --> 00:01:31,350
So we have to confirm the security exception.

16
00:01:32,330 --> 00:01:34,700
Then what will happen?

17
00:01:35,500 --> 00:01:40,700
your Web page will get displayed when you are going to click on this icon.

18
00:01:41,170 --> 00:01:42,030
What will happen?

19
00:01:42,220 --> 00:01:46,960
It will show you various parameters, like a website name.

20
00:01:46,990 --> 00:01:50,300
Is this verified by U-Net solution

21
00:01:50,320 --> 00:01:56,620
And when we are going to click on view certificates, you will find that it is giving you a lot of information,

22
00:01:57,010 --> 00:01:59,390
www.example.com U-Net Solution.

23
00:01:59,680 --> 00:02:04,340
This is the organization Unet when it was issued, when it was valid.

24
00:02:04,720 --> 00:02:10,660
So this is optional just for knowledge purposes that mean if you have got any Graphic client for different

25
00:02:10,930 --> 00:02:12,330
browser, different option.

26
00:02:12,330 --> 00:02:18,940
is there in our case we are not concerned with the client side, our https server is running

27
00:02:18,940 --> 00:02:19,570
properly.

28
00:02:19,990 --> 00:02:26,890
And if you have got any GUI client in our case, I'm just showing you the screenshot.

29
00:02:27,220 --> 00:02:31,570
But in our case, we will limit our lab to master C10 and C20 system.

30
00:02:31,900 --> 00:02:34,430
In your case, any GUI system you can test.

31
00:02:34,960 --> 00:02:41,190
So now in our case, we were able to properly implement your secure http server.

32
00:02:41,590 --> 00:02:45,730
that mean we were able to implement https.

33
00:02:45,730 --> 00:02:46,930
for that we use this lab.

34
00:02:47,240 --> 00:02:52,200
So what we exactly did, we created that, first private key file.

35
00:02:52,210 --> 00:02:54,130
Then we created self-signed certificate.

36
00:02:54,400 --> 00:03:01,660
Then we made entry in ss.conf file and then we restarted the server.

37
00:03:01,690 --> 00:03:10,620
Then we tested it with openSSL s_client then with curl browser also then with elinks also.

38
00:03:10,810 --> 00:03:13,930
So our https is working perfectly.