repo: move packages under their SBo category

Mirror SBo's own <category>/<package>/ layout instead of a flat
<package>/ one. The category is now carried by the directory, so
there's no separate map to maintain, and a package exports to the SBo
repo at the identical relative path.

misc:    SecLists, exploitdb, nuclei
games:   UrbanTerror
network: feroxbuster, ffuf, gobuster, metasploit-framework-bin, r8125

Categories taken from the synced SBo tree, which is authoritative.

This also repairs two things the flat layout had broken:

- test-build's category_of() returned "." for every package, since it
  derives the category from the parent directory name.
- post-commit asserted a fixed depth. It now locates a build by the
  directory holding the .SlackBuild, and names the archive after the
  package with the package dir at the tarball root, as SBo expects.

Drops the exec bit from SecLists.SlackBuild and gobuster.SlackBuild,
flagged by sbolint once the pre-commit hook started running: SBo
requires 0644 and ships both that way.

1 files changed, 18 insertions, 0 deletions

diff --git a/network/metasploit-framework-bin/README b/network/metasploit-framework-bin/README
new file mode 100644
index 0000000..fb0a25e
--- /dev/null
+++ b/network/metasploit-framework-bin/README
@@ -0,0 +1,18 @@
+Metasploit Framework
+
+The world’s most used penetration testing framework
+
+Knowledge is power, especially when it’s shared. A collaboration
+between the open source community and Rapid7, Metasploit helps
+security teams do more than just verify vulnerabilities, manage
+security assessments, and improve security awareness; 
+
+it empowers and arms defenders to always stay one step (or two)
+ahead of the game. 
+
+This is a repackage of the official nightly build of the debian
+package by Rapid7
+
+Security note: the bundled payload and exploit binaries are shipped
+executable, as Metasploit requires. They are delivery artifacts used
+against remote targets, not programs meant to be run on the host.