Bug 1574239

Summary: cryptsetup-reencrypt manpage typos
Product: Red Hat Enterprise Linux 7 Reporter: Corey Marthaler <cmarthal>
Component: cryptsetupAssignee: Ondrej Kozina <okozina>
Status: CLOSED ERRATA QA Contact: Release Test Team <release-test-team-automation>
Severity: low Docs Contact:
Priority: unspecified    
Version: 7.5CC: agk, atodorov, jstodola, mbroz, okozina, prajnoha, rhandlin
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: cryptsetup-2.0.3-1.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-30 11:29:13 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Corey Marthaler 2018-05-02 21:21:10 UTC
Description of problem:

1.
s/you can lose you/you can lose your/
       WARNING: The cryptsetup-reencrypt program is not resistant to  hardware
       or  kernel  failures during reencryption (you can lose you data in this
       case).

2.
s/by/be
       Current  working directory must by writable and temporary files created
       during reencryption must be present.


3.
s/there only/there is only/
              WARNING:  --key-file  option  can be used only if there only one



Version-Release number of selected component (if applicable):
cryptsetup-reencrypt-1.7.4-4.el7.x86_64

Comment 2 Ondrej Kozina 2018-05-03 12:42:17 UTC
Thanks Corey!

The first was already fixed in upstream. I've added remaining two.

commit: https://gitlab.com/cryptsetup/cryptsetup/commit/14f81cb275dc3b398a158ececac3683e2a6a0959

Comment 4 Alexander Todorov 2018-07-11 08:41:01 UTC
All 3 fixed in cryptsetup-reencrypt-2.0.3-1.el7.x86_64

Comment 7 errata-xmlrpc 2018-10-30 11:29:13 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:3239