@hackage hackage-security0.6.3.2
Hackage security library
Categories
License
BSD-3-Clause
Maintainer
cabal-devel@haskell.org
Links
Versions
Installation
Tested Compilers
Dependencies (23)
- Cabal >=2.2.0.1 && <2.6 || >=3.0 && <3.7
- Cabal-syntax <3.7
- base >=4.11
- base16-bytestring >=0.1.1 && <1.1
- base64-bytestring >=1.0 && <1.3
- bytestring >=0.10.8.2 && <0.13 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
cabal-syntax
(off by default)
Are we using Cabal-syntax?
lukko
(off by default)
Use lukko for file-locking, otherwise use GHC.IO.Handle.Lock
The hackage security library provides both server and client utilities for securing the Hackage package server (https://hackage.haskell.org/). It is based on The Update Framework (https://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).