How to Install and Uninstall python-flask-kvsession-doc Package on Kali Linux

Last updated: January 11,2025

1. Install "python-flask-kvsession-doc" package

In this section, we are going to explain the necessary steps to install python-flask-kvsession-doc on Kali Linux


    
        
            $
        

        
            
                sudo apt update
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo apt install
            
                        
                python-flask-kvsession-doc
            
                    
    
    Copied

2. Uninstall "python-flask-kvsession-doc" package

Please follow the steps below to uninstall python-flask-kvsession-doc on Kali Linux:


    
        
            $
        

        
            
                sudo apt remove
            
                        
                python-flask-kvsession-doc
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo apt autoclean && sudo apt autoremove
            
                    
    
    Copied

3. Information about the python-flask-kvsession-doc package on Kali Linux

Package: python-flask-kvsession-doc
Source: flask-kvsession
Version: 0.6.4-0kali1
Architecture: all
Maintainer: Kali Developers
Installed-Size: 119
Depends: libjs-sphinxdoc (>= 4.3)
Homepage: https://pypi.org/project/Flask-KVSession-fork
Priority: optional
Section: doc
Filename: pool/main/f/flask-kvsession/python-flask-kvsession-doc_0.6.4-0kali1_all.deb
Size: 36488
SHA256: 5538e318cf72a0da8a8007fcb262a5eb82ff5d0fc300fc36cf2a66f582706c82
SHA1: b2921371554863ee152d6ea7ad8a50312dc08d7e
MD5sum: 5483d3fe0d5ccbad79858374c705565c
Description: Flask's session handling using server-side sessions (common documentation)
This package contains server-side session replacement for Flask's signed
client-based session management. Instead of storing data on the client, only a
securely generated ID is stored on the client, while the actual session data
resides on the server.
.
This has two major advantages:
- Clients no longer see the session information
- It is possible to securely destroy sessions to protect against replay
attacks.
.
Other things are possible with server side session that are impossible with
clients side sessions, like inspecting and manipulating data in absence of the
client.
.
This is the common documentation package.
Description-md5: