Show HN: Totpgate – Single-packet authorization via TOTP
Totpgate is a lightweight port knocking daemon that utilizes TOTP for single-packet authorization. It listens on UDP for a valid TOTP and opens a TCP port temporarily upon validation. This method enhances security by making each authorization unique and resistant to replay attacks.
- ▪Totpgate operates without external binaries or shared libraries, using a statically linked binary to communicate directly with the kernel.
- ▪The daemon validates the TOTP against a shared secret and modifies nftables rules to allow access for a limited time.
- ▪Pre-built binaries for various architectures are available, and users can also build from source with specific requirements.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | GitHub |
| Canonical URL | https://github.com/PepperDev/totpgate |
| Publication time | Sat, 30 May 2026 06:49:06 +0000 |
| Retrieval time | 2026-05-30T07:12:08.061Z |
| Last seen | 2026-05-30T07:12:08.061Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | yT3g__QG37w9 |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
totpgate Single Packet Authorization via TOTP — a lightweight port knocking daemon that listens on UDP for a valid TOTP and, upon matching, temporarily opens a TCP port via direct netlink firewall manipulation. No external binaries, no shared libraries — just a statically linked binary speaking netlink directly to the kernel. Why Traditional port knocking sequences are predictable (fixed port order) and replayable. TOTP-based single-packet authorization replaces the sequence with a time-based one-time password, making each grant unique and replay-proof.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.