Great work Kirk....check with WhoDo so he can *hopefully* incorporate this into the Puppy 2.15 CE "Viz" edition. I've always been of the opinion that this should be a standard feature or option in the base release._________________Jam

I've tried puppy linux at the encouragement of my brother previously but I couldn't get wifi to work. The last time, it was better but I had just gone up to WPA from WEP and that wasn't there. So I hadn't used it to speak of.
I downloaded 2.14, burned an iso to a CD-RW and started up again. I had a little trouble with the WPA, it wasn't clear to me what numbers I really should be using for password and whatnot, that's not a fault of they puppy system but a lot of stuff you get with SBC Yahoo is "idiot proofed" and you don't really need to know much. But I looked it up.
When you're trying to get the WPA window up it's a little non-intuitive. You have to poke around a bit to get the right sequence of things. I lucked out the first time (beginners luck). It was working fine and that proved it COULD be done. That was helpful because I messed up and thought I could get the CD-RW to load the "change file" when I powered down but that's a no-no I found out.
Anyhow, I had to start over when I powered up and that time I had a bit more trouble with the auto help wizard thing. Having had it work once though kept me going 'cause I knew it could be done!
Turns out you really really need to use the scan thing. But it's a little tricky to select WPA then scan just right before it'll even see a WPA wifi node. Once it does, then just enter the key and you're there.
I'm using an ACER laptop with 802.11g. It's a Travelmate with a Pentium M and CD burner/DVD reader combo.

Great work Kirk....check with WhoDo so he can *hopefully* incorporate this into the Puppy 2.15 CE "Viz" edition. I've always been of the opinion that this should be a standard feature or option in the base release.

I second that._________________Life is too short to spend it in front of a computer

I think It should probably be in the base distro too. It's quite small and offers security for usb flash and for multiple users on the same computer.

Ok, I've got most of the bugs sorted in Beta1 and I'm ready to try something new for Puppy 2.15CE Beta2. Save file encryption is an obvious feature choice and I'd like to include it. Can you let me know what I need to do to the next unleashed build of the 2.15 initrd.gz file to have encryption installed? Thanks, kirk.

I've uploaded my save-file-wizard also WhoDo. Just so you know. When you get encryption sorted, let me know if it has any errors and I'll take a gander.
http://www.murga-linux.com/puppy/viewtopic.php?t=16249

But for now I'd better go test my homework before I leave for the weekend (I wrote and tested it in Puppy with g++, but it will be graded with Visual Studio, so I have to make sure that works too).

As for adding encryption, the basic run-down is edit /sbin/init with a couple lines, and add the aes and cryptoloop modules, which these guys can explain. Also nice is the option to encrypt the file when you first create it. I'll be working on that next week as I port Pizzapup to 2.14. I'd just give you the scripts I used with 2.12, but Puppy's shutdown has changed since then (for the better)._________________Between depriving a man of one hour from his life and depriving him of his life there exists only a difference of degree. --Muad'Dib

Ok, I've got most of the bugs sorted in Beta1 and I'm ready to try something new for Puppy 2.15CE Beta2. Save file encryption is an obvious feature choice and I'd like to include it. Can you let me know what I need to do to the next unleashed build of the 2.15 initrd.gz file to have encryption installed?

I've posted the details here:

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

That's for a modified 2.14 initrd.gz. I've noticed that fsck is now taking up more than half of my boot time. Fsck takes me about 30sec with 512MB save file that has 93MB free in it. Right now the encryption mod is using ext2 like the rest of puppy. I'm thinking we should go back to ext3, or at least make it an option. I never had a problem with ext3 on the loopback device.

I posted the fsck time problem on the other forum, Barry has changed init script to fsck only if it's ext2. Barry seems to always be working on the init script. Might want to see if we can use his current working version.

If you need more info or you've got another init script and you want me to apply these changes to it, let me know.

I’m having difficulty using your app to encrypt my pup_save file. I follow the directions and all seems to go well and the new pup_save_crypt file is created. On reboot I have the option to select the new pup_save_crypt.2fs file but then I get the following error:

You've gotta edit initrd.gz. That means using isomaster to edit the iso before burning it to a cd, or else replacing the initrd.gz file on the usb-drive. I think the instructions said about it.

Gotta go sleep now. Sorry for no details, but already past bed-time._________________Between depriving a man of one hour from his life and depriving him of his life there exists only a difference of degree. --Muad'Dib

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum