1
00:00:01,970 --> 00:00:08,060
Starting from the Windows 7 version at Lucker allows encryption not only of the basic in the system

2
00:00:08,060 --> 00:00:12,240
disks but also of us b disks.

3
00:00:12,410 --> 00:00:14,930
The solution is also called Bit locker to go

4
00:00:20,350 --> 00:00:26,940
the general mechanism is exactly the same but does not require the TPM module.

5
00:00:27,180 --> 00:00:33,940
In this case the TPM module is optional we can encrypt USP disks and the key there was encrypted will

6
00:00:33,940 --> 00:00:37,490
be protected by a password and not stored in the TPM module.

7
00:00:38,830 --> 00:00:40,940
The solution is relatively efficient.

8
00:00:45,010 --> 00:00:49,880
We can encrypt a flash drive with a few gigabytes in about half an hour.

9
00:00:49,920 --> 00:00:52,370
It takes about the same amount of time to decrypt it.

10
00:00:53,320 --> 00:00:59,020
The use of such a flash drive means the reduction in efficiency of about 5 percent such as we mentioned

11
00:00:59,050 --> 00:01:05,540
earlier the initial encryption of the entire area is quite time consuming but it can be cancelled at

12
00:01:05,540 --> 00:01:06,530
any time.

13
00:01:09,840 --> 00:01:16,620
Interestingly we can connect the flash drive encrypted in this way to earlier versions of Windows a

14
00:01:16,650 --> 00:01:22,260
program code will be written on the flash drive allowing its decryption hence the name bit locker to

15
00:01:22,260 --> 00:01:29,210
go detached program permits routing encrypted data but does not allow modification

16
00:01:31,860 --> 00:01:36,270
such a flash drive only becomes a carrier for reading all computers with the exception of those with

17
00:01:36,270 --> 00:01:38,180
the relevant addition of Windows 7

18
00:01:46,560 --> 00:01:47,730
in conclusion.

19
00:01:47,790 --> 00:01:51,540
We compare bit locker to true crypt.

20
00:01:51,580 --> 00:01:54,230
These are solutions with similar functionality.

21
00:01:55,900 --> 00:02:02,750
Both systems allow encryption of entire disks this functionality is based on the fact that operating

22
00:02:02,750 --> 00:02:06,940
systems are not linked directly to a disk.

23
00:02:06,990 --> 00:02:12,210
We have a hierarchical structure of layers and between these layers we can place additional programs

24
00:02:12,540 --> 00:02:17,190
such as drive encryption programs.

25
00:02:17,220 --> 00:02:24,790
This may be a layer between the physical disk and a partition or between a partition and a folder bit

26
00:02:24,830 --> 00:02:27,520
locker as an original solution of Microsoft.

27
00:02:27,650 --> 00:02:36,720
And sure it comes from your crypt foundation but lager is a little newer but it's commercial.

28
00:02:36,810 --> 00:02:43,810
It's available only on selected versions of Windows Vista and later it does not allow hiding disks.

29
00:02:43,820 --> 00:02:51,680
It does however allow authenticating the user by using a password key TPM module or any of their combinations.

30
00:02:53,580 --> 00:03:00,780
In your script we only have a password or a key for the same reason but Lucker support is checking the

31
00:03:00,780 --> 00:03:07,490
integrity of the computer and true crypt is not Lucker also allows for the generation of extra keys

32
00:03:07,490 --> 00:03:09,070
for administrative reasons.

33
00:03:11,320 --> 00:03:17,040
Neither of the two programs enable hardware based encryption only true crypto allows the encryption

34
00:03:17,040 --> 00:03:25,310
of a physical disk in the lower layer blogger encrypts all partitions but not all of the physical disks

35
00:03:27,500 --> 00:03:34,030
partitions can also be encrypted with true crypt encryption of virtual disks is characteristic of true

36
00:03:34,060 --> 00:03:38,920
crypt as far as algorithms are concerned.

37
00:03:39,000 --> 00:03:47,450
In the case of bit locker ABS has been chosen for us in the case of true crypt we can also choose the

38
00:03:47,450 --> 00:03:48,800
algorithm ourself.

39
00:03:50,360 --> 00:03:59,510
I'd recommend a yes an interesting thing is that we can encrypt the disk using several algorithms we

40
00:03:59,510 --> 00:04:07,870
can encrypt data again a second time in regards to moding encryption Locher we have CBC as well as in

41
00:04:07,870 --> 00:04:08,780
true crypt.

42
00:04:09,130 --> 00:04:11,200
And I recommend selecting CBC

43
00:04:13,790 --> 00:04:21,300
elephants as an original solution and bit locker to check the authenticity by diffusing bits circlip

44
00:04:21,410 --> 00:04:27,080
partly verify the authenticity by such that a change in one bit of plain text causes a change of more

45
00:04:27,080 --> 00:04:32,730
than one bit and the ciphertext knowing how it Lucker works.

46
00:04:32,740 --> 00:04:38,290
Let's consider what we should not do so that after disk encryption the data saved on the disk could

47
00:04:38,290 --> 00:04:39,460
actually be a secure.