knock-knock

Knock-Knock: A Live, Multi-Protocol Honeypot Dashboard of Internet Break-in Attempts - 13 Protocols, an Extensible Framework, and a Threat-Intelligence Database Serving a Public IP Blocklist Feed

Runs with mockssource: GitHubhomepagePythonMITcommit da33d6ae4a60

Python, MIT licensed. The project labels itself: blocklist, bots, cybersecurity, dashboard, docker, extensible, ftp and honeypot.

knock-knock runs, with stand-ins for the services it depends on. An Argusic agent installed it in 62 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

With a locally built Redis 7.4.1, MaxMind test GeoIP .mmdb files, and non-root high ports, monitor.py spawned all eight honeypots, uvicorn served the dashboard on :8080 (HTTP 200) with live WebSocket knocks, and the 104-test suite passed; RDP/SSH port overrides, GEOIP_DIR, and stats.py DB_DIR were fixed along the way.

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 92 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs with mocks
Argusic Score
92 / 100
cost of the verifying run
$0.29 (measured)
recorded runs
1
last tested
stars
216
forks
11
open issues
1
watchers
1
size
34 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing knock-knock, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • GeoIP database paths hard-coded to /usr/share/GeoIP, which is root-owned and unpopulated in this non-root container; monitor blocked waiting forever10 minutes
  • RDP honeypot hard-coded c_listen 3389 so ENABLED_PROTOCOLS=RDP:<port> was ignored and the spawned honeypot died (port refused)8 minutes
  • SSH honeypot ignored --port (only read SSH_PORT), so it never bound the ENABLED_PROTOCOLS port6 minutes
  • stats.py hard-coded data/knock_knock.db and crashed with 'no such table: country_intel' when DB_DIR pointed elsewhere3 minutes
  • monitor.py failed with redis ConnectionError Errno 99 connecting to localhost:6379 (IPv6-first) when only IPv4 was bound2 minutes
Install time
62 minutes
Cold machine to finish
19 minutes
Errors hit and fixed
5 hit, 5 fixed with no human help
How the result was proved
python -m pytest tests/ exited 0 with 104 passed (4 added regression tests for the port/GEOIP_DIR fixes); monitor.py spawned 8 honeypots whose ports answered; uvicorn main:app answered GET / with 200 (186421 B) and delivered new_knock messages for SSH/FTP/HTTP/SMTP/TNET/SIP over /ws; lifts confirmed in SQLite via stats.py; knock-api GET /ip/127.0.0.1 returned 200.
Model tokens used
285,315
Exact commit tested
da33d6ae4a60
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
Behaviour against real services
this run was verified against stand-in services only

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

- **SSH honeypot ignored `--port`** (only read `SSH_PORT`) — same symptom (`honeypots/ssh_honeypot_…
- **GeoIP paths hard-coded to `/usr/share/GeoIP`** in `monitor.py`, `main.py`, and `extras/api/knoc…
- **`stats.py` ignored `DB_DIR`** (crashed with `no such table: country_intel` on any non-default D…
- Minor: `localhost`→Redis failed with `Errno 99` (IPv6-first resolution against an IPv4 bind); res…
## Verified end to end
- All 8 honeypot ports OPEN after launch; the 3 latest fixes are covered by `tests/test_install_reg…
- Real credential attempts on SSH/FTP/Telnet/SMTP/HTTP/SIP/RDP/SMB → SSH rejected auth, FTP `530 Lo…
- Persisted to SQLite (`data/knock_knock.db`) with correct fields (e.g. SSH user/pass `e2euser`/`e2…
- Web: `/` → 200 (186421 B), `/summary` → 200, `/static/demo.gif` → 200; `/api` and `/blocklist` → …
- Public API: `/ip/127.0.0.1` → 200 with `listed:true, hits:10`; `/check-ranges?ranges=203.0.113.0/…
- Ban round-trip via `ip_ban.py` wrote and removed the Redis key; `node --check` passed on all thre…
**Not verified:** `restart.sh` (needs systemd/docker, neither present); the real browser rendering …

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Installed in 62 minutes.
  • Recovered from all 5 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Licensed MIT, as reported by its host.

What did not, or is not known

  • Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs with mocks92.000.29

Topics (from GitHub)

blocklistbotscybersecuritydashboarddockerextensibleftphoneypothttppythonrdpsecurityself-hostedsipsmbsmtpsshtelnetthreat-intelligencevisualizations

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/knock-knock.svg)](https://argusic.com/subject/knock-knock)

Questions

Does knock-knock run?
knock-knock runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 62 minutes, hitting 5 errors on the way, and recorded the session.
How did Argusic test knock-knock?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit da33d6ae4a60. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test knock-knock?
The run that produced this verdict cost $0.29: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does knock-knock take to install?
62 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does knock-knock need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing knock-knock?
5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for knock-knock?
The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion