WEBVTT - This file was automatically generated by VIMEO

0
00:00:05.600 --> 00:00:08.200
Hello everyone in this video. We are

1
00:00:08.200 --> 00:00:12.100
 going to see how you can fake the TTL values

2
00:00:11.100 --> 00:00:13.300
 of your scan.

3
00:00:14.100 --> 00:00:17.200
So what is TTL TTL stands for time to

4
00:00:17.200 --> 00:00:20.400
 live? It is the round trip train, which are

5
00:00:20.400 --> 00:00:23.300
 request takes to reach to the Target server and

6
00:00:23.300 --> 00:00:25.500
 come back with the response. So

7
00:00:26.400 --> 00:00:30.300
The syntax of doing this particular scan is nmap. Target

8
00:00:29.300 --> 00:00:32.100
 IP address followed by the

9
00:00:32.100 --> 00:00:37.100
 TTL value by hyphen hyphen TTL 128. Remember

10
00:00:36.100 --> 00:00:39.700
 to some of the operating system. The

11
00:00:39.700 --> 00:00:42.300
 TTL values are fixed. For example,

12
00:00:42.300 --> 00:00:45.500
 the TTL value of Linux operating system

13
00:00:45.500 --> 00:00:48.700
 as 64. Where is the TTL

14
00:00:48.700 --> 00:00:51.700
 value of a Windows operating system is one

15
00:00:51.700 --> 00:00:52.700
 28

16
00:00:54.100 --> 00:00:57.500
so we can identify in case if we

17
00:00:57.500 --> 00:00:57.500
 are.

18
00:00:58.200 --> 00:01:01.800
Sending any particular request to any Target and

19
00:01:01.800 --> 00:01:05.200
 the TTL that we receive we can identify if

20
00:01:04.200 --> 00:01:07.700
 the target server is running onto

21
00:01:07.700 --> 00:01:10.600
 a Linux operating system or a

22
00:01:10.600 --> 00:01:12.000
 Windows operating system.

23
00:01:13.400 --> 00:01:13.600
so

24
00:01:14.500 --> 00:01:17.600
In this scan. We are going to spoof our

25
00:01:17.600 --> 00:01:20.000
 TTL value and we will

26
00:01:20.300 --> 00:01:24.400
 not let the target server identify that the

27
00:01:23.400 --> 00:01:27.200
 request is coming from a Windows computer or

28
00:01:26.200 --> 00:01:28.400
 a Linux computer.

29
00:01:29.300 --> 00:01:30.800
So you can also.

30
00:01:32.400 --> 00:01:35.700
Use any custom TTL value that you want to

31
00:01:35.700 --> 00:01:37.700
 confuse the target machine as well.

32
00:01:38.700 --> 00:01:42.000
You can add hyphen V to see the output inverse

33
00:01:41.100 --> 00:01:45.000
 mode the example of doing this particular scan

34
00:01:44.100 --> 00:01:46.800
 is being written over here.

35
00:01:49.100 --> 00:01:52.600
So this is the Practical time and let's see how

36
00:01:52.600 --> 00:01:55.700
 you can run this particular scan. Well.

37
00:01:57.300 --> 00:02:00.300
I am onto a Linux machine. So the TTL value

38
00:02:00.300 --> 00:02:03.600
 of my Linux machine would be 64.

39
00:02:04.600 --> 00:02:07.900
So, let me just ping this particular IP.

40
00:02:09.200 --> 00:02:12.300
And when I ping this you can see the TTL value which

41
00:02:12.300 --> 00:02:15.900
 is the time to live is 64, which means this

42
00:02:15.900 --> 00:02:18.400
 particular machine to which I

43
00:02:18.400 --> 00:02:20.900
 have paint is a Linux machine.

44
00:02:23.100 --> 00:02:23.500
alright

45
00:02:25.000 --> 00:02:25.300
now

46
00:02:29.600 --> 00:02:32.100
you can see over here. I'm going to run this

47
00:02:32.100 --> 00:02:35.800
 particular command wherein I'm going to give the TTL

48
00:02:35.800 --> 00:02:37.500
 as 1:28.

49
00:02:40.800 --> 00:02:40.900
so

50
00:02:42.200 --> 00:02:45.900
you can see the output I have scanned the machine already. I'm

51
00:02:45.900 --> 00:02:47.000
 going to run a

52
00:02:47.700 --> 00:02:50.800
Wireshark filter, which is IP dot

53
00:02:50.800 --> 00:02:51.400
 TTL

54
00:02:52.100 --> 00:02:55.900
This particular filter is used to filter the request

55
00:02:55.900 --> 00:02:57.900
 based on the TTL values.

56
00:02:58.400 --> 00:03:02.600
So you can see I have given a TTL value of 128, which

57
00:03:02.600 --> 00:03:05.400
 means generally the request should be

58
00:03:05.400 --> 00:03:07.900
 coming from a Windows based operating system.

59
00:03:09.500 --> 00:03:10.200
Let's verify.

60
00:03:12.200 --> 00:03:15.700
Over here you can see that this particular

61
00:03:15.700 --> 00:03:18.200
 machine has scanned itself and

62
00:03:18.200 --> 00:03:20.700
 the value is 1 28.

63
00:03:21.500 --> 00:03:24.900
As you can see over here, the machine was Linux

64
00:03:24.900 --> 00:03:28.000
 machine, but instead of showing a

65
00:03:27.100 --> 00:03:30.600
 TTL of 64. It is

66
00:03:30.600 --> 00:03:33.900
 showing a TTL of 128 which

67
00:03:33.900 --> 00:03:36.300
 symbolizes the TTL value

68
00:03:36.300 --> 00:03:39.100
 of a Windows operating system. So this is

69
00:03:39.100 --> 00:03:43.600
 the way we have spoofed our TTL to bypass some

70
00:03:43.600 --> 00:03:47.600
 of the machines which basically restrict the

71
00:03:48.500 --> 00:03:50.800
scanners based on the TTL values

72
00:03:51.800 --> 00:03:54.500
Let us go on to this website wherein you

73
00:03:54.500 --> 00:03:57.800
 can read about default device TTL

74
00:03:57.800 --> 00:04:00.800
 values and over here. You can easily

75
00:04:00.800 --> 00:04:04.000
 see that 128 TTL

76
00:04:03.200 --> 00:04:07.200
 value is for Windows based computers

77
00:04:06.200 --> 00:04:07.800
 mostly.

78
00:04:10.200 --> 00:04:11.100
As you can see over here.

79
00:04:12.200 --> 00:04:15.500
128 represent and symbolizes Windows

80
00:04:15.500 --> 00:04:16.300
 computers

81
00:04:17.200 --> 00:04:20.600
what we have scanned from a Linux computer and still we

82
00:04:20.600 --> 00:04:24.300
 choose this TTL value that was 128

83
00:04:23.300 --> 00:04:25.900
 instead of 64.

84
00:04:26.700 --> 00:04:26.800
So

85
00:04:28.200 --> 00:04:31.500
I hope you guys understood how we can fake our

86
00:04:31.500 --> 00:04:34.600
 TTL value while we are scanning any particular

87
00:04:34.600 --> 00:04:36.400
 Target using in map.

88
00:04:36.900 --> 00:04:37.200
Thank you.
