Source: nbtscan Version: 1.7.2-2 Tags: patch Hi,
I was running the autopkgtest of nbtscan on a dedicated server and the relevant provider captured the scanning and was not happy. Given that the test does not actually evaluate any responses, I think it would not degrade the test in any way if it were scanning the loopback interface instead and thus avoid tripping up paranoid hosters. I'm attaching a patch for your convenience. Helmut
diff --minimal -Nru nbtscan-1.7.2/debian/changelog nbtscan-1.7.2/debian/changelog --- nbtscan-1.7.2/debian/changelog 2022-10-29 19:17:25.000000000 +0200 +++ nbtscan-1.7.2/debian/changelog 2024-05-06 11:28:15.000000000 +0200 @@ -1,3 +1,10 @@ +nbtscan (1.7.2-2.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * autopkgtest: Scan loopback rather than the internet. (Closes: #-1) + + -- Helmut Grohne <hel...@subdivi.de> Mon, 06 May 2024 11:28:15 +0200 + nbtscan (1.7.2-2) unstable; urgency=medium * debian/control: bumped Standards-Version to 4.6.1. diff --minimal -Nru nbtscan-1.7.2/debian/tests/control nbtscan-1.7.2/debian/tests/control --- nbtscan-1.7.2/debian/tests/control 2022-10-29 19:17:22.000000000 +0200 +++ nbtscan-1.7.2/debian/tests/control 2024-05-06 11:28:15.000000000 +0200 @@ -1,6 +1,6 @@ Test-Command: nbtscan | grep Usage Restrictions: superficial -Test-Command: nbtscan -v 203.0.113.0/24 +Test-Command: nbtscan -v 127.1.0.0/24 -Test-Command: nbtscan -d -b 100000 -t 2000 203.0.113.0-220 +Test-Command: nbtscan -d -b 100000 -t 2000 127.1.0.0-220
