summaryrefslogtreecommitdiff
path: root/pkgs/development/libraries/nettle/generic.nix
blob: b626e137c42723a18a08958b05a6a6733050eec0 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
{
  lib,
  stdenv,
  buildPackages,
  gmp,
  gnum4,

  # Version specific args
  version,
  src,
}:

stdenv.mkDerivation {
  pname = "nettle";

  inherit version src;

  outputs = [
    "out"
    "dev"
  ];
  outputBin = "dev";

  depsBuildBuild = [ buildPackages.stdenv.cc ];
  nativeBuildInputs = [ gnum4 ];
  propagatedBuildInputs = [ gmp ];

  configureFlags =
    # runtime selection of HW-accelerated code; it's default since 3.7
    [ "--enable-fat" ]
    # Make sure the right <gmp.h> is found, and not the incompatible
    # /usr/include/mp.h from OpenSolaris.  See
    # <https://lists.gnu.org/archive/html/hydra-users/2012-08/msg00000.html>
    # for details.
    ++ lib.optional stdenv.hostPlatform.isSunOS "--with-include-path=${gmp.dev}/include";

  doCheck = (stdenv.hostPlatform.system != "i686-cygwin" && !stdenv.hostPlatform.isDarwin);

  enableParallelBuilding = true;

  patches = lib.optional (stdenv.hostPlatform.system == "i686-cygwin") ./cygwin.patch;

  meta = {
    description = "Cryptographic library";

    longDescription = ''
      Nettle is a cryptographic library that is designed to fit
      easily in more or less any context: In crypto toolkits for
      object-oriented languages (C++, Python, Pike, ...), in
      applications like LSH or GNUPG, or even in kernel space.  In
      most contexts, you need more than the basic cryptographic
      algorithms, you also need some way to keep track of available
      algorithms, their properties and variants.  You often have
      some algorithm selection process, often dictated by a protocol
      you want to implement.

      And as the requirements of applications differ in subtle and
      not so subtle ways, an API that fits one application well can
      be a pain to use in a different context.  And that is why
      there are so many different cryptographic libraries around.

      Nettle tries to avoid this problem by doing one thing, the
      low-level crypto stuff, and providing a simple but general
      interface to it.  In particular, Nettle doesn't do algorithm
      selection.  It doesn't do memory allocation. It doesn't do any
      I/O.
    '';

    license = lib.licenses.gpl2Plus;

    homepage = "https://www.lysator.liu.se/~nisse/nettle/";

    platforms = lib.platforms.all;
    maintainers = [ lib.maintainers.vcunat ];
    identifiers.cpeParts = lib.meta.cpeFullVersionWithVendor "nettle_project" version;
  };
}