Puppy Linux Discussion Forum

[technosaurus]

For security, if you add that to a daemonized script, you may want to set MYPASS="" immediately after you are finished with it.

[starhawk]

BTW, I'm of the opinion that few puppy users (if any) really need an encrypted savefile.

Then again, I have nothing worth stealing, only partially on purpose.

Not to say, Jan99, that you shouldn't have one, just, I'm a little surprised when I come across someone who thinks it's necessary.

Only two people I can think of who really need it are Julian Assange (does he even use Puppy?) and that one dude that really doesn't like John Murga for some weird reason that I never fully understood.

[jpeps]

[goingnuts]

maddox: You need to escape the spaces:

[greengeek]

[goingnuts]

Also adie from the FOX-lib - although quite big for a static build - seems to work.
For syntax highlight you need to place the Adie.stx file in same directory as you have installed adie and after that define the colors via Options/Preferences/styles

[postfs1]

[Jan99]

I am not an expert in this either (in fact more like a beginner )!

Managed to append some script lines to the mount script.
Now mount is reacting more as in other pups when it comes to encryption=
With a bonus that when I don't provide a mount-point it will do a fsck.

Unfortunatuly when unmounting the loop device is not freed and I do not know how to do it in a script (yet).
Manual free after unmount with losetup -d /dev/loop* works ok.

The lines I appended are:
if [ "$2" == "encryption=aes" ] || [ "$2" == "encryption=blowfish" ] || [ "$2" == "encryption=1" ] ; then
if [ "$2" == "encryption=aes" ] ; then
encryption=aes
else
if [ "$2" == "encryption=blowfish" ] ; then
encryption=blowfish
else
if [ "$2" == "encryption=1" ] ; then
encryption=1
fi
fi
fi

freeloop=$(/sbin/losetup -f)
losetup -e $encryption "${freeloop}" $3
if [ "$4" == "" ] ; then
fsck ${freeloop}
losetup -d ${freeloop}
exit
else
mount-FULL ${freeloop} $4
exit
fi
fi

[technosaurus]

For future reference, here is a way to simplify that kind of code:

[goingnuts]

Attached static builds of shutterbug (screen shot utility) and PathFinder (file manager) both from FOXlib 1.6.47. Although quite big they also seems quite feature rich and stable.

[Ibidem]

[Jan99]

pUPnGO busybox = V1.17.0
Original pup 412 busybox = V1.8.2 (clears loop device on unmount )
Have used busybox from pup412 in pUPnGO and then the loop device get cleared (just to test).

So i think it is a compile option of busybox (probably the encryption= too).

Thank you technosaurus that is simplifying a lot have changed code to:
case "$2" in
encryption=*)eval $2
freeloop=$(/sbin/losetup -f)
losetup -e $encryption "${freeloop}" $3
if [ "$4" == "" ] ; then
fsck ${freeloop}
losetup -d ${freeloop}
exit
else
mount-FULL ${freeloop} $4
exit
fi
::
esac

[goingnuts]

Ibidem: libstdc++ - but I will try your suggestion using uclibc++ - thanks! Update: Actually seems that the binary gets slightly (14K) bigger with uclibc++ at least in my trials. Guess the big size of FOX-lib compiled static bins are mostly because FOX uses the X-lib extensively (?). Anyway - this can be reduced by combining the different applications in a multicall binary - which on the other hand needs a bunch of patching...
Jan99: I will look at the busybox compile...Update: I cant find any busybox configure flags that will turn on/of the clearing of loop device on unmount - so sort of stuck here...

Attached a draft for a gtkdialog1 GUI for creating and mounting aes-crypted files - sort of poor mans TrueCrypt...

[goingnuts]

I have been revisiting the build of busybox as the question arise if the umount of loop devises could auto delete the used /dev/loop. This remains unsorted but another thing popped up that I will report for future reference. I have used the same busybox source for pupngo through all the versions and the last rebuild was in June 2012. Since then I have changed my uclibc toolchain but the new builds of busybox uses the same source and the same .config file...

But now I have a problem with the xterm-wrapper script which wont launch rxvt. The original part that fail is

[greengeek]

Hi goingnuts - I am trying to work around a display problem I get when I use qtweb browser, and I think it has something to do with fonts and/or encoding so I was hoping you might have a suggestion:

The worst part of the symptom goes away when I remove the file /usr/share/fonts/default/TTF/h.pcf.gz but I don't know why. Do you have any idea what that file does? (seems odd to have a gz file in there, but it definitely has some effect on how the characters display...)

Symptoms as follows:
When I sign in to my webmail I see large crosses that obscure some areas. It seems to be some characters that may have different encoding (like ' apostrophes) and also characters that are "hidden" (like password entry fields). You can see this effect in pic 1.

Pic2 shows the effect after I remove the h.pcf.gz file. The crosses have been replaced by a less intrusive character. (but still doesn't show the ' character correctly). At least it's much more readable this way till I work out how to add the correct encoding or font.

Can you think of any downside of me leaving out that file permanently?