Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 1510841

Summary: cryptsetup: Fix for unaligned access to hidden truecrypt header caused regression on systems with pagesize > 4KiB [rhel-7.4.z]
Product: Red Hat Enterprise Linux 7 Reporter: Oneata Mircea Teodor <toneata>
Component: cryptsetupAssignee: Ondrej Kozina <okozina>
Status: CLOSED ERRATA QA Contact: Release Test Team <release-test-team>
Severity: high Docs Contact: Marc Muehlfeld <mmuehlfe>
Priority: high    
Version: 7.5CC: agk, bugproxy, hannsj_uhl, jbrassow, jkachuck, jstodola, mbroz, okozina, pkotvan, prajnoha, release-test-team, rhandlin
Target Milestone: rcKeywords: Patch, Regression, ZStream
Target Release: ---   
Hardware: ppc64le   
OS: Linux   
Fixed In Version: cryptsetup-1.7.4-3.el7_4.1 Doc Type: Bug Fix
Doc Text:
Due to a bug, the cryptsetup utility previously failed to open certain TrueCrypt images on architectures that use a page size greater than 4 KiB. The problem has been fixed, and cryptsetup now checks that read and write operations for the last part of an image is exactly the requested size instead of a full block. As a result, opening TrueCrypt images works as expected in the mentioned scenario.
Story Points: ---
Clone Of: 1479857 Environment:
Last Closed: 2017-11-30 16:11:26 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 1479857    
Bug Blocks:    

Description Oneata Mircea Teodor 2017-11-08 10:19:26 UTC
This bug has been copied from bug #1479857 and has been proposed to be backported to 7.4 z-stream (EUS).

Comment 10 errata-xmlrpc 2017-11-30 16:11:26 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.