Summary: | util-linux-2.12q and USE=old-crypt causes mount failure on aes-256 loopback files | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Peter Hyman <pete4abw> |
Component: | [OLD] Core system | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED WONTFIX | ||
Severity: | major | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Peter Hyman
2005-09-26 13:49:28 UTC
you probably have to run losetup-old-crypt yourself before running mount-old-crypt those two files are built in the same way as the 2.12i ebuild, they're just renamed I was referring to an EXISTING file already created and set up. Maybe I missed something here, but anyway, I was able to extract the info by downgrading temporarily while I figure out how to do it with the new. thx so was i in order to use your existing file you're prob going to have to run `losetup-old-crypt` and then `mount-old-crypt` by hand rather than just letting `mount-old-crypt` run losetup for you stuff is my encryptied pseudo disk. I tried all these combinations. None of them worked. Where can I get more detailed information about how to make this work? Now, it's just a matter of pride :) I'm gonna get this to work! AES256 is from the manpage. aes-256 is what I used to enter on the mount line. peter@mars ~ $ sudo losetup-old-crypt -e aes256 /dev/loop0 stuff You must specify a key size (in bits) for use with CryptoAPI encryption. peter@mars ~ $ sudo losetup-old-crypt -e AES256 /dev/loop0 stuff You must specify a key size (in bits) for use with CryptoAPI encryption. peter@mars ~ $ sudo losetup-old-crypt -e AES256-256 /dev/loop0 stuff Password: Invalid cipher "AES256" Error in crypto parameters, exiting peter@mars ~ $ sudo losetup-old-crypt -e AES256 /dev/loop0 ./stuff You must specify a key size (in bits) for use with CryptoAPI encryption. peter@mars ~ $ sudo losetup-old-crypt -e AES-256 /dev/loop0 ./stuff Password: Invalid cipher "AES" Error in crypto parameters, exiting Anyway, thanks for the feedback. I really think though that there is something amiss in the old-crypto code. Maybe at some point a warning about extrating the data first should be posted. I've used cryptoloop for years and never had a problem with a util-linux upgrade before. turns out that loop and cryptoloop had to be built into kernel image. None of the processes would work if loaded with modprobe. So, for me, at least, I'm stuck with old-crypt since, for the time being, these "modules" must be built in. Took me forever to work that combination out! However, the crypto modules can be loaded on demand. Go figure! |