WEBVTT - This file was automatically generated by VIMEO

1
00:00:14.200 --> 00:00:16.100
 Hello everyone. Welcome back.

2
00:00:17.600 --> 00:00:20.600
 Since this entire course is dedicated session, hijacking. Let's

3
00:00:20.600 --> 00:00:23.800
 try to understand what is a session also

4
00:00:23.800 --> 00:00:26.300
 will try to understand how our sessions being

5
00:00:26.300 --> 00:00:30.600
 implemented on both web. And network will

6
00:00:30.600 --> 00:00:33.100
 just go to the basics for now. And the

7
00:00:33.100 --> 00:00:36.700
 next module will take a deep dive on various implementation mechanisms.

8
00:00:36.800 --> 00:00:39.600
 So what's called the session session

9
00:00:39.600 --> 00:00:42.900
 is nothing. But the connectivity that is being established between

10
00:00:42.900 --> 00:00:44.100
 a client and a server.

11
00:00:45.400 --> 00:00:48.000
 All the devices over the network has to set up a

12
00:00:48.100 --> 00:00:51.200
 communication in which each of those is going to send

13
00:00:51.200 --> 00:00:54.400
 a request and the server is going to respond back

14
00:00:54.400 --> 00:00:57.700
 with an appropriate response. So,

15
00:00:57.700 --> 00:01:00.700
 each session is going to be identified

16
00:01:00.700 --> 00:01:03.900
 with a unique value known as session ID. So

17
00:01:03.900 --> 00:01:06.200
 these such an IDs are generally, a

18
00:01:06.200 --> 00:01:09.200
 numeric or alphanumeric value based on the implementation from

19
00:01:09.200 --> 00:01:10.100
 the development side.

20
00:01:11.200 --> 00:01:15.400
 So, these each session ID will be uniquely mapped with

21
00:01:15.400 --> 00:01:18.200
 a user in order to identify who is sending the

22
00:01:18.200 --> 00:01:18.800
 request.

23
00:01:20.300 --> 00:01:24.200
 Now, let's take a look at the web based implementation. So

24
00:01:24.200 --> 00:01:27.600
 over the web, the default protocol that would be used is http.

25
00:01:29.400 --> 00:01:33.000
 So HTTP protocol is bad, fall stateless. So

26
00:01:32.100 --> 00:01:35.100
 what does that mean? So ideally the

27
00:01:35.100 --> 00:01:39.000
 web server cannot store the information to

28
00:01:38.400 --> 00:01:42.200
 uniquely identify the client. Since

29
00:01:41.200 --> 00:01:44.600
 each of this request is being understood

30
00:01:44.600 --> 00:01:48.300
 on isolation or one-to-one basis. So

31
00:01:48.300 --> 00:01:50.400
 now let's take try to understand the scenario.

32
00:01:52.400 --> 00:01:55.200
 So the internet, let's assume a case where there's

33
00:01:55.200 --> 00:01:56.800
 an EB, c.com web server.

34
00:01:58.200 --> 00:02:01.200
 So once a user a is trying to send

35
00:02:01.200 --> 00:02:04.200
 a request, he will send out is one

36
00:02:04.200 --> 00:02:06.500
 session ID once he's been authenticated.

37
00:02:07.600 --> 00:02:10.500
 Or with a thought in authentication as well. This

38
00:02:10.500 --> 00:02:13.300
 is done in order for the web server to

39
00:02:13.300 --> 00:02:16.600
 uniquely identify each user since

40
00:02:16.700 --> 00:02:19.600
 over a period of time. We may have multiple users

41
00:02:19.700 --> 00:02:22.200
 sending out multiple requests. So

42
00:02:22.200 --> 00:02:25.300
 the prediction are you? We can see that both the users a and

43
00:02:25.300 --> 00:02:28.100
 user be have a unique session ID. So this

44
00:02:28.100 --> 00:02:32.000
 is how Servo is going to respond back to each user

45
00:02:31.300 --> 00:02:34.100
 based on the requests that they

46
00:02:34.100 --> 00:02:34.900
 send it out.

47
00:02:35.800 --> 00:02:38.400
 Along with those, she protocol also sends

48
00:02:38.400 --> 00:02:41.200
 out multiple headers. So in this

49
00:02:41.200 --> 00:02:44.400
 scenario, we can see the type of request. The user agent

50
00:02:44.400 --> 00:02:48.000
 is nothing, but a browser that is being used to send out the request. What

51
00:02:47.100 --> 00:02:50.000
 is a domain name? And what are

52
00:02:50.100 --> 00:02:53.900
 the data types or what are the separate inquiry mechanisms?

53
00:02:55.200 --> 00:02:58.100
 Now similarly, let's try to take an overview about the

54
00:02:58.100 --> 00:03:01.100
 network protocol. So in this particular scenario, let's try to

55
00:03:01.100 --> 00:03:05.100
 understand how TCP works. So unlike HTTP TCP

56
00:03:04.100 --> 00:03:07.400
 is a connection-oriented protocol also

57
00:03:07.400 --> 00:03:10.600
 known as a true connection. So that means it is going to

58
00:03:10.700 --> 00:03:13.200
 maintain the information about the session till the time. It

59
00:03:13.200 --> 00:03:16.200
 is active TCP. Protocol is also known

60
00:03:16.200 --> 00:03:20.200
 as three-way handshake protocol, which is also known as syn synack

61
00:03:19.200 --> 00:03:22.600
 and ack. The first step. The

62
00:03:22.600 --> 00:03:24.700
 client is going to send out a syn packet.

63
00:03:25.200 --> 00:03:28.800
 Informing the servo to initiate a session in

64
00:03:28.800 --> 00:03:31.700
 the response. The particular server

65
00:03:31.800 --> 00:03:35.500
 is going to take the syn packet from the client increment,

66
00:03:34.800 --> 00:03:37.200
 with a value of 1 and

67
00:03:37.200 --> 00:03:40.400
 set, an acknowledgment packet with another random value. So,

68
00:03:40.400 --> 00:03:43.500
 in that way, the client, once it receives it,

69
00:03:43.100 --> 00:03:46.500
 once it calculates, the increment value

70
00:03:46.500 --> 00:03:49.300
 of 1 for the same, it does understand the server

71
00:03:49.300 --> 00:03:52.100
 as receptors request, and it has also sent out

72
00:03:52.100 --> 00:03:53.100
 an acknowledgement packet.

73
00:03:53.800 --> 00:03:56.200
 So in the final step, the client is going to

74
00:03:56.200 --> 00:03:59.400
 send back the college packet, incriminate the value of one and

75
00:03:59.400 --> 00:04:02.500
 sent back to the server. So in that way, both

76
00:04:02.500 --> 00:04:05.300
 client and server, both know that

77
00:04:05.300 --> 00:04:08.200
 both have accepted the request and have sent the response and the connection has been

78
00:04:08.200 --> 00:04:08.800
 established.

79
00:04:10.100 --> 00:04:13.700
 So in this particular section, we have looked at both stateless session

80
00:04:13.100 --> 00:04:17.300
 in which three cosas process in isolation and

81
00:04:16.300 --> 00:04:19.300
 the stateful session in terms

82
00:04:19.300 --> 00:04:22.300
 of TCP where each and every request is being tracked and

83
00:04:22.300 --> 00:04:24.100
 maintained until the session is acted.

84
00:04:25.600 --> 00:04:27.300
 That is what this video. Thank you.
