dadc7eb329
Whenever we create scripts that are installed to $out, we must use runtimeShell in order to get the shell that can be executed on the machine we create the package for. This is relevant for cross-compiling. The only use case for stdenv.shell are scripts that are executed as part of the build system. Usages in checkPhase are borderline however to decrease the likelyhood of people copying the wrong examples, I decided to use runtimeShell as well.
39 lines
1.3 KiB
Nix
39 lines
1.3 KiB
Nix
{ stdenv, fetchurl, jre, runtimeShell }:
|
|
|
|
let
|
|
version = "1.7.23";
|
|
jar = fetchurl {
|
|
name = "burpsuite.jar";
|
|
url = "https://portswigger.net/Burp/Releases/Download?productId=100&version=${version}&type=Jar";
|
|
sha256 = "1y83qisn9pkn88vphpli7h8nacv8jv3sq0h04zbri25nfkgvl4an";
|
|
};
|
|
launcher = ''
|
|
#!${runtimeShell}
|
|
exec ${jre}/bin/java -jar ${jar} "$@"
|
|
'';
|
|
in stdenv.mkDerivation {
|
|
name = "burpsuite-${version}";
|
|
buildCommand = ''
|
|
mkdir -p $out/bin
|
|
echo "${launcher}" > $out/bin/burpsuite
|
|
chmod +x $out/bin/burpsuite
|
|
'';
|
|
|
|
preferLocalBuild = true;
|
|
|
|
meta = {
|
|
description = "An integrated platform for performing security testing of web applications";
|
|
longDescription = ''
|
|
Burp Suite is an integrated platform for performing security testing of web applications.
|
|
Its various tools work seamlessly together to support the entire testing process, from
|
|
initial mapping and analysis of an application's attack surface, through to finding and
|
|
exploiting security vulnerabilities.
|
|
'';
|
|
homepage = https://portswigger.net/burp/;
|
|
downloadPage = "https://portswigger.net/burp/freedownload";
|
|
license = [ stdenv.lib.licenses.unfree ];
|
|
platforms = jre.meta.platforms;
|
|
hydraPlatforms = [];
|
|
maintainers = [ stdenv.lib.maintainers.bennofs ];
|
|
};
|
|
}
|