13
13
log from being able to access the data stored in those files.
14
14
For example, when using cluster file encryption, users who have read
15
15
access to the cluster directories for backup purposes will not be able
16
- to decrypt the data stored in the these files.
16
+ to decrypt the data stored in these files.
17
17
</para>
18
18
19
19
<para>
24
24
Key one is used to encrypt write-ahead log (WAL) files. Two different
25
25
keys are used so that primary and standby servers can use different zero
26
26
(heap/index/temp) keys, but the same one (WAL) key, so that these keys
27
- can eventually be rotated by switching the primary to the standby as
27
+ can eventually be rotated by switching the primary to the standby
28
28
and then changing the WAL key.
29
29
</para>
30
30
@@ -68,7 +68,7 @@ initdb -D dbname --cluster-key-command='ckey_passphrase.sh'
68
68
During the <command>initdb</command> process, if
69
69
<option>--cluster-key-command</option> is specified, two data-level
70
70
encryption keys are created. These two keys are then encrypted with
71
- the key enryption key (KEK) supplied by the cluster key command before
71
+ the key encryption key (KEK) supplied by the cluster key command before
72
72
being stored in the database directory. The key or passphrase that
73
73
derives the key must be supplied from the terminal or stored in a
74
74
trusted key store, such as key vault software, hardware security module.
@@ -87,7 +87,7 @@ initdb -D dbname --cluster-key-command='ckey_passphrase.sh'
87
87
</para>
88
88
89
89
<para>
90
- The data encryption keys are randomly generated and are of 128, 192,
90
+ The data encryption keys are randomly generated and are 128, 192,
91
91
or 256-bits in length. They are encrypted by the key encryption key
92
92
(KEK) using Advanced Encryption Standard (<acronym>AES256</acronym>)
93
93
encryption in Galois/Counter Mode (<acronym>GCM</acronym>), which also
0 commit comments