Description of problem:
change in message when passphrase is provided to cryptsetup in RHEL-7.6
Version-Release number of selected component (if applicable):
cryptsetup-2.0.3-3.el7.x86_64
cryptsetup-libs-2.0.3-3.el7.x86_64
cryptsetup-python-2.0.3-3.el7.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Create file using dd and use it to create loop device
$ dd if=/dev/urandom of=/opt/cntdb/data/secure.img bs=100M count=0 seek=1
$ losetup /dev/loop0 /opt/cntdb/data/secure.img
2. Setup luks format device using cryptsetup
$ cryptsetup -q -y luksFormat /dev/loop0
Enter passphrase for /dev/loop0:
Verify passphrase:
3. Opens the LUKS device
$ cryptsetup luksOpen /dev/loop0 encrypted
Enter passphrase for /dev/loop0:
^^^^^^^^^^^^
Actual results:
Message prints the loop device name "/dev/loop0" when passphrase is provided
Expected results:
It should print the name of backing file name as below.
$ cryptsetup luksOpen /dev/loop0 encrypted
Enter passphrase for /opt/cntdb/data/secure.img:
^^^^^^^^^^^^^^^^^^^^^^^^^^
Additional info:
We see expected result in older version RHEL-7.4
[root@rhel7-debuginfo-2 ~]# cat /etc/redhat-release
Red Hat Enterprise Linux Server release 7.4 (Maipo)
[root@rhel7-debuginfo-2 ~]# rpm -qa | grep crypt
cryptsetup-1.7.4-3.el7.x86_64
[root@rhel7-debuginfo-2 ~]# cryptsetup luksOpen /dev/loop0 encrypted
Enter passphrase for /opt/cntdb/data/secure.img: -----------> prompt for mount point
Comment 5guazhang@redhat.com
2019-09-11 04:07:20 UTC
Hello
# cryptsetup -q -y luksFormat /dev/loop0p1
Enter passphrase for /dev/loop0p1:
Verify passphrase:
]# cryptsetup luksOpen /dev/loop0p1 encryp
Enter passphrase for /dev/loop0p1:
# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 15G 0 loop
└─loop0p1 259:0 0 9.3G 0 loop
└─encryp 253:7 0 9.3G 0 crypt
so move to verified
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-2020:1130
Description of problem: change in message when passphrase is provided to cryptsetup in RHEL-7.6 Version-Release number of selected component (if applicable): cryptsetup-2.0.3-3.el7.x86_64 cryptsetup-libs-2.0.3-3.el7.x86_64 cryptsetup-python-2.0.3-3.el7.x86_64 How reproducible: Always Steps to Reproduce: 1. Create file using dd and use it to create loop device $ dd if=/dev/urandom of=/opt/cntdb/data/secure.img bs=100M count=0 seek=1 $ losetup /dev/loop0 /opt/cntdb/data/secure.img 2. Setup luks format device using cryptsetup $ cryptsetup -q -y luksFormat /dev/loop0 Enter passphrase for /dev/loop0: Verify passphrase: 3. Opens the LUKS device $ cryptsetup luksOpen /dev/loop0 encrypted Enter passphrase for /dev/loop0: ^^^^^^^^^^^^ Actual results: Message prints the loop device name "/dev/loop0" when passphrase is provided Expected results: It should print the name of backing file name as below. $ cryptsetup luksOpen /dev/loop0 encrypted Enter passphrase for /opt/cntdb/data/secure.img: ^^^^^^^^^^^^^^^^^^^^^^^^^^ Additional info: We see expected result in older version RHEL-7.4 [root@rhel7-debuginfo-2 ~]# cat /etc/redhat-release Red Hat Enterprise Linux Server release 7.4 (Maipo) [root@rhel7-debuginfo-2 ~]# rpm -qa | grep crypt cryptsetup-1.7.4-3.el7.x86_64 [root@rhel7-debuginfo-2 ~]# cryptsetup luksOpen /dev/loop0 encrypted Enter passphrase for /opt/cntdb/data/secure.img: -----------> prompt for mount point