Tiny Core Linux
Tiny Core Extensions => TCE Q&A Forum => Topic started by: yoshi314 on January 25, 2010, 02:54:52 PM
-
i've been wondering about that for a while now; is there a package for cryptsetup + crypto kernel modules for TCL, and LVM somewhere? i can't seem to be able to find it via appbrowser.
-
We have loop-aes support in the 2.x series; cryptohome isn't supported anymore, but you can encrypt files and partitions fine.
Util-linux-ng for the user-space tools, and tripl for easier setting up if you don't wish to go manual.
Besides AES, Blowfish, Twofish, and Serpent are available in loop-aes-extra.tcz.
-
is it (loop-aes) compatible with existing encrypted partitions created with cryptsetup?
my entire hdd is encrypted, so i'd like to access it somehow from TC :]
-
I don't think so. Never used dm-crypt though, don't quote me on that.
-
all right then. i guess that means i have to build my own kernel, device-mapper, lvm and cryptsetup.
it's surprising nobody needed these so far.
-
Actually, only the lvm/dm modules are needed, if you don't want to build it all.
-
and crypto ones, too.
i'm already experimenting with replacing the kernel in TC, and it doesn't look too bad. but it throws up a lot of warnings though :]
-
sorry for double post.
it turned to be quite lucky - kernel has crypto support and i just had to install mdadm (for dm-* modules), some development packages and get lvm + crypsetup compiled. now i can access my encrypted partitions properly from TC.
i hope somebody will package those two tools, as i'm sure i'm not the only person that could use them. i might try, after i experiment with packaging in TC for a while.\
edit: it seems TC is missing ext4 support. aww crap :D
-
edit: it seems TC is missing ext4 support. aww crap Cheesy
ext4 is supported through the filesystems-2.6.29.1-tinycore extension.
-
yeah, i found it a few minutes later ;)
i'd better read up on packaging for TC tomorrow.
btw where do we report bugs with packages?
-
The tce bugs area is best.
-
I'm very interested in having LVM support in tinycore. I'm planning to use microcore as a PXE-bootable install/maintenance image. I've bundled in rsync, etc., but I still need LVM support. Please post a note on the forum if you create packages, and thanks in advance.
-
i did, but it's far from proper. but hey, at least it works (for me, that is) ;-)
http://www.4shared.com/file/210551409/68fde1d6/lvm.html
it's LVM + cryptsetup packaged together (that's what i meant by far from proper). i still have them packaged separately in .tar.gz packs if somebody needs them.
you need to create .md5.txt for it. i assume this is absolutely required by tce loader.
md5sum lvm.tcz >> lvm.tcz.md5.txt
i don't think this needs any special dependencies.
you need mdadm package because of dm* kernel modules it contains.
-
i did, but it's far from proper. but hey, at least it works (for me, that is) ;-)
http://www.4shared.com/file/210551409/68fde1d6/lvm.html
Beautiful! This works great! I've dropped your lvm.tcz into /opt/tce/optional along with:
gcc_libs.tcz
mdadm.tcz
md.tcz
openssh.tcz
openssl-0.9.8h.tcz
popt.tcz
rsync.tcz
and their respective md5 files, then created links in /opt/tce, pointing to the tcz files in "optional". I re-made the image with
find | cpio -o -H newc | gzip -2 > ../microcore-rsync.gz
and everything works! Thanks so much.
Bryan
-
cool. i remember that popt was a build dependency. i didn't expect it to be a runtime dep. or maybe i was thinking about some other package ;)
aaagh, nevermind that :]
-
The popt package is a dependency for the rsync package I included.