How to Install and Uninstall ghc-cipher-aes Package on openSUSE Leap

Last updated: February 28,2025

1. Install "ghc-cipher-aes" package

Learn how to install ghc-cipher-aes on openSUSE Leap


    
        
            $
        

        
            
                sudo zypper refresh
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo zypper install
            
                        
                ghc-cipher-aes
            
                    
    
    Copied

2. Uninstall "ghc-cipher-aes" package

Please follow the step by step instructions below to uninstall ghc-cipher-aes on openSUSE Leap:


    
        
            $
        

        
            
                sudo zypper remove
            
                        
                ghc-cipher-aes
            
                    
    
    Copied

3. Information about the ghc-cipher-aes package on openSUSE Leap

Information for package ghc-cipher-aes:
---------------------------------------
Repository : Main Repository
Name : ghc-cipher-aes
Version : 0.2.11-bp155.2.14
Arch : x86_64
Vendor : openSUSE
Installed Size : 162.2 KiB
Installed : No
Status : not installed
Source package : ghc-cipher-aes-0.2.11-bp155.2.14.src
Upstream URL : https://hackage.haskell.org/package/cipher-aes
Summary : Fast AES cipher implementation with advanced mode of operations
Description :
Fast AES cipher implementation with advanced mode of operations.
The modes of operations available are ECB (Electronic code book), CBC (Cipher
block chaining), CTR (Counter), XTS (XEX with ciphertext stealing), GCM (Galois
Counter Mode).
The AES implementation uses AES-NI when available (on x86 and x86-64
architecture), but fallback gracefully to a software C implementation.
The software implementation uses S-Boxes, which might suffer for cache timing
issues. However do notes that most other known software implementations,
including very popular one (openssl, gnutls) also uses similar implementation.
If it matters for your case, you should make sure you have AES-NI available, or
you'll need to use a different implementation.