How to Install and Uninstall ghc-http-client-restricted Package on openSUSE Leap
Last updated: November 08,2024
1. Install "ghc-http-client-restricted" package
Here is a brief guide to show you how to install ghc-http-client-restricted on openSUSE Leap
$
sudo zypper refresh
Copied
$
sudo zypper install
ghc-http-client-restricted
Copied
2. Uninstall "ghc-http-client-restricted" package
Please follow the instructions below to uninstall ghc-http-client-restricted on openSUSE Leap:
$
sudo zypper remove
ghc-http-client-restricted
Copied
3. Information about the ghc-http-client-restricted package on openSUSE Leap
Information for package ghc-http-client-restricted:
---------------------------------------------------
Repository : Main Repository
Name : ghc-http-client-restricted
Version : 0.0.5-bp155.2.15
Arch : x86_64
Vendor : openSUSE
Installed Size : 82.3 KiB
Installed : No
Status : not installed
Source package : ghc-http-client-restricted-0.0.5-bp155.2.15.src
Upstream URL : https://hackage.haskell.org/package/http-client-restricted
Summary : Restricting the servers that http-client will use
Description :
Addition to the http-client and http-client-tls libraries, that restricts the
HTTP servers that can be used.
This is useful when a security policy needs to eg, prevent connections to HTTP
servers on localhost or a local network, or only allow connections to a
specific HTTP server.
It handles restricting redirects as well as the initial HTTP connection, and it
also guards against DNS poisoning attacks.
---------------------------------------------------
Repository : Main Repository
Name : ghc-http-client-restricted
Version : 0.0.5-bp155.2.15
Arch : x86_64
Vendor : openSUSE
Installed Size : 82.3 KiB
Installed : No
Status : not installed
Source package : ghc-http-client-restricted-0.0.5-bp155.2.15.src
Upstream URL : https://hackage.haskell.org/package/http-client-restricted
Summary : Restricting the servers that http-client will use
Description :
Addition to the http-client and http-client-tls libraries, that restricts the
HTTP servers that can be used.
This is useful when a security policy needs to eg, prevent connections to HTTP
servers on localhost or a local network, or only allow connections to a
specific HTTP server.
It handles restricting redirects as well as the initial HTTP connection, and it
also guards against DNS poisoning attacks.