Convert pupsave to encrypted pupsave?

[vtpup]

This is probably completely obvious or covered a hundred times already, but is there a simple way to convert an unencrypted savefile to an encrypted savefile? (Bionicpup64)

[bigpup]

This is kind of old, but I guess it should still work.
Converting nonencrypted pupsave to encrypted pupsave
http://www.murga-linux.com/puppy/viewtopic.php?t=50747

[vtpup]

Thanks Bigpup, but it doesn't work. A few reasons.... it wants to modprobe old aes modules not present, it overfills /tmp, and unfortunately, it also turns out I have a save folder, not a savefile.

I guess if I used Bcrypt in Bionicpup64 (under pfix=ram) I could encrypt the existing savefolder. But I'm wondering how I could get Puppy to ask for the pasword key on start-up.

Does puppy know that it's an encrypted savefile if the name of the savefile has a specific name tag, like "crypt" or "luks" in it, and then it handles the password query?

That's what I'm guessing happens.....

[bigpup]

it also turns out I have a save folder, not a savefile.

That is the problem. It was made for save files.

Save folder is a completely different thing.

I have no idea about encrypting a save folder.

Watch your words.
the general word pupsave could be a save file or a save folder.
Completely different saves.

[bigpup]

I guess you could make a test save folder and try your idea.

[vtpup]

Hmm, not having much luck here.

LottsaLuks program will encrypt a partition or a whole disk, or will create a new encrypted savefile, but will not encrypt an exisring a folder or a savefile

Bcrypt on Puppy <Menu> <Personal> will encrypt a file, but not a folder. It might work, I suppose on a pupsavefile, but not a pupsave folder.

It's surprising to me that no one else has ever wanted to encrypt a savefile (or folder) after having created an unencrypted version.

Also, it would be nice to have a tool (if it doesn't already exist) for converting from a savefile to a save folder, and vice versa.

We're sometimes asked when setting up a puppy to make major and irrevocable decisions we later find we'd like to change, once we have more experience.

I actually hadn't intended to make a save folder for my present setup, but hadn't realized such things existed, and misunderstood the setup wizard as asking if I wanted to save a savefile in a particular subfolder. In fact I operated for quite awhile before looking carefully at what I thought was my savefile, and finally realizing what I had!

[vtpup]

If I mounted a new encrypted savefile and also my existing savefolder (while running a pfix-ram Puppy) would I need to use sfs tools to copy the contents from the existing savefolder to the encrypted savefolder? Or could I just mount both and do the copies, and then un-mount?

[vtpup]

Well that worked slick as a whistle.

1.) Ran Puppy pfix=ram
2.) Did a Properties on my existing save folder -- it was 2439 megs.
3.) Closed Puppy, and it asked if I wanted a savefile. Yes, encrypted, 4 gigs (must be larger than save folder was). Set a password.
4.) Rebooted pfix=ram
5.) Opened the save folder. Then mounted the encrypted savefile, using password.
6.) Select all, deleted everything in the encrypted savefile.
7.) Select all, copied everything in the savefolder to the encrypted savefile.
8.) Unmount the encrypted savefile by clicking on it.
9.) Move savefolder to a deeper subdirectory, so it won't get found during next boot.
10.) Move new encrypted savefolder into the puppy directory, where the savefolder used to be.
11.) Reboot normally. Now with an encrypted savefile.

Everything is exactly as it was -- even rxvt history (uparrow) is what I was doing just before last shutdown. I'm writing this using the new encrypted savefolder version.

And of course, you could go the other way as well -- unencrypt, or convert from a savefile to savefolder, or both.