search for: cryptsetup

On Monday, 7 September 2020 11:43:54 CEST Richard W.M. Jones wrote: > This commit deprecates luks-open/luks-open-ro/luks-close for the more > generic sounding names cryptsetup-open/cryptsetup-close, which also > correspond directly to the cryptsetup commands. > > The optional cryptsetup-open readonly flag is used to replace the > functionality of luks-open-ro. > > The optional cryptsetup-open crypttype parameter can be used to select > the type (co...

...;> Clues for the poor? Yes, the server will, at some point in the future, >> go to CentOS 7, but that needs my user to be off for a while, and his jobs >> run literally for weeks, with loads upwords of 30 on an HBS (honkin' big >> server).... > > MAPDEVICE=/dev/sdxy ; cryptsetup luksOpen ${MAPDEVICE} luks-$(cryptsetup > luksUUID ${MAPDEVICE}) Something's not right. I did cryptsetup luksOpen /dev/sdb luks-$(cryptsetup luksUUID $(/dev/sdb)) --key-file /etc/crypt.pw It did want the password, so I added --key-file, but it seems to have created /dev/mapper/luks, not th...

...Errata and Bugfix Advisory 2017:3330 Upstream details at : https://access.redhat.com/errata/RHBA-2017:3330 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 05b360cd746586e2cb31c3b5aecfccfa6d46e762a63e17d90fe58c0673ef7958 cryptsetup-1.7.4-3.el7_4.1.x86_64.rpm 6ab99ca682d66a92cbb41a280bfb9b888765df58a725b196a2dc591e69a09f46 cryptsetup-devel-1.7.4-3.el7_4.1.i686.rpm 8529c48d49199fb3cc70eabfed02764c54e5a789d69c849780162defeb55c329 cryptsetup-devel-1.7.4-3.el7_4.1.x86_64.rpm f1a3b716795383298998d1bffde622b0bc461aef695e6a07fc0b38...

This commit deprecates luks-open/luks-open-ro/luks-close for the more generic sounding names cryptsetup-open/cryptsetup-close, which also correspond directly to the cryptsetup commands. The optional cryptsetup-open readonly flag is used to replace the functionality of luks-open-ro. The optional cryptsetup-open crypttype parameter can be used to select the type (corresponding to cryptsetup open --ty...

This commit deprecates luks-open/luks-open-ro/luks-close for the more generic sounding names cryptsetup-open/cryptsetup-close, which also correspond directly to the cryptsetup commands. The optional cryptsetup-open readonly flag is used to replace the functionality of luks-open-ro. The optional cryptsetup-open crypttype parameter can be used to select the type (corresponding to cryptsetup open --ty...

On Mon, Sep 07, 2020 at 10:41:20AM +0100, Richard W.M. Jones wrote: >For BitLocker disks cryptsetup does not (yet? ever?) support reading >UUIDs and this function will fail. This does not matter here so just >ignore the error. > >Note there is no error message, cryptsetup simply returns with a bad >exit code: > >><rescue> cryptsetup luksUUID /dev/sda2 >><re...

CentOS Errata and Bugfix Advisory 2011:0987 Upstream details at : https://rhn.redhat.com/errata/RHBA-2011-0987.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) x86_64: 43373cbbed09bbc76a26cdee67af757f cryptsetup-luks-1.0.3-8.el5.i386.rpm 5d9d213b916577d8cd99cc194e583691 cryptsetup-luks-1.0.3-8.el5.x86_64.rpm 31580d6954545200bcaeb9b3cf3b610f cryptsetup-luks-devel-1.0.3-8.el5.i386.rpm 56bdcc7c1315ecbdee1815c358e33f41 cryptsetup-luks-devel-1.0.3-8.el5.x86_64.rpm Source: fab5e9ff77de2d9b0da2ed23d8146d02 c...

On Tue, Oct 06, 2020 at 03:06:54PM +0100, Richard W.M. Jones wrote: >On Tue, Oct 06, 2020 at 03:25:20PM +0200, Martin Kletzander wrote: >> On Mon, Sep 07, 2020 at 10:41:20AM +0100, Richard W.M. Jones wrote: >> >For BitLocker disks cryptsetup does not (yet? ever?) support reading >> >UUIDs and this function will fail. This does not matter here so just >> >ignore the error. >> > >> >Note there is no error message, cryptsetup simply returns with a bad >> >exit code: >> > >> >...

https://gitlab.com/cryptsetup/cryptsetup/issues/488 This prevents virt-* tools from opening encrypted partitions automatically. Even 1024M isn't sufficient. I had to bump the memory up to 1400M to make it work, which is just too big for routine use. Even worse if the RAM size isn't quite large enough (eg 1200M) cryp...

These commits, along with the associated changes to common: https://www.redhat.com/archives/libguestfs/2020-March/msg00286.html support the transparent decryption and inspection of Windows guests encrypted with BitLocker encryption. To do the BitLocker decryption requires cryptsetup 2.3.0 (although cryptsetup 2.3 is not required for existing LUKS use). It also requires a new-ish Linux kernel, I believe 5.3+ This starts by adding new APIs cryptsetup-open and cryptsetup-close. As well as dropping the "luks-" prefix, this allows specifying an optional type parameter,...

On a just-built C 7 box, I've got this: boot, boot_efi, /, swap, and export. Now, the last three are encrypted. For /, I'm trying to add an escrow key. df -h shows me that / is /dev/dm-1. However, when I use cryptsetup luksAddKey /dev/dm-1, it just comes back, without prompting me for a password. What am I missing? mark

...text file in vim does not qualify as a valid password. Instead, a valid keyfile is created by doing the following: echo -n "password" > keyfile.key which explicitly creates the file with password on the first line with an explicit newline at the end of the file. This is because cryptsetup needs a newline at the end of the keyfile. Just using a text editor like vim does not create a valid keyfile that cryptsetup can equate with a key for an encrypted volume. This addition is (at least) worth six hours of my time, so hence may be worth about that much to anyone who may read...

CentOS Errata and Bugfix Advisory 2011:0987 Upstream details at : https://rhn.redhat.com/errata/RHBA-2011-0987.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) i386: 46b5fa919e72f7feeb280b43decc335e cryptsetup-luks-1.0.3-8.el5.i386.rpm dfcf63435dbd6cdd8d1779514329cc4b cryptsetup-luks-devel-1.0.3-8.el5.i386.rpm Source: fab5e9ff77de2d9b0da2ed23d8146d02 cryptsetup-luks-1.0.3-8.el5.src.rpm -- Karanbir Singh CentOS Project { http://www.centos.org/ } irc: z00dax, #centos at irc.freenode.net

...heezy/sid, too. --- appliance/packagelist.in | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/appliance/packagelist.in b/appliance/packagelist.in index b26ef23..4830962 100644 --- a/appliance/packagelist.in +++ b/appliance/packagelist.in @@ -23,7 +23,6 @@ btrfs-progs cryptsetup cryptsetup-luks /* old name used before Fedora 17 */ - diffutils e2fsprogs /* e4fsprogs only exists on RHEL 5, will be ignored everywhere else. */ e4fsprogs @@ -51,7 +50,6 @@ bsdmainutils btrfs-tools cryptsetup - diff e2fsprogs gfs-tools gfs2-tools @@ -77,7 +75,6 @@...

Upgraded a RAID. Copied everything from backup. And then my manager said I had to encrypt the drive. I've done that, and made the filesystem, but I can't mount it. CentOS 6. I have the entry in /etc/crypttab, and a key in /etc/crypt.pw, and the luks UUID in /etc/fstab. I cannot find the command that tells it to create the device in /dev/mapper from the info in /etc/crypttab. Clues for

Original version linked from here: https://bugzilla.redhat.com/show_bug.cgi?id=1808977#c8 There is no change in the code in this series, but feedback from the original series was we shouldn't lose the error message in patch 7. When I tested this just now in fact we don't lose the error if debugging is enabled, but I have updated the commit message to note what the error message is in the

Hi everyone, I added a page under the HowTos for Encryption, and then added a guide for encrypting /tmp /swap and /home using cryptsetup and LUKS keys on LVM, when you already have partitions setup. http://wiki.centos.org/HowTos/EncryptTmpSwapHome Regards, Max

...1808977#c8 The original feedback was that ignoring errors from guestfs_luks_uuid would ignore legitimate errors from non-BitLocker disks, so I have modified this series so that errors are only ignored in the BitLocker case. As noted in the 4th patch there is no actual error in the BitLocker case, cryptsetup luksUUID simply exits without printing anything. Rich.

...ios-sparc (>= 1.0+svn1018) but 1.0+svn640-1 is installed. My first question is, is this normal? Do I need the qemu and qemu-system packages installed? What about these openbios dependencies? The next problem I have encountered: When I installed libguestfs-tools, aptitude also installed the cryptsetup ( cryptsetup/squeeze uptodate 2:1.1.3-4squeeze2 ) package as a dependency. Since then, every time I run update-initramfs, I get this: # update-initramfs -u update-initramfs: Generating /boot/initrd.img-2.6.32-5-amd64 cryptsetup: WARNING: failed to detect canonical device of /dev/md1 cryptsetup:...

On Tue, Oct 06, 2020 at 03:25:20PM +0200, Martin Kletzander wrote: > On Mon, Sep 07, 2020 at 10:41:20AM +0100, Richard W.M. Jones wrote: > >For BitLocker disks cryptsetup does not (yet? ever?) support reading > >UUIDs and this function will fail. This does not matter here so just > >ignore the error. > > > >Note there is no error message, cryptsetup simply returns with a bad > >exit code: > > > >><rescue> cryptsetu...