nixpkgs/pkgs/tools/security/notary/default.nix
Maximilian Bosch 9842c4b107
treewide: update which packages I'm currently maintaining
Idea shamelessly stolen from 4e60b0efae56cc8e1a8a606a5a89462c38aba305.

I realized that I don't really know anymore where I'm listed as maintainer and what
I'm actually (co)-maintaining which means that I can't proactively take
care of packages I officially maintain.

As I don't have the time, energy and motivation to take care of stuff I
was interested in 1 or 2 years ago (or packaged for someone else in the
past), I decided that I make this explicit by removing myself from several
packages and adding myself in some other stuff I'm now interested in.

I've seen it several times now that people remove themselves from a
package without removing the package if it's unmaintained after that
which is why I figured that it's fine in my case as the affected pkgs
are rather low-prio and were pretty easy to maintain.
2019-12-26 15:27:47 +01:00

66 lines
2.2 KiB
Nix

{ stdenv, fetchFromGitHub, buildGoPackage, libtool }:
buildGoPackage rec {
pname = "notary";
version = "0.6.1";
gitcommit = "d6e1431f";
src = fetchFromGitHub {
owner = "theupdateframework";
repo = "notary";
rev = "v${version}";
sha256 = "1ak9dk6vjny5069hp3w36dbjawcnaq82l3i2qvf7mn7zfglbsnf9";
};
patches = [ ./no-git-usage.patch ];
buildInputs = [ libtool ];
buildPhase = ''
runHook preBuild
cd go/src/github.com/theupdateframework/notary
SKIPENVCHECK=1 make client GITCOMMIT=${gitcommit}
runHook postBuild
'';
goPackagePath = "github.com/theupdateframework/notary";
installPhase = ''
runHook preInstall
install -D bin/notary $bin/bin/notary
runHook postInstall
'';
#doCheck = true; # broken by tzdata: 2018g -> 2019a
checkPhase = ''
make test PKGS=github.com/theupdateframework/notary/cmd/notary
'';
meta = with stdenv.lib; {
description = "Notary is a project that allows anyone to have trust over arbitrary collections of data";
longDescription = ''
The Notary project comprises a server and a client for running and
interacting with trusted collections. See the service architecture
documentation for more information.
Notary aims to make the internet more secure by making it easy for people
to publish and verify content. We often rely on TLS to secure our
communications with a web server which is inherently flawed, as any
compromise of the server enables malicious content to be substituted for
the legitimate content.
With Notary, publishers can sign their content offline using keys kept
highly secure. Once the publisher is ready to make the content available,
they can push their signed trusted collection to a Notary Server.
Consumers, having acquired the publisher's public key through a secure
channel, can then communicate with any notary server or (insecure) mirror,
relying only on the publisher's key to determine the validity and
integrity of the received content.
'';
license = licenses.asl20;
homepage = https://github.com/theupdateframework/notary;
maintainers = with maintainers; [ vdemeester ];
platforms = platforms.unix;
};
}