summaryrefslogtreecommitdiffstats
path: root/sbin/geom/class
diff options
context:
space:
mode:
authorbrueffer <brueffer@FreeBSD.org>2006-06-06 19:03:51 +0000
committerbrueffer <brueffer@FreeBSD.org>2006-06-06 19:03:51 +0000
commitb3ea269400d8b89e620574bc3fd9af3e1cc46444 (patch)
treefb8c05756dbfd2c37d88e99719103f06a3549210 /sbin/geom/class
parentc0d73ceee51380e59f394bc7b61ca4ac30183ec6 (diff)
downloadFreeBSD-src-b3ea269400d8b89e620574bc3fd9af3e1cc46444.zip
FreeBSD-src-b3ea269400d8b89e620574bc3fd9af3e1cc46444.tar.gz
Clarify and merge two sentences.
Discussed with: pjd
Diffstat (limited to 'sbin/geom/class')
-rw-r--r--sbin/geom/class/eli/geli.86
1 files changed, 2 insertions, 4 deletions
diff --git a/sbin/geom/class/eli/geli.8 b/sbin/geom/class/eli/geli.8
index c84a28f..e0ceeb0 100644
--- a/sbin/geom/class/eli/geli.8
+++ b/sbin/geom/class/eli/geli.8
@@ -611,10 +611,8 @@ If data is modified or copied from one place on the disk
to another,
.Nm
should be able to detect such a modification.
-If an attacker can remember the encrypted data, he can write them back to the
-same place.
-This will not be detected even if the data were legally modified
-between read and write operations of the attacker.
+If an attacker can remember the encrypted data, modify them and write them
+back to the same place, the modification will not be detected.
.Nm
will not protect your data against replay attacks.
.Sh SEE ALSO
OpenPOWER on IntegriCloud