Find the answer to your Linux question:
Results 1 to 3 of 3
I've had this happen before: an encrypted volume will unencrypt with losetup and mount fine on the system it was encrypted on, but not another bailing with "must specify file ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Aug 2010
    Posts
    31

    unencrypting on a different system fails


    I've had this happen before: an encrypted volume will unencrypt with losetup and mount fine on the system it was encrypted on, but not another bailing with "must specify file system type" ( usually meaning a bad password, but not the case here ).

    the first time this happened was after a large system update, and I was able to chroot from a previous system backup and successfully unencrypt. now I am in the same predicament but have no previous system backup to chroot into.

    I've got the encrypted medium (a file) and the correct password and I know the encryption method, but cant unencrypt. so what can I do? whats the issue here?

  2. #2
    Just Joined!
    Join Date
    Aug 2010
    Posts
    31
    heres an interesting bit. with the wrong password I always get this:
    Code:
    mount -oencryption=aes file /mnt/tmp
    Password: 
    mount: you must specify the filesystem type
    but with the correct password, it does this instead:
    Code:
    mount -oencryption=aes file /mnt/tmp
    Password: 
    mount: wrong fs type, bad option, bad superblock on /dev/loop1,
           missing codepage or helper program, or other error
           In some cases useful info is found in syslog - try
           dmesg | tail  or so
    and this is what dmesg has to say:
    Code:
    init_special_inode: bogus i_mode (166236) for inode loop0:8
    EXT3-fs (loop0): error: invalid journal inode
    there are text files on the encrypted medium which would show by doign a `cat /dev/loop0 | strings -n 10` but it shows nothing intelligible. the unencryption is just plain not working like it should...
    Last edited by zeroth; 07-22-2011 at 03:20 PM.

  3. #3
    Just Joined!
    Join Date
    Aug 2010
    Posts
    31
    another interesting bit, after losetup'ing to loop0 with correct password:

    Code:
    cat /dev/loop0 > tst
    file tst
    tst: Linux rev 1.0 ext3 filesystem data, UUID=d0830430-7237-4dcd-8b68-c9e35c46916d

  4. $spacer_open
    $spacer_close

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •