| Commit message (Collapse) | Author | Age |
|\
| |
| | |
wifite2: 2.5.3 -> 2.5.5
|
| | |
|
|\ \ |
|
| |\ \
| | | |
| | | | |
tunnelto: 0.1.5 -> 0.1.6
|
| | | | |
|
| | | | |
|
| |\ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
When testing WireGuard updates, I usually run the VM-tests with
different kernels to make sure we're not introducing accidental
regressions for e.g. older kernels.
I figured that we should automate this process to ensure continuously
that WireGuard works fine on several kernels.
For now I decided to test the latest LTS version (5.4) and
the latest kernel (currently 5.6). We can add more kernels in the
future, however this seems to significantly slow down evaluation and
time.
The list can be customized by running a command like this:
nix-build nixos/tests/wireguard --arg kernelVersionsToTest '["4.19"]'
The `kernelPackages` argument in the tests is null by default to make
sure that it's still possible to invoke the test-files directly. In that
case the default kernel of NixOS (currently 5.4) is used.
|
|\| | | | |
|
| |\ \ \ \
| | |_|/ /
| |/| | | |
pirate-get: 0.3.7 -> 0.4.0
|
| | | | | |
|
| | | | | |
|
| | |_|/
| |/| | |
|
|\| | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This fixes the issues with glibc 2.30, which were caused because glibc
no longer allows to dlopen/LD_PRELOAD a PIE executable.
So this release is essentially just a hotfix release which addresses
this issue by splitting the executable and library.
Signed-off-by: aszlig <aszlig@nix.build>
Reported-by: @zimbatm
|
| | | | |
|
| |/ / |
|
| |\ \
| | | |
| | | | |
amass: 3.6.1 -> 3.6.2
|
| | | | |
|
| |/ /
| | |
| | |
| | | |
Fixes #88178
|
|\| | |
|
| | |
| | |
| | |
| | | |
https://github.com/imsnif/bandwhich/releases/tag/0.15.0
|
| |\ \
| | | |
| | | | |
tendermint: 0.32.11 -> 0.32.12
|
| | | | |
|
| |\ \ \
| | | | |
| | | | | |
wireguard-go: fix executable name
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
It's supposed to be `wireguard-go` instead of `wireguard`. Upstream does
this right in their Makefile, however we use our own build-script which
creates a wrong file in $out, so it has to be fixed in the
`postInstall`-hook.
Closes #88567
|
|\| | | | |
|
| | | | | |
|
| |/ / / |
|
| |\ \ \
| | | | |
| | | | | |
croc: 8.0.9 -> 8.0.11
|
| | | | | |
|
| |\ \ \ \
| | | | | |
| | | | | | |
openvpn: update and wrap update-systemd-resolved
|
| | |/ / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The string replacement we were doing was just too brittle, so wrap the
script with a modified PATH instead as it is less likely to break on new
versions.
|
| |\ \ \ \
| | |/ / /
| |/| | | |
tridactyl-native: 1.18.1 -> 1.19.0
|
| | |/ / |
|
| |\ \ \
| | | | |
| | | | | |
pirate-get: 0.3.5 -> 0.3.7
|
| | |/ / |
|
| |\ \ \
| | | | |
| | | | | |
openconnect: 8.05 -> 8.10
|
| | |/ /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Also update vpnc script.
Fixes:
- https://nvd.nist.gov/vuln/detail/CVE-2019-16239
- https://nvd.nist.gov/vuln/detail/CVE-2020-12105
- https://nvd.nist.gov/vuln/detail/CVE-2020-12823
|
| |\ \ \
| | | | |
| | | | | |
dnsproxy: 0.27.1 -> 0.28.1
|
| | |/ / |
|
| | | |
| | | |
| | | |
| | | | |
https://lists.zx2c4.com/pipermail/wireguard/2020-May/005431.html
|
| |\ \ \
| | | | |
| | | | | |
amass: 3.6.0 -> 3.6.1
|
| | |/ / |
|
| |\ \ \
| | | | |
| | | | | |
podman packages: add passthru tests
|
| | |/ / |
|
| |/ / |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
https://www.nlnetlabs.nl/news/2020/May/19/unbound-1.10.1-released/
It fixes DoS CVEs; details e.g. on http://www.nxnsattack.com/
On each Linux platform this should be around 8k rebuilds,
so as a compromise I'm pushing to staging-next.
|
|\| | |
|
| | | |
|