similar to: FYI: cryptsetup luksOpen now requires loads of RAM

Leon Fauster wrote: >> Am 20.06.2017 um 16:53 schrieb m.roth at 5-cent.us: >> >> 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

> Am 20.06.2017 um 17:12 schrieb m.roth at 5-cent.us: > > Leon Fauster wrote: >>> Am 20.06.2017 um 16:53 schrieb m.roth at 5-cent.us: >>> >>> 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

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

> Am 20.06.2017 um 16:53 schrieb m.roth at 5-cent.us: > > 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

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

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

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

CentOS 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

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

In keeping with our general aim to consolidate libvirt project infrastructure services on GitLab, we now wish to have issues for upstream libvirt projects reported on the appropriate https://gitlab.com/libvirt/ repository issue tracker. For further details see: https://libvirt.org/bugs.html Bugs against OS distro provided binary packages should continue to be filed against the OS distros'

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:

This is about Network-Bound Disk Encryption (NBDE) not to be confused of course with NBD! NBDE is where you use disk encryption in your virtual machines. But instead of having to type a passphrase when the guest boots, there is a network server which gives out tokens, so as long as the guest is booted from the trusted network it is able to boot unattended. In RHEL[1] we have three pieces of

On 04/03/15 06:33 PM, Robert Nichols wrote: > On 03/04/2015 03:16 PM, Digimer wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Hi all, >> >> I created a LUKS encrypted partition via a udev-triggered script on >> 6.6 using --key-file /tmp/foo. This worked fine, and I can decrypt the >> LUKS partition via script and manually using

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

Since we're no longer only inspecting LUKS devices, use a more generic name. This rewrite also makes the function clearer. --- options/decrypt.c | 34 +++++++++++++++------------------- 1 file changed, 15 insertions(+), 19 deletions(-) diff --git a/options/decrypt.c b/options/decrypt.c index d868f70..58f8df9 100644 --- a/options/decrypt.c +++ b/options/decrypt.c @@ -28,6 +28,7 @@ #include

Is there an easy way (cli) to enable a luks encrypted partition after reboot (a partition that was not enabled while booting, because not in the crypttab). I can execute the necessary command stack [1] but just wondering if there is an "enterprise/easy" way to do that ... [1] cryptsetup luksOpen $(blkid -t TYPE="crypto_LUKS" -o device) \ luks-$(cryptsetup luksUUID

On Fri, Oct 09, 2020 at 04:33:53PM +0100, Richard W.M. Jones wrote: >On Fri, Oct 09, 2020 at 05:02:57PM +0200, Martin Kletzander wrote: >> Basically what I did was create a small disk, create one partition >> over the whole disk, then cryptsetup luksFormat the partition, open >> it and format it with a filesystem (without any LVM). That is one >> of the things you were

On Thu, Mar 5, 2015 at 10:25 PM, Tim <lists at kiuni.de> wrote: > Hi Chris, > > thanks for your answer. > > It is the first time I decided to encrypt my lvm. I choosed to encrypt the > volume group, not every logical volume itself, because in case of doing lvm > snapshots in that group they will be encrypted too? Yes, anything that's COW'd is also encrypted in

On Tue, Jan 21, 2020 at 03:07:11PM +0100, Jan Synacek wrote: > The following patch attempts to implement sparsification of > LUKS-encrypted partitions. It uses lsblk to pair the underlying LUKS > block device with its mapped name. Also, --allow-discards was added > by default to luks_open(). > > There are several potential issues that I can think of: > > 1) If and entire

Hi, http://mcgrewsecurity.com/projects/msramdmp a com32 for dumping RAM... Tru