1 .\" Copyright (c) 2005-2011 Pawel Jakub Dawidek <pawel@dawidek.net>
2 .\" All rights reserved.
4 .\" Redistribution and use in source and binary forms, with or without
5 .\" modification, are permitted provided that the following conditions
7 .\" 1. Redistributions of source code must retain the above copyright
8 .\" notice, this list of conditions and the following disclaimer.
9 .\" 2. Redistributions in binary form must reproduce the above copyright
10 .\" notice, this list of conditions and the following disclaimer in the
11 .\" documentation and/or other materials provided with the distribution.
13 .\" THIS SOFTWARE IS PROVIDED BY THE AUTHORS AND CONTRIBUTORS ``AS IS'' AND
14 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
15 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
16 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHORS OR CONTRIBUTORS BE LIABLE
17 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
18 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
19 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
20 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
21 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
22 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
32 .Nd "control utility for the cryptographic GEOM class"
34 To compile GEOM_ELI into your kernel, add the following lines to your kernel
36 .Bd -ragged -offset indent
38 .Cd "options GEOM_ELI"
41 Alternatively, to load the GEOM_ELI module at boot time, add the following line
44 .Bd -literal -offset indent
56 .Op Fl B Ar backupfile
58 .Op Fl i Ar iterations
59 .Op Fl J Ar newpassfile
60 .Op Fl K Ar newkeyfile
62 .Op Fl s Ar sectorsize
66 .Cm label - an alias for
79 .Cm stop - an alias for
87 .Op Fl s Ar sectorsize
96 .Op Fl i Ar iterations
98 .Op Fl J Ar newpassfile
100 .Op Fl K Ar newkeyfile
159 utility is used to configure encryption on GEOM providers.
161 The following is a list of the most important features:
163 .Bl -bullet -offset indent -compact
167 framework, so when there is crypto hardware available,
169 will make use of it automatically.
171 Supports many cryptographic algorithms (currently
179 Can optionally perform data authentication (integrity verification) utilizing
180 one of the following algorithms:
189 Can create a User Key from up to two, piecewise components: a passphrase
190 entered via prompt or read from one or more passfiles; a keyfile read from
193 Allows encryption of the root partition.
194 The user will be asked for the
195 passphrase before the root file system is mounted.
197 Strengthens the passphrase component of the User Key with:
200 .%T "PKCS #5: Password-Based Cryptography Specification, Version 2.0."
205 Allows the use of two independent User Keys (e.g., a
208 .Qq "company key" ) .
212 performs simple sector-to-sector encryption.
214 Allows the encrypted Master Key to be backed up and restored,
215 so that if a user has to quickly destroy key material,
216 it is possible to get the data back by restoring keys from
219 Providers can be configured to automatically detach on last close
220 (so users do not have to remember to detach providers after unmounting
223 Allows attaching a provider with a random, one-time Master Key -
224 useful for swap partitions and temporary file systems.
226 Allows verification of data integrity (data authentication).
228 Allows suspending and resuming encrypted devices.
231 The first argument to
233 indicates an action to be performed:
234 .Bl -tag -width ".Cm configure"
236 Initialize the provider which needs to be encrypted.
237 Here you can set up the cryptographic algorithm to use, Data Key length,
239 The last sector of the provider is used to store metadata.
242 subcommand also automatically writes metadata backups to
243 .Pa /var/backups/<prov>.eli
245 The metadata can be recovered with the
247 subcommand described below.
249 Additional options include:
250 .Bl -tag -width ".Fl J Ar newpassfile"
252 Enable data integrity verification (authentication) using the given algorithm.
253 This will reduce the size of storage available and also reduce speed.
254 For example, when using 4096 bytes sector and
256 algorithm, 89% of the original provider storage will be available for use.
257 Currently supported algorithms are:
265 If the option is not given, there will be no authentication, only encryption.
266 The recommended algorithm is
269 Try to decrypt this partition during boot, before the root partition is mounted.
270 This makes it possible to use an encrypted root partition.
271 One will still need bootable unencrypted storage with a
273 directory, which can be a CD-ROM disc or USB pen-drive, that can be removed
275 .It Fl B Ar backupfile
276 File name to use for metadata backup instead of the default
277 .Pa /var/backups/<prov>.eli .
278 To inhibit backups, you can use
283 Encryption algorithm to use.
284 Currently supported algorithms are:
292 The default and recommended algorithm is
297 Enable booting from this encrypted root filesystem.
298 The boot loader prompts for the passphrase and loads
300 from the encrypted partition.
301 .It Fl i Ar iterations
302 Number of iterations to use with PKCS#5v2 when processing User Key
303 passphrase component.
304 If this option is not specified,
306 will find the number of iterations which is equal to 2 seconds of crypto work.
307 If 0 is given, PKCS#5v2 will not be used.
308 PKCS#5v2 processing is performed once, after all parts of the passphrase
309 component have been read.
310 .It Fl J Ar newpassfile
311 Specifies a file which contains the passphrase component of the User Key
315 is given as -, standard input will be used.
316 Only the first line (excluding new-line character) is taken from the given file.
317 This argument can be specified multiple times, which has the effect of
318 reassembling a single passphrase split across multiple files.
319 Cannot be combined with the
322 .It Fl K Ar newkeyfile
323 Specifies a file which contains the keyfile component of the User Key
327 is given as -, standard input will be used.
328 This argument can be specified multiple times, which has the effect of
329 reassembling a single keyfile split across multiple keyfile parts.
331 Data Key length to use with the given cryptographic algorithm.
332 If the length is not specified, the selected algorithm uses its
335 .Bl -ohang -offset indent
339 .It Nm AES-CBC , Nm Camellia-CBC
345 + n * 32, for n=[0..10]
350 Do not use a passphrase as a component of the User Key.
351 Cannot be combined with the
354 .It Fl s Ar sectorsize
355 Change decrypted provider's sector size.
356 Increasing the sector size allows increased performance,
357 because encryption/decryption which requires an initialization vector
358 is done per sector; fewer sectors means less computational work.
362 calls (i.e., TRIM/UNMAP).
363 This can prevent an attacker from knowing how much space you're actually
364 using and which sectors contain live data, but will also prevent the
365 backing store (SSD, etc) from reclaiming space you're not using, which
366 may degrade its performance and lifespan.
367 The underlying provider may or may not actually obliterate the deleted
368 sectors when TRIM is enabled, so it should not be considered to add any
371 Metadata version to use.
372 This option is helpful when creating a provider that may be used by older
377 section to find which metadata version is supported by which FreeBSD version.
378 Note that using an older version of metadata may limit the number of
382 Attach the given provider.
383 The encrypted Master Key will be loaded from the metadata and decrypted
384 using the given passphrase/keyfile and a new GEOM provider will be created
385 using the given provider's name with an
389 Additional options include:
390 .Bl -tag -width ".Fl j Ar passfile"
392 If specified, a decrypted provider will be detached automatically on last close.
393 This can help with scarce memory so the user does not have to remember to detach the
394 provider after unmounting the file system.
395 It only works when the provider was opened for writing, so it will not work if
396 the file system on the provider is mounted read-only.
397 Probably a better choice is the
403 Specifies a file which contains the passphrase component of the User Key
405 For more information see the description of the
411 Specifies a file which contains the keyfile component of the User Key
413 For more information see the description of the
419 Do not use a passphrase as a component of the User Key.
420 Cannot be combined with the
424 Attach read-only provider.
425 It will not be opened for writing.
428 Detach the given providers, which means remove the devfs entry
429 and clear the Master Key and Data Keys from memory.
431 Additional options include:
432 .Bl -tag -width ".Fl f"
434 Force detach - detach even if the provider is open.
436 Mark provider to detach on last close.
437 If this option is specified, the provider will not be detached
438 while it is open, but will be automatically detached when it is closed for the
439 last time even if it was only opened for reading.
442 Attach the given providers with a random, one-time (ephemeral) Master Key.
443 The command can be used to encrypt swap partitions or temporary file systems.
445 Additional options include:
446 .Bl -tag -width ".Fl a Ar sectorsize"
448 Enable data integrity verification (authentication).
449 For more information, see the description of the
453 Encryption algorithm to use.
454 For more information, see the description of the
458 Detach on last close.
459 Note: this option is not usable for temporary file systems as the provider will
460 be detached after creating the file system on it.
461 It still can (and should be) used for swap partitions.
462 For more information, see the description of the
466 Data Key length to use with the given cryptographic algorithm.
467 For more information, see the description of the
470 .It Fl s Ar sectorsize
471 Change decrypted provider's sector size.
472 For more information, see the description of the
476 Disable TRIM/UNMAP passthru.
477 For more information, see the description of the
482 Change configuration of the given providers.
484 Additional options include:
485 .Bl -tag -width ".Fl b"
487 Set the BOOT flag on the given providers.
488 For more information, see the description of the
492 Remove the BOOT flag from the given providers.
494 Enable booting from this encrypted root filesystem.
495 The boot loader prompts for the passphrase and loads
497 from the encrypted partition.
499 Deactivate booting from this encrypted root partition.
501 Enable TRIM/UNMAP passthru.
502 For more information, see the description of the
506 Disable TRIM/UNMAP passthru.
509 Install a copy of the Master Key into the selected slot, encrypted with
511 If the selected slot is populated, replace the existing copy.
512 A provider has one Master Key, which can be stored in one or both slots,
513 each encrypted with an independent User Key.
516 subcommand, only key number 0 is initialized.
517 The User Key can be changed at any time: for an attached provider,
518 for a detached provider, or on the backup file.
519 When a provider is attached, the user does not have to provide
520 an existing passphrase/keyfile.
522 Additional options include:
523 .Bl -tag -width ".Fl J Ar newpassfile"
524 .It Fl i Ar iterations
525 Number of iterations to use with PKCS#5v2.
526 If 0 is given, PKCS#5v2 will not be used.
527 To be able to use this option with the
529 subcommand, only one key has to be defined and this key must be changed.
531 Specifies a file which contains the passphrase component of a current User Key
533 .It Fl J Ar newpassfile
534 Specifies a file which contains the passphrase component of the new User Key
537 Specifies a file which contains the keyfile component of a current User Key
539 .It Fl K Ar newkeyfile
540 Specifies a file which contains the keyfile component of the new User Key
543 Specifies the index number of the Master Key copy to change (could be 0 or 1).
544 If the provider is attached and no key number is given, the key
545 used for attaching the provider will be changed.
546 If the provider is detached (or we are operating on a backup file)
547 and no key number is given, the first Master Key copy to be successfully
548 decrypted with the provided User Key passphrase/keyfile will be changed.
550 Do not use a passphrase as a component of the current User Key.
551 Cannot be combined with the
555 Do not use a passphrase as a component of the new User Key.
556 Cannot be combined with the
561 Destroy (overwrite with random data) the selected Master Key copy.
562 If one is destroying keys for an attached provider, the provider
563 will not be detached even if all copies of the Master Key are destroyed.
564 It can even be rescued with the
566 subcommand because the Master Key is still in memory.
568 Additional options include:
569 .Bl -tag -width ".Fl a Ar keyno"
571 Destroy all copies of the Master Key (does not need
575 Force key destruction.
576 This option is needed to destroy the last copy of the Master Key.
578 Specifies the index number of the Master Key copy.
579 If the provider is attached and no key number is given, the key
580 used for attaching the provider will be destroyed.
581 If provider is detached (or we are operating on a backup file) the key number
585 This command should be used only in emergency situations.
586 It will destroy all copies of the Master Key on a given provider and will
587 detach it forcibly (if it is attached).
588 This is absolutely a one-way command - if you do not have a metadata
589 backup, your data is gone for good.
590 In case the provider was attached with the
592 flag, the keys will not be destroyed, only the provider will be detached.
594 Additional options include:
595 .Bl -tag -width ".Fl a"
597 If specified, all currently attached providers will be killed.
600 Backup metadata from the given provider to the given file.
602 Restore metadata from the given file to the given provider.
604 Additional options include:
605 .Bl -tag -width ".Fl f"
607 Metadata contains the size of the provider to ensure that the correct
608 partition or slice is attached.
609 If an attempt is made to restore metadata to a provider that has a different
612 will refuse to restore the data unless the
615 If the partition or slice has been grown, the
617 subcommand should be used rather than attempting to relocate the metadata
624 Suspend device by waiting for all inflight requests to finish, clearing all
625 sensitive information (like the Master Key and Data Keys) from kernel memory,
626 and blocking all further I/O requests until the
628 subcommand is executed.
629 This functionality is useful for laptops: when one wants to suspend a
630 laptop, one does not want to leave an encrypted device attached.
631 Instead of closing all files and directories opened from a file system located
632 on an encrypted device, unmounting the file system, and detaching the device,
635 subcommand can be used.
636 Any access to the encrypted device will be blocked until the Master Key is
640 Thus there is no need to close nor unmount anything.
643 subcommand does not work with devices created with the
646 Please note that sensitive data might still be present in memory after
647 suspending an encrypted device due to the file system cache, etc.
649 Additional options include:
650 .Bl -tag -width ".Fl a"
657 Resume previously suspended device.
658 The caller must ensure that executing this subcommand does not access the
659 suspended device, leading to a deadlock.
660 For example suspending a device which contains the file system where the
662 utility is stored is bad idea.
664 Additional options include:
665 .Bl -tag -width ".Fl j Ar passfile"
667 Specifies a file which contains the passphrase component of the User Key
669 For more information see the description of the
675 Specifies a file which contains the keyfile component of the User Key
677 For more information see the description of the
683 Do not use a passphrase as a component of the User Key.
684 Cannot be combined with the
691 that the provider has been resized.
692 The old metadata block is relocated to the correct position at the end of the
693 provider and the provider size is updated.
695 Additional options include:
696 .Bl -tag -width ".Fl s Ar oldsize"
698 The size of the provider before it was resized.
701 If no arguments are given, the
703 subcommand will print the version of
705 userland utility as well as the version of the
709 If GEOM providers are specified, the
711 subcommand will print metadata version used by each of them.
713 Clear metadata from the given providers.
715 This will erase with zeros the encrypted Master Key copies stored in the
718 Dump metadata stored on the given providers.
733 Additional options include:
734 .Bl -tag -width ".Fl v"
744 utility generates a random Master Key for the provider.
745 The Master Key never changes during the lifetime of the provider.
746 Each copy of the provider metadata, active or backed up to a file, can store
747 up to two, independently-encrypted copies of the Master Key.
749 Each stored copy of the Master Key is encrypted with a User Key, which
752 utility from a passphrase and/or a keyfile.
755 utility first reads all parts of the keyfile in the order specified on the
756 command line, then reads all parts of the stored passphrase in the order
757 specified on the command line.
758 If no passphrase parts are specified, the system prompts the user to enter
760 The passphrase is optionally strengthened by PKCS#5v2.
761 The User Key is a digest computed over the concatenated keyfile and passphrase.
763 During operation, one or more Data Keys are deterministically derived by
764 the kernel from the Master Key and cached in memory.
765 The number of Data Keys used by a given provider, and the way they are
766 derived, depend on the GELI version and whether the provider is configured to
767 use data authentication.
771 variables can be used to control the behavior of the
774 The default value is shown next to each variable.
775 Some variables can also be set in
776 .Pa /boot/loader.conf .
777 .Bl -tag -width indent
778 .It Va kern.geom.eli.version
779 Version number of the
782 .It Va kern.geom.eli.debug : No 0
786 This can be set to a number between 0 and 3 inclusive.
787 If set to 0, minimal debug information is printed.
789 maximum amount of debug information is printed.
790 .It Va kern.geom.eli.tries : No 3
791 Number of times a user is asked for the passphrase.
792 This is only used for providers which are attached on boot
793 (before the root file system is mounted).
794 If set to 0, attaching providers on boot will be disabled.
795 This variable should be set in
796 .Pa /boot/loader.conf .
797 .It Va kern.geom.eli.overwrites : No 5
798 Specifies how many times the Master Key will be overwritten
799 with random values when it is destroyed.
800 After this operation it is filled with zeros.
801 .It Va kern.geom.eli.visible_passphrase : No 0
802 If set to 1, the passphrase entered on boot (before the root
803 file system is mounted) will be visible.
804 This alternative should be used with caution as the entered
805 passphrase can be logged and exposed via
807 This variable should be set in
808 .Pa /boot/loader.conf .
809 .It Va kern.geom.eli.threads : No 0
810 Specifies how many kernel threads should be used for doing software
812 Its purpose is to increase performance on SMP systems.
813 If set to 0, a CPU-pinned thread will be started for every active CPU.
814 .It Va kern.geom.eli.batch : No 0
815 When set to 1, can speed-up crypto operations by using batching.
816 Batching reduces the number of interrupts by responding to a group of
817 crypto requests with one interrupt.
818 The crypto card and the driver has to support this feature.
819 .It Va kern.geom.eli.key_cache_limit : No 8192
820 Specifies how many Data Keys to cache.
822 (8192 keys) will allow caching of all keys for a 4TB provider with 512 byte
823 sectors and will take around 1MB of memory.
824 .It Va kern.geom.eli.key_cache_hits
825 Reports how many times we were looking up a Data Key and it was already in
827 This sysctl is not updated for providers that need fewer Data Keys than
828 the limit specified in
829 .Va kern.geom.eli.key_cache_limit .
830 .It Va kern.geom.eli.key_cache_misses
831 Reports how many times we were looking up a Data Key and it was not in cache.
832 This sysctl is not updated for providers that need fewer Data Keys than the limit
834 .Va kern.geom.eli.key_cache_limit .
837 Exit status is 0 on success, and 1 if the command fails.
839 Initialize a provider which is going to be encrypted with a
840 passphrase and random data from a file on the user's pen drive.
842 Attach the provider, create a file system, and mount it.
844 Unmount the provider and detach it:
845 .Bd -literal -offset indent
846 # dd if=/dev/random of=/mnt/pendrive/da2.key bs=64 count=1
847 # geli init -s 4096 -K /mnt/pendrive/da2.key /dev/da2
848 Enter new passphrase:
849 Reenter new passphrase:
850 # geli attach -k /mnt/pendrive/da2.key /dev/da2
852 # dd if=/dev/random of=/dev/da2.eli bs=1m
854 # mount /dev/da2.eli /mnt/secret
857 # geli detach da2.eli
860 Create an encrypted provider, but use two User Keys:
861 one for your employee and one for you as the company's security officer
862 (so it is not a tragedy if the employee
864 forgets his passphrase):
865 .Bd -literal -offset indent
867 Enter new passphrase: (enter security officer's passphrase)
868 Reenter new passphrase:
869 # geli setkey -n 1 /dev/da2
870 Enter passphrase: (enter security officer's passphrase)
871 Enter new passphrase: (let your employee enter his passphrase ...)
872 Reenter new passphrase: (... twice)
875 You are the security officer in your company.
876 Create an encrypted provider for use by the user, but remember that users
877 forget their passphrases, so backup the Master Key with your own random key:
878 .Bd -literal -offset indent
879 # dd if=/dev/random of=/mnt/pendrive/keys/`hostname` bs=64 count=1
880 # geli init -P -K /mnt/pendrive/keys/`hostname` /dev/ada0s1e
881 # geli backup /dev/ada0s1e /mnt/pendrive/backups/`hostname`
882 (use key number 0, so the encrypted Master Key will be re-encrypted by this)
883 # geli setkey -n 0 -k /mnt/pendrive/keys/`hostname` /dev/ada0s1e
884 (allow the user to enter his passphrase)
885 Enter new passphrase:
886 Reenter new passphrase:
889 Encrypted swap partition setup:
890 .Bd -literal -offset indent
891 # dd if=/dev/random of=/dev/ada0s1b bs=1m
892 # geli onetime -d -e 3des ada0s1b
893 # swapon /dev/ada0s1b.eli
896 The example below shows how to configure two providers which will be attached
897 on boot (before the root file system is mounted).
898 One of them is using passphrase and three keyfile parts and the other is
899 using only a keyfile in one part:
900 .Bd -literal -offset indent
901 # dd if=/dev/random of=/dev/da0 bs=1m
902 # dd if=/dev/random of=/boot/keys/da0.key0 bs=32k count=1
903 # dd if=/dev/random of=/boot/keys/da0.key1 bs=32k count=1
904 # dd if=/dev/random of=/boot/keys/da0.key2 bs=32k count=1
905 # geli init -b -K /boot/keys/da0.key0 -K /boot/keys/da0.key1 -K /boot/keys/da0.key2 da0
906 Enter new passphrase:
907 Reenter new passphrase:
908 # dd if=/dev/random of=/dev/da1s3a bs=1m
909 # dd if=/dev/random of=/boot/keys/da1s3a.key bs=128k count=1
910 # geli init -b -P -K /boot/keys/da1s3a.key da1s3a
913 The providers are initialized, now we have to add these lines to
914 .Pa /boot/loader.conf :
915 .Bd -literal -offset indent
916 geli_da0_keyfile0_load="YES"
917 geli_da0_keyfile0_type="da0:geli_keyfile0"
918 geli_da0_keyfile0_name="/boot/keys/da0.key0"
919 geli_da0_keyfile1_load="YES"
920 geli_da0_keyfile1_type="da0:geli_keyfile1"
921 geli_da0_keyfile1_name="/boot/keys/da0.key1"
922 geli_da0_keyfile2_load="YES"
923 geli_da0_keyfile2_type="da0:geli_keyfile2"
924 geli_da0_keyfile2_name="/boot/keys/da0.key2"
926 geli_da1s3a_keyfile0_load="YES"
927 geli_da1s3a_keyfile0_type="da1s3a:geli_keyfile0"
928 geli_da1s3a_keyfile0_name="/boot/keys/da1s3a.key"
931 If there is only one keyfile, the index might be omitted:
932 .Bd -literal -offset indent
933 geli_da1s3a_keyfile_load="YES"
934 geli_da1s3a_keyfile_type="da1s3a:geli_keyfile"
935 geli_da1s3a_keyfile_name="/boot/keys/da1s3a.key"
938 Not only configure encryption, but also data integrity verification using
940 .Bd -literal -offset indent
941 # geli init -a hmac/sha256 -s 4096 /dev/da0
942 Enter new passphrase:
943 Reenter new passphrase:
944 # geli attach /dev/da0
946 # dd if=/dev/random of=/dev/da0.eli bs=1m
948 # mount /dev/da0.eli /mnt/secret
952 writes the metadata backup by default to the
953 .Pa /var/backups/<prov>.eli
955 If the metadata is lost in any way (e.g., by accidental overwrite), it can be restored.
956 Consider the following situation:
957 .Bd -literal -offset indent
959 Enter new passphrase:
960 Reenter new passphrase:
962 Metadata backup can be found in /var/backups/da0.eli and
963 can be restored with the following command:
965 # geli restore /var/backups/da0.eli /dev/da0
967 # geli clear /dev/da0
968 # geli attach /dev/da0
969 geli: Cannot read metadata from /dev/da0: Invalid argument.
970 # geli restore /var/backups/da0.eli /dev/da0
971 # geli attach /dev/da0
975 If an encrypted file system is extended, it is necessary to relocate and
977 .Bd -literal -offset indent
978 # gpart create -s GPT ada0
979 # gpart add -s 1g -t freebsd-ufs -i 1 ada0
980 # geli init -K keyfile -P ada0p1
981 # gpart resize -s 2g -i 1 ada0
982 # geli resize -s 1g ada0p1
983 # geli attach -k keyfile -p ada0p1
986 Initialize provider with the passphrase split into two files.
987 The provider can be attached using those two files or by entering
989 as the passphrase at the
992 .Bd -literal -offset indent
993 # echo foo > da0.pass0
994 # echo bar > da0.pass1
995 # geli init -J da0.pass0 -J da0.pass1 da0
996 # geli attach -j da0.pass0 -j da0.pass1 da0
999 Enter passphrase: foobar
1004 devices on a laptop, suspend the laptop, then resume devices one by one after
1005 resuming the laptop:
1006 .Bd -literal -offset indent
1009 <resume your laptop>
1010 # geli resume -p -k keyfile gpt/secret
1011 # geli resume gpt/private
1014 .Sh ENCRYPTION MODES
1016 supports two encryption modes:
1018 which was standardized as
1022 with unpredictable IV.
1027 is very similar to the mode
1029 .Sh DATA AUTHENTICATION
1031 can verify data integrity when an authentication algorithm is specified.
1032 When data corruption/modification is detected,
1034 will not return any data, but instead will return an error
1036 The offset and size of the corrupted data will be printed on the console.
1037 It is important to know against which attacks
1039 provides protection for your data.
1040 If data is modified in-place or copied from one place on the disk
1041 to another even without modification,
1043 should be able to detect such a change.
1044 If an attacker can remember the encrypted data, he can overwrite any future
1045 changes with the data he owns without it being noticed.
1048 will not protect your data against replay attacks.
1050 It is recommended to write to the whole provider before first use,
1051 in order to make sure that all sectors and their corresponding
1052 checksums are properly initialized into a consistent state.
1053 One can safely ignore data authentication errors that occur immediately
1054 after the first time a provider is attached and before it is
1055 initialized in this way.
1071 block cipher is implemented by Yoshisato Yanagisawa in
1076 metadata version supported by the given FreeBSD version:
1077 .Bl -column -offset indent ".Sy FreeBSD" ".Sy version"
1078 .It Sy FreeBSD Ta Sy GELI
1079 .It Sy version Ta Sy version
1102 .An Pawel Jakub Dawidek Aq Mt pjd@FreeBSD.org
projects / FreeBSD / FreeBSD.git / blob