| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
See: https://bugs.busybox.net/show_bug.cgi?id=4520
|
|
|
|
|
|
The comma-separated list TYPE... specifies which types of encryption
to allow for persistent media, and whether to allow plaintext media.
The possible TYPEs are the old {none, luks}, with default "none". The
only change is that this allow plaintext and encrypted media to be
used simultaneously.
|
|
It currently only makes snapshots read-only. Support for overlays will
be a bit more complicated to implement.
|
|
Current dependencies are dm-crypt, cryptsetup and askpass.
|
|
|
|
Both overlays and snapshots are now scanned at the same time, and each
device is only mounted once. Passphrases for LUKS volumes are only
asked for once, and unused ones are closed. Also, snapshot files on
encrypted partitions are now supported.
|
|
|
|
|
|
|
|
Since this newline was written to stdout it both messed up the the
display of errors while entering a LUKS passphrase, and caused
find_cow_device to return a bad string under certain
circumstances. Example: You have home-rw on /dev/sdX1. You'll first
be asked for passphrase for "live-rw on /dev/sdX1", which you skip (a
newline has been written to stdout now). Then you're asked for
"home-rw on /dev/sdX1", which is what you want so you enter it.
Thanks to the spurious newline find_cow_device returns "\n/dev/loopY",
which breaks some tests later.
|
|
The comma-separated list METHOD... specifies which types of persistent
setups we allow. Current possible METHODs are {snapshot, overlay}. The
default value is both, i.e. persistent-method=snapshot,overlay.
|
|
These type of options has have been replaced by persistent-encryption
and persistent-storage.
|
|
The comma-separated list TYPE... specifies which types of persistent
storage to use. Current possible TYPEs are {file, filesystem}. For
instance, persistent-storage=filesystem is equivalent to the old
persistent=nofiles, but persistent-storage=file allows to look for
only files, which wasn't possible before. The default is to look for
both, i.e. persistent-storage=filesystem,file.
|
|
|
|
When specified we completely ignore unencrypted media when probing for
persistent media.
|
|
This is the way to control whether to use encrypted persistent media,
instead of the (from this commit on) obsolete persistent=cryptsetup.
|
|
Muftakhidinov <baurthefirst@gmail.com> for spotting it.
|
|
This improves support for stacked SquashFS a lot: it allows a given SquashFS to
delete files in another one it's on top of.
|
|
devices.
|
|
validateroot bootscript, stripped live systems may or may not carry /usr/share/doc.
|
|
If live-boot finds a "wrong" filesystem that looks OK, then the error message
can be pretty confusing. Panic with an explicit message in this case.
The "is this rootfs valid" test is implemented by checking if the
/usr/share/doc/live-boot/ directory exists: as per Debian Policy 2.3 (Copyright
considerations), this directory must exist on any system where the live-boot
binary package is installed.
Adapted and reformatted from a patch by Christian Hofstaedtler <ch@grml.org>.
|
|
patch by Michael Schierl <schierlm@gmx.de>.
|
|
This is e.g. needed when one's threat model does not allow her to trust the
local hard disks.
|
|
The already duplicated code will be needed a few more times for the upcoming
persistent-media={removable,removable-usb} boot option. Copy/pasting it a few
more times seems the wrong way to go, hence this factorization.
Depending on the place they are used, the newly introduced functions must return
a list of devices named either /sys/block/* or /dev/*. Their first parameter
therefore specifies the wanted output format (default is /dev/* as it is the
most often used).
|
|
This will be needed for the upcoming persistent-media={removable,removable-usb}
boot option.
|
|
for lvm and md devices.
|
|
|
|
|
|
|
|
|
|
sendsigs (Closes: #621908).
|
|
|
|
Taking care that the filesystem kernel module is loaded before issuing
the mount command.
|
|
|
|
|
|
Michael Prokop <mika@grml.org>.
|
|
|
|
|
|
|
|
consistency with live-config.
|
|
|
|
When running "mount DEV MOUNTPOINT" for the device provided by the fromiso= boot
option, Squeeze's busybox errors out with:
Mounting $DEV on /isofrom failed: No such file on directory.
Using mount -t auto fixes the bug.
|
|
E.g. prefer mounting /dev/sdb1 rather than /dev/sdb.
The isohybrid feature makes both valid devices for being searched for a live
filesystem image. Previous code mounted /dev/sdb on /live/image which makes it
hard to create a second partition on the USB stick.
This brings the need to explicitly check whether the full device is in the
blacklist before even considering its subdevices: the previous blacklist
checking code worked because the full device was always considered before its
subdevices, which is not true anymore.
|
|
|
|
Previous blacklist checking was a bit overzealous: e.g. if /dev/sdb1 was
blacklisted (e.g. because it would contain the system-wide persistence COW
device), any other device whose name contains the blacklist one, such as
/dev/sdb11, was also be blacklisted.
|
|
|
