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

Last updated: November 25,2024

1. Install "medusa.x86_64" package

Please follow the guidance below to install medusa.x86_64 on Red Hat Enterprise Linux 8 (RHEL 8)


    
        
            $
        

        
            
                sudo dnf update
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf install
            
                        
                medusa.x86_64
            
                    
    
    Copied

2. Uninstall "medusa.x86_64" package

Please follow the steps below to uninstall medusa.x86_64 on Red Hat Enterprise Linux 8 (RHEL 8):


    
        
            $
        

        
            
                sudo dnf remove
            
                        
                medusa.x86_64
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo dnf autoremove
            
                    
    
    Copied

3. Information about the medusa.x86_64 package on Red Hat Enterprise Linux 8 (RHEL 8)

Last metadata expiration check: 1:13:04 ago on Mon Feb 26 15:59:38 2024.
Available Packages
Name : medusa
Version : 2.2
Release : 15.20181216git292193b.el8
Architecture : x86_64
Size : 226 k
Source : medusa-2.2-15.20181216git292193b.el8.src.rpm
Repository : epel
Summary : Parallel brute forcing password cracker
URL : http://www.foofus.net/jmk/medusa/medusa.html
License : GPLv2
Description : Medusa is a speedy, massively parallel, modular,
: login brute-forcer for network services.
: Some of the key features of Medusa are:
:
: * Thread-based parallel testing. Brute-force
: testing can be performed against multiple hosts,
: users or passwords concurrently.
: * Flexible user input. Target information
: (host/user/password) can be specified in a variety of ways.
: For example, each item can be either a single
: entry or a file containing multiple entries.
: Additionally, a combination file format allows
: the user to refine their target listing.
: * Modular design. Each service module exists
: as an independent .mod file.
: This means that no modifications are necessary
: to the core application in order to extend
: the supported list of services for brute-forcing.