Slackware64-current: Creation of LUKS encrypted partition segfaults
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Slackware64 14.2 and current, SlackwareARM current
Posts: 1,645
Rep:
Slackware64-current: Creation of LUKS encrypted partition segfaults
Hi,
has anyone successfully created a LUKS partition with cryptsetup on Slackware64-current?
Doing this when booting from the CD*, I just get a segfault. Before that, cryptsetup asks the same questions as usual, asks for uppercase YES to confirm the creation, but then stops. Opening an existing LUKS encrypted partitions works though.
* I created a miniiso disc with Eric's script from the Slackware64-current tree. I don't know if this can be the source for my cryptsetup problem.
THis is a confirmed bug. It only happens with the cryptsetup's static binary (which is in the installer) and running it on x86_64 and trying to apply the luksFormat command.
Other distros suffered from the same, and all seem to have reverted to using the dynamic version of cryptsetup.
While that runs the risk of killing cryptsetup when we upgrade something like gpg libraries, the current situation sucks more because you can not create a LUKS volume in the slackware64 installer.
I guess we'll swap the static binary with the dynamically linked equivalent soon.
Any idea where the underlying problem is? Is it cryptsetup itself, one of the libraries it's linked against or a compiler/linker bug? It just seems a little strange that the bug is specific to the staticly compiled version.
THis is a confirmed bug. It only happens with the cryptsetup's static binary (which is in the installer) and running it on x86_64 and trying to apply the luksFormat command.
Eric
Don't be stupid.
This is a topic about what happens in slackware64-current as opposed to slackware-current.
If you have something constructive to say about the slackware64 issue, fine, go ahead. Otherwise, your comments are irrelevant to this discussion.
Other distros suffered from the same, and all seem to have reverted to using the dynamic version of cryptsetup.
Very polite, Eric.
I believe arny was trying to tell that not all distros using static cryptsetup suffered from that bug. I used your howto (Luks+LVM) on a BW64-12.2 box and had no problems (fresh new install)
But then, I take the opportunity to ask this: So slackware64-current has more differences from slackware-current than just the x86_64 architecture? I admit my ignorance here, because I thought slack64-current was slack-current, just recompiled to 64bits.
By the way, perhaps instead of calling people stupid, you guys could ask those who have things working about how they fixed the problems. Perhaps it could save time and sweat
Another post irrelevant to this topic. You should open a new thread if you want to have a discussion about slackware64 and the underlying philosophy for developing it the way it is now.
With the latest updates this seems not yet to be fixed. After creating a Linux partition on my external USB hard disk I do:
Code:
# cryptsetup -s 256 -y luksFormat /dev/sdd1
WARNING!
========
This will overwrite data on /dev/sdd1 irrevocably.
Are you sure? (Type uppercase yes): YES
Segmentation fault
I just post this, because this functionality is very important for me, and I hope it's not dropped as a feature for Slackware64 13.0. I do not mean to urge anyone, just want to express that I hope it's gonna be working sooner or later.
I just post this, because this functionality is very important for me, and I hope it's not dropped as a feature for Slackware64 13.0. I do not mean to urge anyone, just want to express that I hope it's gonna be working sooner or later.
Hmm I did my slackware64-current installation based on a June 23rd snapshot and I created a LUKS partition without any problems. This is on an AMD Mobile Sempron 3500+ processor btw.
Edit: I used the twofish encryption algorithm. Maybe the segfault happens with the default aes encryption only.
Hmm, I tried it several hours ago with all the latest patches applied on an external USB hard disk, and it failed. On Slackware 12.2 (32-bit) it worked just fine, as usual.
Hmm, I tried it several hours ago with all the latest patches applied on an external USB hard disk, and it failed. On Slackware 12.2 (32-bit) it worked just fine, as usual.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.