How to Install and Uninstall bilibop-lockfs Package on Kali Linux

Last updated: May 17,2024

1. Install "bilibop-lockfs" package

Please follow the step by step instructions below to install bilibop-lockfs on Kali Linux


    
        
            $
        

        
            
                sudo apt update
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo apt install
            
                        
                bilibop-lockfs
            
                    
    
    Copied

2. Uninstall "bilibop-lockfs" package

Please follow the guidelines below to uninstall bilibop-lockfs on Kali Linux:


    
        
            $
        

        
            
                sudo apt remove
            
                        
                bilibop-lockfs
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo apt autoclean && sudo apt autoremove
            
                    
    
    Copied

3. Information about the bilibop-lockfs package on Kali Linux

Package: bilibop-lockfs
Source: bilibop (0.6.3)
Version: 0.6.3+b1
Installed-Size: 128
Maintainer: Yann Amar
Architecture: amd64
Depends: bilibop-common (= 0.6.3+b1), initramfs-tools, udev (>= 242-6)
Recommends: cryptsetup
Suggests: aufs-dkms, bilibop-device-policy, gnome-icon-theme, libnotify-bin, plymouth
Size: 37672
SHA256: 9b2634c9fde5a2da33116cdd4ac0b188b3d99c818d758e66f2b2d6a4996a6710
SHA1: a0ca86aca3e03f45a8e4f0456f5e085d28fceaa9
MD5sum: 15146b7624af6842cbb046fd9dce33d0
Description: 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:
Homepage: https://un.poivron.org/~quidame/wiki/bilibop
Tag: admin::boot, admin::filesystem, implemented-in::shell, role::plugin,
role::program, suite::debian
Section: admin
Priority: optional
Filename: pool/main/b/bilibop/bilibop-lockfs_0.6.3+b1_amd64.deb