How to Install and Uninstall bilibop-lockfs Package on Ubuntu 16.04 LTS (Xenial Xerus)

Last updated: November 26,2024

1. Install "bilibop-lockfs" package

This tutorial shows how to install bilibop-lockfs on Ubuntu 16.04 LTS (Xenial Xerus)


    
        
            $
        

        
            
                sudo apt update
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo apt install
            
                        
                bilibop-lockfs
            
                    
    
    Copied

2. Uninstall "bilibop-lockfs" package

This guide covers the steps necessary to uninstall bilibop-lockfs on Ubuntu 16.04 LTS (Xenial Xerus):


    
        
            $
        

        
            
                sudo apt remove
            
                        
                bilibop-lockfs
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo apt autoclean && sudo apt autoremove
            
                    
    
    Copied

3. Information about the bilibop-lockfs package on Ubuntu 16.04 LTS (Xenial Xerus)

Package: bilibop-lockfs
Priority: optional
Section: universe/admin
Installed-Size: 137
Maintainer: Ubuntu Developers
Original-Maintainer: Yann Amar
Architecture: amd64
Source: bilibop
Version: 0.5.0
Depends: bilibop-common (= 0.5.0), initramfs-tools, initscripts (>= 2.88dsf-13.3)
Recommends: cryptsetup
Suggests: bilibop-device-policy, gnome-icon-theme, libnotify-bin, plymouth
Filename: pool/universe/b/bilibop/bilibop-lockfs_0.5.0_amd64.deb
Size: 34948
MD5sum: 2f231f3c76b2a50f7561b01f67074f7f
SHA1: 248a2211850bc2e63fbb202ffc1aa043af3b4f41
SHA256: c9a95752952f8a0546378847438fe30c41264056b37c96b90edbac05346316c8
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 occured.
* 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.
.
Some features may require Linux kernel 2.6.37 or higher to work properly.
Description-md5: 229e6e1129a070af2e81ea21ca78b10f
Homepage: https://un.poivron.org/~quidame/wiki/bilibop
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Origin: Ubuntu