Error decrypting LUKS partition prior to capture/imaging

[Sebastian Roth]

@george1421 Should we add this to the official FOG kernel/init? Do you know how much extra in size that is?

[george1421]

@Sebastian-Roth said in Error decrypting LUKS partition prior to capture/imaging:

Should we add this to the official FOG kernel/init?

(??)

I’m seeing this as still a one off situation. Until now I didn’t know LUKS partition encryption existed. I can say if we see more requests like this we can add it to FOS Linux. I added the patch files here so the changes don’t get lost with time.

From a size perspective the added openssl executable is minimal as well as adding in the crypto drivers into the kernel. Looking at buildroot images directory I see the uncompressed inits at 268435456 and compressed 19986704. I would have to recompile it without openssl to give you a (like for like) comparison. So the question from a developer standpoint is there any additional utility can FOG get from including the openssl executable? The openssl libraries are already included in FOS Linux for other reasons. Are we passing things between FOS and FOG today that should be protected a bit better in the future? Possibly in 1.6.x it would add some value (??)

[Sebastian Roth]

@george1421 said in Error decrypting LUKS partition prior to capture/imaging:

The openssl libraries are already included in FOS Linux for other reasons. Are we passing things between FOS and FOG today that should be protected a bit better in the future? Possibly in 1.6.x it would add some value (??)

We’ll do as soon as we see it’s needed.

[Quazz]

@george1421 I believe at one point it was suggested to use SSH to handle interactions with the server instead of ftp/nfs (one or both, don’t remember)

Though I imagine that’s further down the line.