aboutsummaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)AuthorFilesLines
18 hoursmetasploit-framework-bin: update to 6.5.9HEADmasterDanilo M.3-7/+7
18 hoursSecLists: update to 2026.2Danilo M.2-4/+4
18 hoursexploitdb: update to 2026_10_27Danilo M.2-4/+4
11 daysAGENTS.md: record exploitdb noarch/ELF false positiveDanilo M.1-0/+7
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
11 daysexploitdb: update to 2026_10_23Danilo M.2-4/+4
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-02exploitdb: fix README and .info formatting drift from SBoDanilo M.2-2/+2
Drop the trailing blank line from README and split DOWNLOAD back onto two lines, matching the published SBo copy. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-02exploitdb: update to 2026_10_02Danilo M.2-4/+4
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-25cadaver: add version 0.28Danilo M.6-0/+156
Adopted from SBo, where the build was orphaned at 0.23.3. Moved here from Slackware-Pentesting-Suite. Uses the upstream release tarball, which ships a generated configure and the neon macros, so the build no longer clones neon from git or runs autogen.sh. CFLAGS now reach configure. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-25AGENTS.md: keep symlink cleanup out of .gitDanilo M.1-1/+1
The git hooks are now installed as symlinks in .git/hooks, so the documented `find . -type l -delete` removed them along with the sbodl source symlinks. Exclude .git from the cleanup. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-25AGENTS.md: point agents at the maintainer workspaceDanilo M.1-0/+5
Agent tools that stop at the nearest AGENTS.md would otherwise never see the operational workflow (hooks, sweep, test builds, SBo delivery) that now lives in the parent workspace. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-25Move maintainer tooling out of the repoDanilo M.5-372/+48
Git hooks, the upstream sweep and the SBo delivery workflow are the maintainer's operational tools, not package knowledge. They now live in a private workspace that wraps all three SlackBuild repos, with one shared copy of each hook instead of three drifting ones. Also in this pass: - AGENTS.md: checksum loop documented as sbodl (sbofixinfo does not fix checksums), nvchecker must not run without a token config, prefer use_latest_release over use_max_tag - README: Git Hooks section replaced by a short Contributing note - sweep report renamed to LAST_SWEEP.md across all three repos Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-23docs: add r8125 build notes and clean-sweep recording stepDanilo M.1-0/+44
Fold the r8125 maintainer notes into AGENTS.md rather than a file beside the package: the post-commit hook tars every file under a package dir into the SBo submission archive, so notes kept there would ship upstream. The r8125 section covers what the SlackBuild alone does not explain: the KERNEL= and PRINT_PACKAGE_NAME=1 overrides, the @KERNEL@ placeholder check, and the full reason ENABLE_DASH_SUPPORT=n is load-bearing. Upstream's Makefile defaults DASH on and appends -DENABLE_DASH_SUPPORT via EXTRA_CFLAGS +=, but the SlackBuild passes EXTRA_CFLAGS on the make command line, which overrides instead of appending; the define is lost while r8125_dash.o is still built, and it fails against a struct with members ifdef'd out. Dropping the flag on a version bump reintroduces the failure. Also record that Realtek edits a listing's description in place without re-rolling the tarball, so a changed blurb is not a release. Verified this session: the 9.018.00 description now reads "kernel up to 7.1" while Version, UpdateTime and MD5 are all unchanged. The nvchecker clean-sweep paragraph was already staged in the working tree from an earlier session and is included here. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-14docs: note SBo PR bodies should be -stable-onlyDanilo M.1-0/+3
2026-09-14docs: update exploitdb row with published SBo versionDanilo M.1-1/+1
2026-09-14python3-telethon: update to 1.45.0Danilo M.2-4/+4
2026-09-14ffuf: update to 2.3.0Danilo M.2-4/+4
2026-09-14exploitdb: update to 2026_09_12Danilo M.2-4/+4
2026-09-07docs: refresh package table with published SBo versionsDanilo M.1-3/+3
exploitdb 2026_07_09 -> 2026_08_19, metasploit-framework-bin 6.4.144 -> 6.5.3, nuclei 3.11.0 -> 3.11.1. Verified against the upstream 15.0 and master branches, which agree on all ten packages. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011EurHqRGprQisEWJQP4tLz
2026-09-07exploitdb: update to 2026_09_04Danilo M.2-4/+4
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011EurHqRGprQisEWJQP4tLz
2026-08-21Added python3-telethonDanilo M.6-0/+168
2026-08-19exploitdb: update to 2026_08_19Danilo M.2-4/+4
2026-08-19metasploit-framework-bin: update to 6.5.3Danilo M.3-7/+7
2026-08-13exploitdb: update to 2026_08_12Danilo M.2-4/+4
2026-08-09docs: rename CLAUDE.md to AGENTS.md and update referencesDanilo M.5-491/+493
2026-08-09nuclei: update to 3.11.1Danilo M.2-4/+4
2026-08-09metasploit-framework-bin: update to 6.5.2Danilo M.2-6/+6
2026-08-08CLAUDE.md: document fork setup, file modes, symlink cleanupDanilo M.1-2/+46
Three things a future session would otherwise have to rediscover: - How to recreate the fork clone. Its path was recorded but not the setup, and .git/config isn't tracked, so a re-clone silently loses user.name=danix and commits revert to the global name. Adds the three identity conditions and how to verify them on a live PR. - The 0644 requirement, and that git tracks the exec bit, which is how SecLists and gobuster carried 0755 until sbolint started running. Includes the fix and a repo-wide audit command. - Symlink cleanup now says to run it from the repo root; the old note predates the category layout, where a package-dir-relative find misses other categories.
2026-08-08CLAUDE.md: document the GitHub PR delivery channelDanilo M.1-0/+71
SBo accepts updates to published packages as pull requests (SBo-Github-Workflows.txt). Record that alongside the existing submission-tarball route, plus the facts that took checking: - The fork is a separate clone at ~/Programming/GIT/GITHUB/slackbuilds, never a remote of this repo; the histories are unrelated. - PRs are based on master. Merged PRs display a base of "github", a transient integration branch admins retarget onto and delete, so it is not a branch to target. - The exported commit is synthesized at export time and uses SBo's wording, so local history here stays independent and keeps its own format.
2026-08-08repo: move packages under their SBo categoryDanilo M.62-8/+30
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.
2026-08-08hooks: fix pre-commit sbolint never runningDanilo M.1-1/+16
The sbolint loop extracted build dirs with "cut -d/ -f1,2", which is correct for SBo's own <category>/<package>/ layout but yields a file path in this repo's flat <package>/ layout (e.g. nuclei/nuclei.info). The guard then tested nuclei/nuclei.info/slack-desc, which never exists, so sbolint was silently skipped on every package commit. Walk up from each changed file to the directory holding the .SlackBuild instead. Depth is no longer assumed, so this works for the current flat layout and for <category>/<package>/ after the planned migration.
2026-08-07CLAUDE.md: fix msf completion regen, gem paths are mandatoryDanilo M.1-6/+29
The extract-to-tmp generator command as documented never worked on its own. The embedded ruby has /opt/metasploit-framework baked in as its prefix, so bundler resolves gems there regardless of the extract dir and fails with Bundler::GemNotFound. It only appeared to work when a host install sat at that path, which also meant it read the installed version rather than the one being packaged. Add the required GEM_HOME/GEM_PATH/BUNDLE_GEMFILE, note that the ruby version in the gem path moves on upstream bumps, and drop the advice to fall back to a live /opt install. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-07metasploit-framework-bin: update to 6.5.1Danilo M.3-7/+7
Regenerated msfvenom.bash-completion against the 6.5.1 framework. Man pages checked against kali, unchanged. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-07-30CLAUDE.md: prefer extract-to-tmp over host install for msf artifact regenDanilo M.1-9/+19
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-30metasploit-framework-bin: update to 6.4.147Danilo M.3-7/+7
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-16nvchecker: use_latest_release for SecLists and ffufDanilo M.1-2/+2
Both cut GitHub Releases; use the lenient releases/latest endpoint instead of the rate-limited git/refs/tags one. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-16README: complete package table with all 10 packagesDanilo M.1-1/+8
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-16gitignore: ignore local-only LAST_SWEEP sweep reportDanilo M.1-0/+1
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-14extract docker tooling to ../sbo-dockerbuildDanilo M.16-5116/+23
The test-build tool and image-builder chain grew from a .extras/ helper into a standalone toolchain, now maintained in its own repo (../sbo-dockerbuild). Remove them here (scripts, examples, design docs) and repoint CLAUDE.md: test-building is now done with the installed `test-build` CLI, deps resolved from the SBo tree, both trees verified per bump. Package-maintenance files stay: nvchecker.toml, hooks/, assets/. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-14metasploit-framework-bin: update to 6.4.144Danilo M.3-8/+8
Refresh msfvenom.bash-completion against the installed 6.4.144 framework. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-14exploitdb: update to 2026-07-09Danilo M.2-4/+4
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-14nuclei: update to 3.11.0Danilo M.2-4/+4
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-14ffuf: update to 2.2.1Danilo M.2-4/+4
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-14test-build: add --keep to save the built target packageDanilo M.1-0/+14
Binary-repack packages (metasploit-framework-bin) need a post-install step on the host: install the package, then regenerate artifacts that require a live install (msfvenom bash-completion, man pages). This repo is deliberately outside the buildsystem workflow, so producing that package meant a manual root build here. --keep instead copies the built target .txz out to <data>/kept/ (path printed) so it can be installed on the host directly from a normal test run. The build is otherwise throwaway; deps are unaffected. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-14test-build: variant-namespace the dep cache and prune stale digestsDanilo M.2-3/+32
The dep cache was keyed on image digest alone, so a nightly image rebuild orphaned the old digest's cache dir forever (disk creep). Namespace it as <variant>-<digest> and, on each run, prune superseded digests of the SAME variant. Scoping to the variant means a --current run does not wipe the 15.0 cache, so testing both trees back-to-back still reuses built deps (e.g. google-go-lang). Correctness was already fine (digest self-invalidates); this just stops the accumulation, matching sbo-batch-test's invalidate-on-base-update. Add three prune self-checks. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-14image-builder: catch build/push failures, prune cache on --forceDanilo M.3-7/+44
The main loop runs build_variant in an `if ! (...)` condition, which suppresses set -e inside the subshell, so a failed docker build fell through to push a nonexistent tag and log "Done" (seen live: a transient containerd export lock reported success). Add explicit exit checks on docker build and docker push in all three scripts; return non-zero so the variant is marked failed. Also prune the build cache before a --force full-image build: --force already implies --no-cache, so the stale cache is dead weight that still loads the snapshotter's lock bookkeeping and has raced the layer export. Best-effort, never fails the build. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-14test-build: target the local SlackBuild (CWD/path), deps from the treeDanilo M.2-3/+56
The tool resolved the target package from the SBo tree, so it tested the already-published version, not the local edit under test. Useless for the maintenance workflow, where the point is to verify an edited SlackBuild while its deps come from the tree. resolve_target_dir now takes the target from where you are: - a path (absolute, ./x, or containing /): that dir - a bare name: ./<name>/ under CWD, else CWD itself if it IS <name>/ Repo-agnostic; deps still resolve from the configured SBo tree via find_slackbuild_dir. Add four target-resolution self-checks. Also source /etc/profile.d/*.sh in the build container before running the SlackBuild: the heredoc is a non-login shell, so a bare `go build` picked the system gccgo 1.18 instead of the installed google-go-lang; sourcing profile.d activates dep-provided env (GOROOT/PATH, cargo, ...) as a real login build would. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-14image-builder: cron moved to 03:00/05:00 (trees now sync 01:00/02:00)Danilo M.1-14/+15
Tree syncs moved earlier (01:00, 02:00), so the image chain runs earlier too and both variants are ready well before the ~09:00 work start: -current 03:00/03:20/04:30 (ready ~04:35), 15.0 05:00/05:20/06:30 (ready ~06:35). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-14image-builder: cron gates both variants, add 15.0, drop --forceDanilo M.1-5/+13
All three scripts self-gate (ChangeLog hash, base digest, full digest + .txz hash), so --force was forcing needless full rebuilds. Drop it: unchanged nights are now cheap no-ops. Add the 15.0 variant (09:00/09:20/11:00), which on frozen stable rebuilds only when the 15.0 repo actually changes. -current stays at 06:00/06:20/08:00. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-14image-builder: README cron matches deployed 06:00/06:20/08:00 scheduleDanilo M.1-4/+6
The nightly chain on docker.noland.dnx runs after the NAS repo syncs (04:00, 05:00): bootstrap 06:00, full-image 06:20 (~55 min), testbuild 08:00. Also add the --version current --force flags the deployed crontab actually uses. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-07-14test-build: auto-pull the image from the LAN registry when missingDanilo M.1-10/+16
require_image now docker-pulls ACTIVE_IMAGE (a fully-qualified registry ref) if it is not already local, instead of erroring out and telling the user to pull by hand. Only errors if the pull itself fails. Pull-if-missing only: a stale local tag is not refreshed (noted for a future --pull flag). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>