@hackage hackage-security0.5.3.0
Hackage security library
Categories
License
BSD-3-Clause
Maintainer
cabal-devel@haskell.org
Links
Versions
Installation
Dependencies (23)
- Cabal >=1.14 && <3.2
- base >=4.5 && <4.13
- base16-bytestring >=0.1.1 && <0.2
- base64-bytestring >=1.0 && <1.1
- bytestring >=0.9 && <0.11
- containers >=0.4 && <0.7 Show all…
Dependents (7)
@hackage/hackage-security-HTTP, @hackage/hackage-repo-tool, @hackage/stack, @hackage/cabal-file, @hackage/cabal-install, @hackage/pantry-tmp, Show all…
Package Flags
base48
(on by default)
Are we using base 4.8 or later?
use-network-uri
(on by default)
Are we using network-uri?
old-directory
(off by default)
Use directory < 1.2 and old-time
The hackage security library provides both server and client utilities for securing the Hackage package server (http://hackage.haskell.org/). It is based on The Update Framework (http://theupdateframework.com/), a set of recommendations developed by security researchers at various universities in the US as well as developers on the Tor project (https://www.torproject.org/).
The current implementation supports only index signing, thereby enabling untrusted mirrors. It does not yet provide facilities for author package signing.
The library has two main entry points:
Hackage.Security.Client is the main entry point for
clients (the typical example being cabal), and
Hackage.Security.Server is the main entry point for
servers (the typical example being hackage-server).