Internal Error Cryptsetup Luksopen Failed
Format For Printing -XML -Clone This Bug -Last Comment First Last Prev Next This bug is not in your last search results. Bug577614 - pmount is not able to mount a LUKS encrypted partition Summary: pmount is not able to mount a LUKS encrypted partition Status: CLOSED ERRATA Aliases: None Product: Fedora Classification: Fedora Component: pmount (Show other bugs) Sub Component: --- Version: 12 Hardware: All Linux Priority low Severity medium TargetMilestone: --- TargetRelease: --- Assigned To: Jan Zeleny QA Contact: Fedora Extras Quality Assurance Docs Contact: URL: Whiteboard: Keywords: Depends On: Blocks: Show dependency tree /graph Reported: 2010-03-28 06:22 EDT by Karel Piwko Modified: 2010-06-22 13:18 EDT (History) CC List: 11 users (show) agk dwysocha jpmahowald jzeleny lvm-team mbroz opensource pertusus pjones prockai whulbert See Also: Fixed In Version: pmount-0.9.22-1.fc12 Doc Type: Bug Fix Doc Text: Story Points: --- Clone Of: Environment: Last Closed: 2010-06-22 13:12:36 EDT Type: --- Regression: --- Mount Type: --- Documentation: --- CRM: Verified Versions: Category: --- oVirt Team: --- RHEL 7.3 requirements from Atomic Host: Cloudforms Team: --- Attachments (Terms of Use) Add an attachment (proposed patch, testcase, etc.) Groups: None (edit) Description Karel Piwko 2010-03-28 06:22:03 EDT Description of problem: pmount is not able to mount a partition encrypted by LUKS. It fails before it asks for a password with following message. "Internal error: cryptsetup luksOpen failed" Version-Release number of selected component (if applicable): pmount.0.9.20-1.fc12.x86_64 cryptsetup-luks-1.1.0-0.4.fc12.x86_64 How reproducible: Always. Steps to Reproduce: 1. Plug in a removable device foo_dev with LUKS encrypted partition 2. Execute pmount /dev/foo_dev Actual results: pmount fails with an error message. Expected results: pount asks for password key and, if successfully unlocked, the partition is mounted in /media/foo directory Additional info: This is related to libgcrypt and libcap libraries, precisely holding of UID and EID. See explanation at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=552273. Workaround already exists in pmount Git repository and binary compiled from there works just fine. Comment 1 Jan Zeleny 2010-03-29 04:51:03 EDT Could you please execute pmount with option -d to enable debug messages? I have an idea what's going on, but I need some more information. C
parpagnas Member Registered: 2013-05-15 Posts: 17 [SOLVED] Impossible to crypt the drive using cryptsetup Hello,I have boot my computer on archiso in order to install arch's latest build on it. I have chosen to use GPT instead of MBR and i want to encrypt the hard drive before installing arch on it. I have been followinf this tuto and others but i've never manged to crypt my partition:$ sudo cryptsetup -c aes-xts-plain -y -s 512 -r luksFormat /dev/sda2 --debug # cryptsetup 1.6.1 processing "cryptsetup -c aes-xts-plain -y -s 512 -r luksFormat /dev/sda2 --debug" # Running command luksFormat. # Locking https://bugzilla.redhat.com/show_bug.cgi?id=577614 memory. # Installing SIGINT/SIGTERM handler. # Unblocking interruption on signal. WARNING! ======== This will overwrite data on /dev/sda2 irrevocably. Are you sure? (Type uppercase yes): YES # Allocating crypt device /dev/sda2 context. # Trying to open and read device /dev/sda2. # Initialising device-mapper backend library. # Timeout set to 0 miliseconds. # Iteration time set to 1000 miliseconds. # Interactive passphrase entry requested. Enter passphrase: Verify https://bbs.archlinux.org/viewtopic.php?id=164071 passphrase: # Formatting device /dev/sda2 as type LUKS1. # Crypto backend (gcrypt 1.5.2) initialized. # Topology: IO (512/0), offset = 0; Required alignment is 1048576 bytes. # Generating LUKS header version 1 using hash sha1, aes, xts-plain, MK 64 bytes # Crypto backend (gcrypt 1.5.2) initialized. # KDF pbkdf2, hash sha1: 349525 iterations per second. # Data offset 4096, UUID 99256e6c-34b6-4775-b945-5c7082c44c6b, digest iterations 42625 # Updating LUKS header of size 1024 on device /dev/sda2 # Key length 64, device size 97265664 sectors, header size 4036 sectors. # Reading LUKS header of size 1024 from device /dev/sda2 # Key length 64, device size 97265664 sectors, header size 4036 sectors. # Adding new keyslot -1 using volume key. # Calculating data for key slot 0 # Crypto backend (gcrypt 1.5.2) initialized. # KDF pbkdf2, hash sha1: 351399 iterations per second. # Key slot 0 use 171581 password iterations. # Using hash sha1 for AF in key slot 0, 4000 stripes # Updating key slot 0 [0x1000] area. # Calculated device size is 500 sectors (RW), offset 8. # dm version OF [16384] (*1) # dm versions OF [16384] (*1) # Device-mapper backend running with UDEV s
från GoogleLogga inDolda fältSök efter grupper eller meddelanden
get pre-encrypted HDD with cryptsetup to work on OpenWRT Pages 1 You must login or register to post a reply RSS topic feed Posts: 4 1 Topic by molocho 2015-01-22 13:30:36 molocho Member Offline Registered: 2015-01-22 Posts: 1 Topic: Cannot get pre-encrypted HDD with cryptsetup to work on OpenWRT Hey folks,first i would like to share my basic idea. I have a synology from where i would like to make scheduled backups via ssh-rsync to an external USB-HDD, hooked up to another linux device. As there are other people who have physical access to the HDD, the data must be saved in an encrypted state. Basically i want to grab my USB-HDD in case of emergency and take it to any linux machine available to restore/rescue data. So far i have been doing the backup to the HDD plugged onto a raspberry pi b+, which worked out pretty well - the data is now stored on the external drive. Now i would like dump the Raspi and hook the USB-HDD to my OpenWRT router. (TP-Link WDR4300) I found out to forget about DD-WRT, which i have been using so far, if i want to get cryptsetup to run on it.Now the main problem is the installation of this previously encrypted and written USB-HDD with cryptsetup onto the OpenWRT. I googled for days and cannot get my problem resolved on Barrier Breaker 14.07.Using cryptsetup on the Raspi, that USB-HDD with data on it worked like a charm. I have exported the cryptkey from there to a file, of course i know my passwords. Accessing the encrypted Data on this USB drive hooked up to another linux device worked so far after doing these steps:installing cryptsetupinstall USB-HDD drive supportcheck with "fdisk -l" for /dev/sda1 to see that the USB-HDD is therecopy cryptkey to /root/key.sda1 via SCP to the device where USB-HDD is plugged in"chmod 400 /root/key.sda1" (for security reasons)"cryptsetup luksAddKey /dev/sda1 /root/key.sda1" <-- this is where i cannot get further on OpenWRT "cryptsetup luksUUID /dev/sda1""cryptsetup luksOpen /dev/sda1 sda1""mkdir /mnt_sda1""mount /dev/mapper/sda1 /mnt_sda1"as mentioned above on the following commandline i get multiple errors aka"device-mapper: remove ioctl on temporary-cryptsetup-XXXX failed: No such device or address"where XXXX seems to be the current process ID.i've been following a trail where the file "/dev/mapper/control" might be