How to Install and Uninstall dislocker.x86_64 Package on Red Hat Enterprise Linux 9 (RHEL 9)

Last updated: November 30,2024

1. Install "dislocker.x86_64" package

This tutorial shows how to install dislocker.x86_64 on Red Hat Enterprise Linux 9 (RHEL 9)


    
        
            $
        

        
            
                sudo dnf update
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf install
            
                        
                dislocker.x86_64
            
                    
    
    Copied

2. Uninstall "dislocker.x86_64" package

Please follow the instructions below to uninstall dislocker.x86_64 on Red Hat Enterprise Linux 9 (RHEL 9):


    
        
            $
        

        
            
                sudo dnf remove
            
                        
                dislocker.x86_64
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf autoremove
            
                    
    
    Copied

3. Information about the dislocker.x86_64 package on Red Hat Enterprise Linux 9 (RHEL 9)

Last metadata expiration check: 1:01:02 ago on Mon Feb 26 07:04:30 2024.
Available Packages
Name : dislocker
Version : 0.7.3
Release : 7.el9
Architecture : x86_64
Size : 24 k
Source : dislocker-0.7.3-7.el9.src.rpm
Repository : epel
Summary : Utility to access BitLocker encrypted volumes
URL : https://github.com/Aorimn/dislocker
License : GPLv2+
Description : Dislocker has been designed to read BitLocker encrypted partitions ("drives")
: under a Linux system. The driver has the capability to read/write partitions
: encrypted using Microsoft Windows Vista, 7, 8, 8.1 and 10 (AES-CBC, AES-XTS,
: 128 or 256 bits, with or without the Elephant diffuser, encrypted partitions);
: BitLocker-To-Go encrypted partitions (USB/FAT32 partitions).
:
: The file name where the BitLocker encrypted partition will be decrypted needs
: to be given. This may take a long time, depending on the size of the encrypted
: partition. But afterward, once the partition is decrypted, the access to the
: NTFS partition will be faster than with FUSE. Another thing to think about is
: the size of the disk (same size as the volume that is tried to be decrypted).
: Nevertheless, once the partition is decrypted, the file can be mounted as any
: NTFS partition and won't have any link to the original BitLocker partition.