SEARCH
0-9 A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
Prev | Current Page 248 | Next

Shon Harris, Allen Harper, Chris Eagle, and Jonathan Ness

"Gray Hat Hacking, Second Edition"

lzm /mnt/sdb1_removable/bt/modules/
We reboot again and inspect the /root directory. Strangely, test2.text is present but
test1.txt is not there. What could have gone wrong?
It turns out that the changes captured in /mnt/live/memory/changes do not
include changes made by LiveCD modules. So in the second test, the only change
detected was the addition of test2.txt. According to LiveCD, the test1.txt was there on
boot already and not registered as a change. We need some way to make the changes
from the previous change module appear as new changes. Unpacking the previous
LZM over the file system would be one way to do that and is reflected in the final set
of commands next.
echo "Preserving changes to /root and /home directories for the next boot.."
# first apply changes saved from existing change module
lzm2dir /mnt/sdb1_removable/bt/modules/zconfigs.lzm /
# next, with the previous changes applied, remove the previous change module
so mksquashfs doesn't error
rm /mnt/sdb1_removable/bt/modules/zconfigs.lzm
# these directories will probably already be there but mksquashfs will error
if they are not
touch /mnt/live/memory/changes/{home,root}
# create a new zchanges.lzm
mksquashfs /mnt/live/memory/changes/{home,root} /mnt/sdb1_removable/bt/
modules/zchanges.


Pages:
236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260