How to Install and Uninstall bilibop-lockfs Package on Ubuntu 20.10 (Groovy Gorilla)
Last updated: December 24,2024
1. Install "bilibop-lockfs" package
Please follow the instructions below to install bilibop-lockfs on Ubuntu 20.10 (Groovy Gorilla)
$
sudo apt update
Copied
$
sudo apt install
bilibop-lockfs
Copied
2. Uninstall "bilibop-lockfs" package
This guide let you learn how to uninstall bilibop-lockfs on Ubuntu 20.10 (Groovy Gorilla):
$
sudo apt remove
bilibop-lockfs
Copied
$
sudo apt autoclean && sudo apt autoremove
Copied
3. Information about the bilibop-lockfs package on Ubuntu 20.10 (Groovy Gorilla)
Package: bilibop-lockfs
Architecture: amd64
Version: 0.6.0
Priority: optional
Section: universe/admin
Source: bilibop
Origin: Ubuntu
Maintainer: Ubuntu Developers
Original-Maintainer: Yann Amar
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 138
Depends: bilibop-common (= 0.6.0), initramfs-tools, udev (>= 242-6)
Recommends: cryptsetup
Suggests: aufs-dkms, bilibop-device-policy, gnome-icon-theme, libnotify-bin, plymouth
Filename: pool/universe/b/bilibop/bilibop-lockfs_0.6.0_amd64.deb
Size: 35528
MD5sum: 4b55cb000f5934463f662b343be0cbc0
SHA1: ddad3cac18f971673bb113c9d033a5dbb6762d0b
SHA256: b265d56f2c75f28f4c38c4defe5add796db714b99444ff3eb79c2e561f978a3c
SHA512: 543cd2637073a3d302d9de1ebf99d77ee68f8b0573801912b3184119c8e8316a8dc23d7c9e748c119300d0eb197ebaf3ccb7fd7336405858df1e653b57e1b6ed
Homepage: https://un.poivron.org/~quidame/wiki/bilibop
Description-en: lock filesystems and write changes into RAM
Bilibop helps to maintain a Debian GNU/Linux operating system installed
on an external media (USB, FireWire, Flash memory, eSATA). It hardens
standard rules and policies to make the system more robust in this
particular situation.
.
If the lockfs feature is enabled (in a configuration file, in the boot
commandline or by a heuristic), nothing will be written on the filesystems
listed in /etc/fstab, except for those that have been whitelisted, or for
the encrypted swap devices. More, bilibop-lockfs now is able to detect if
the drive has been locked by a physical switch, and then overrides its own
settings to unconditionally apply a 'hard' policy.
.
The root filesystem is locked (set readonly, using either aufs or overlay)
by an initramfs script which also modifies the temporary fstab to prepare
other filesystems to be locked later by a mount helper script.
.
bilibop-lockfs provides the following features:
* whitelist based policy: filesystems on which you want to allow persistent
changes must be explicitly listed in a configuration file.
* swap devices policy: they can be used 'as is', noauto, only if encrypted,
only if encrypted with a random key, or not used at all.
* not only filesystems are set read-only, but also block devices: this
forbids changes of the partition table, boot sectors, LUKS headers and
LVM metadata.
* plymouth messages to know at boot time if bilibop-lockfs is enabled or
not, or if an error occurred.
* desktop notifications at startup about filesystems status, to inform the
user that volatile or persistent changes are allowed or not, and where.
.
This package can be used as an alternative to fsprotect or overlayroot,
especially for writable operating systems embedded on a USB stick; but it
may also be installed on public or personal computers, for daily use,
kiosks, testing purposes, or as a tool in anti-forensics strategies.
Description-md5: 3d0ab976669fa15081c34e0bcced86df
Architecture: amd64
Version: 0.6.0
Priority: optional
Section: universe/admin
Source: bilibop
Origin: Ubuntu
Maintainer: Ubuntu Developers
Original-Maintainer: Yann Amar
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 138
Depends: bilibop-common (= 0.6.0), initramfs-tools, udev (>= 242-6)
Recommends: cryptsetup
Suggests: aufs-dkms, bilibop-device-policy, gnome-icon-theme, libnotify-bin, plymouth
Filename: pool/universe/b/bilibop/bilibop-lockfs_0.6.0_amd64.deb
Size: 35528
MD5sum: 4b55cb000f5934463f662b343be0cbc0
SHA1: ddad3cac18f971673bb113c9d033a5dbb6762d0b
SHA256: b265d56f2c75f28f4c38c4defe5add796db714b99444ff3eb79c2e561f978a3c
SHA512: 543cd2637073a3d302d9de1ebf99d77ee68f8b0573801912b3184119c8e8316a8dc23d7c9e748c119300d0eb197ebaf3ccb7fd7336405858df1e653b57e1b6ed
Homepage: https://un.poivron.org/~quidame/wiki/bilibop
Description-en: lock filesystems and write changes into RAM
Bilibop helps to maintain a Debian GNU/Linux operating system installed
on an external media (USB, FireWire, Flash memory, eSATA). It hardens
standard rules and policies to make the system more robust in this
particular situation.
.
If the lockfs feature is enabled (in a configuration file, in the boot
commandline or by a heuristic), nothing will be written on the filesystems
listed in /etc/fstab, except for those that have been whitelisted, or for
the encrypted swap devices. More, bilibop-lockfs now is able to detect if
the drive has been locked by a physical switch, and then overrides its own
settings to unconditionally apply a 'hard' policy.
.
The root filesystem is locked (set readonly, using either aufs or overlay)
by an initramfs script which also modifies the temporary fstab to prepare
other filesystems to be locked later by a mount helper script.
.
bilibop-lockfs provides the following features:
* whitelist based policy: filesystems on which you want to allow persistent
changes must be explicitly listed in a configuration file.
* swap devices policy: they can be used 'as is', noauto, only if encrypted,
only if encrypted with a random key, or not used at all.
* not only filesystems are set read-only, but also block devices: this
forbids changes of the partition table, boot sectors, LUKS headers and
LVM metadata.
* plymouth messages to know at boot time if bilibop-lockfs is enabled or
not, or if an error occurred.
* desktop notifications at startup about filesystems status, to inform the
user that volatile or persistent changes are allowed or not, and where.
.
This package can be used as an alternative to fsprotect or overlayroot,
especially for writable operating systems embedded on a USB stick; but it
may also be installed on public or personal computers, for daily use,
kiosks, testing purposes, or as a tool in anti-forensics strategies.
Description-md5: 3d0ab976669fa15081c34e0bcced86df