nixpkgs/pkgs/servers/nosql/cassandra/2.1.nix

{ callPackage, ... } @ args:

callPackage ./generic.nix (args // {
  version = "2.1.22";
  sha256 = "1wk57dz0kmc6d5y8d8dkx269lzh3ark3751z734gxncwdlclcyz3";
  generation = "2_1";
  extraMeta.knownVulnerabilities = [
    # Fixed in 3.* but 2.* hasn't been released since
    "CVE-2020-17516"
  ];
})
cassandra: refactor versioning This change: - refactors the packages so it is easier to create and update new versions of cassandra. - fixes a bug where Cassandra will not connect to another member unless LD_PRELOADing libstdc++.so. Without that change, it generates a stack trace and dies with exceptions regarding org.xerial.snappy. - restricts platform to linux as procps is also linux only. 2016-07-22 21:34:43 +02:00			`{ callPackage, ... } @ args:`
Add cassandra 2.0 According to the project website (http://cassandra.apache.org) version 2.0 is the most stable version. It's the one that's recommended if you are already in production or going into production soon. Cassandra 2.0 is also the version that's officially supported by Titan (http://thinkaurelius.github.io/titan), a distributed graph database that uses cassandra as one of it's backends. 2015-02-24 16:57:39 +01:00
cassandra: refactor versioning This change: - refactors the packages so it is easier to create and update new versions of cassandra. - fixes a bug where Cassandra will not connect to another member unless LD_PRELOADing libstdc++.so. Without that change, it generates a stack trace and dies with exceptions regarding org.xerial.snappy. - restricts platform to linux as procps is also linux only. 2016-07-22 21:34:43 +02:00			`callPackage ./generic.nix (args // {`
cassandra_2_1: 2.1.20 -> 2.1.22 Reason: Fixes CVE-2020-13946 Apache Cassandra RMI Rebind Vulnerability Description: It is possible for a local attacker without access to the Apache Cassandra process or configuration files to manipulate the RMI registry to perform a man-in-the-middle attack and capture user names and passwords used to access the JMX interface. The attacker can then use these credentials to access the JMX interface and perform unauthorised operations. Users should also be aware of CVE-2019-2684, a JRE vulnerability that enables this issue to be exploited remotely. 2.1.x users should upgrade to 2.1.22 2020-11-25 02:42:29 +01:00			`version = "2.1.22";`
			`sha256 = "1wk57dz0kmc6d5y8d8dkx269lzh3ark3751z734gxncwdlclcyz3";`
cassandra: Add passthru.tests 2020-12-09 13:01:56 +01:00			`generation = "2_1";`
cassandra_2*: mark as insecure 2021-02-18 11:44:25 +01:00			`extraMeta.knownVulnerabilities = [`
			`# Fixed in 3.* but 2.* hasn't been released since`
			`"CVE-2020-17516"`
			`];`
cassandra: refactor versioning This change: - refactors the packages so it is easier to create and update new versions of cassandra. - fixes a bug where Cassandra will not connect to another member unless LD_PRELOADing libstdc++.so. Without that change, it generates a stack trace and dies with exceptions regarding org.xerial.snappy. - restricts platform to linux as procps is also linux only. 2016-07-22 21:34:43 +02:00			`})`