Puppy Linux Discussion Forum

[Gn2]

[PaulBx1]

John, you might be interested in this code fragment in that tutorial I last mentioned, the one that seems most relevant to the Puppy boot process:

[John Doe]

Thanks for the links Gn2. There was some really good info in there.

[John Doe]

[PaulBx1]

So John, where does that statement come from? Can it be dismantled and simplified to the point it starts working again?

What is "TESTPARTS"? I want to try that statement at the command line.

[mlamelas]

Hi everyone,

Will this process for encrypting the pup_save work for 2.15? I assume the initrd is different for each version, or no? How about the encryption script?

Many thanks,

Mel

[RobertB]

[Pizzasgood]

You can add it by hand, 2.15 just doesn't include it by default like it was originally going to. Just follow the same procedure you'd use for 2.14.

[mlamelas]

Hi Pizzasgood and other posters,

Thanks for your help. I am a relatively new comer to Puppy and Linux in general. When you say add encryption by hand to 2.15, what are the steps? Is there a library that needs to be added, or some source code that needs to be compiled, and if so, which?

There is another thread about compiling truecrypt where I have posted a question, but let me ask a question here since it may relate to encryption in general.

I followed the instructions in the other thread for compiling truecrypt, using Puppy 2.15 and Truecrypt 4.3. I got an error message about inserting the dm and truecrypt modules when I tried to mount a tc volume.

Another user who was successful in compiling Truecrypt 4.2a under Puppy 2.12 uploaded the four ko files from his compile. I copied them to the appropriate folders in 2.15, did a depmod -a, and truecrypt was able to mount a volume. With a glitch because the names show up in 8.3 format, but it did work.

My question then is whether the inability to compile Truecrypt 4.3 under Puppy 2.15 is related to the version of Truecrypt (4.3 v. 4.2a), or to the fact that encryption was taken out of Puppy2.15? Would taking out whatever was taken out of Puppy 2.15 affect the ability to compile Truecrypt?

Many thanks,

Mel

[kirk]

The 2.14 encryption stuff is here:

http://www.puppyos.net/forum/?1172086471

It uses cryptoloop with AES 128 for encryption. TrueCrypt would be a whole other adventure.

Or just wait for 2.16, It won't be long.

[mlamelas]

Hi Kirk,

Thanks for the info. I downloaded the initrd.gz file and copied it to my drive, replacing the default initrd.gz file that came with 2.15, but the system would not boot. It said that it could not find puppy in idehd and dropped to the shell. If I rename the pup_215.sfs to pup_214.sfs then it loads fine, but then you end up with a version conflict with the rest of the sfs files (zdrv, web_215).

I will wait for 2.16, but if encrypting the pupsave file is going to require a different initrd.gz file than the default, someone would have to create one for each new version of puppy. That may not be an optimal solution.

With respect to truecrypt, it has been compiled successfully with versions prior to 2.15, so I am wondering whether part of the kernel code that deals with encryption that was removed in 2.15 is creating my problem with the compile.

For now, I am using the ko files from the prior version compiles and that works. As long as the module doesn't change from 2.6.18.1 that will probably solve my problem with truecrypt.

For now, I will create a truecrypt volume inside of puppy for my stored passwords files, and as a second layer set up some kind of log in process to protect against loss or theft of the puppy pen drive.

Best regards,

Mel

[kirk]

[mlamelas]

I was hoping that was the answer. I have downloaded the 2.16 beta.