http://puppylinux.ca/tpp/pizzasgood/pcp ... REV1.delta - 24 MB
http://puppylinux.ca/tpp/pizzasgood/pcp ... ta.md5.txt
Like I said, just uploaded the .delta file. When I know I've fixed it I'll upload the iso and make a more formal announcement about rev1 (or 2 or whatever it takes).
To apply the .delta, use something like this:
xdelta3 -d -s oldfile oldfiletonewfile.delta newfile
specifically:
Code: Select all
xdelta3 -d -s pcpuppyos_301.iso pcpos_FINAL_to_REV1.delta pcpuppyos_301-rev1.iso
This uses the latest Pebble (which I actually forgot to release - was waiting on Dinky to test if it had solved his problems with Tigerpup, but he's been too busy with his new daughter to get back to me.)
This also uses version 0.2 of the timesync script, which uses a list of timeservers at /etc/timeservers, and will go through it until it finds one that works, then caches it at /etc/.last_good_timeserver so that it doesn't have to use trial-and-error every time.
Finally, I updated ClamAV to 0.94.1rc1, along with the virus definitions.
@technowomble: I haven't tested this version with a full install yet, due to my lack of a free partition where I could do one. Let me know if it works properly this time, and if not, post a copy of your menu.lst file and I'll see what I can do. If necessary I do have enough space to move everything off of one of the less-used partitions.
@PaulBx1: I think I found some info on what you were asking about, and from what I can tell we're already doing that.
http://en.wikipedia.org/wiki/Dm-crypt
When using the cipher block chaining mode of operation with predictable initialization vectors as other disk encryption software, the disk is vulnerable to watermarking attacks. This means that an attacker is able to detect the presence of specially crafted data on the disk. To address this problem in its predecessors, dm-crypt included provisions for more elaborate, disk encryption-specific modes of operation.[1] Support for ESSIV (encrypted salt-sector initialization vector) was introduced in Linux kernel version 2.6.10, LRW in 2.6.20 and XTS in 2.6.24. However, the CBC mode is still the default for compatibility with older volumes.
http://www.saout.de/misc/dm-crypt/
The defaults are aes with a 256 bit key, hashed using ripemd160. Since Linux 2.6.10 you can use an alternative IV scheme to prevent a watermark attack weakness. aes-cbc-essiv:sha256 should do it.
Code: Select all
# cryptsetup status save_file
/dev/mapper/save_file is active:
cipher: aes-cbc-essiv:sha256
keysize: 128 bits
device: /dev/loop2
offset: 1032 sectors
size: 152729 sectors
mode: read/write
I actually didn't specify anything besides the defaults in the script, but according to the above output we're using the ESSIV version anyways. Maybe I set that when I compiled it, or maybe they've just changed the defaults since they last updated the documentation.
[size=75]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[/size]
[img]http://www.browserloadofcoolness.com/sig.png[/img]