How to Install and Uninstall dislocker.x86_64 Package on CentOS 8 / RHEL 8

Last updated: May 17,2024

1. Install "dislocker.x86_64" package

This guide let you learn how to install dislocker.x86_64 on CentOS 8 / RHEL 8


    
        
            $
        

        
            
                sudo dnf update
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf install
            
                        
                dislocker.x86_64
            
                    
    
    Copied

2. Uninstall "dislocker.x86_64" package

In this section, we are going to explain the necessary steps to uninstall dislocker.x86_64 on CentOS 8 / RHEL 8:


    
        
            $
        

        
            
                sudo dnf remove
            
                        
                dislocker.x86_64
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf autoremove
            
                    
    
    Copied

3. Information about the dislocker.x86_64 package on CentOS 8 / RHEL 8

Last metadata expiration check: 1 day, 4:13:54 ago on Sun May 9 13:03:46 2021.
Available Packages
Name : dislocker
Version : 0.7.3
Release : 1.el8
Architecture : x86_64
Size : 27 k
Source : dislocker-0.7.3-1.el8.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.