POST-QUANTUM RESILIENCE (PQC)

Post-quantum cryptography and hybrid TLS 1.3

Deterministic protection against future quantum cryptanalysis and 'harvest now, decrypt later' (HNDL) state-level interception. GADNET deploys hybrid ML-KEM key encapsulation mechanisms alongside next-gen NIST standardized digital signatures.

Hybrid X25519MLKEM768 key exchange

Combines classical X25519 elliptic-curve Diffie-Hellman with quantum-resistant ML-KEM-768. Compromising either primitive leaves session secrecy completely intact.

Immunity to harvest-now-decrypt-later

Hybrid TLS combines classical and post-quantum key exchange on supported router connections. This helps address the risk of traffic being recorded for future decryption attempts.

Post-quantum SLH-DSA & ML-DSA signatures

Software release manifests and kernel updates are validated through stateless hash-based SLH-DSA-128s (FIPS 205) and lattice-based ML-DSA-65 (FIPS 204) signatures.

Dual post-quantum node PKI

GADNET maintains an autonomous on-node public key infrastructure issuing ML-DSA-65 certificates for internal domains (admin-pq.gadnet), operating concurrently with ECDSA P-256 roots.

>> Technical details: TLS 1.3 KEM negotiation & OpenSSL PQC cipher suites

The GADNET node utilizes OpenSSL supporting named key exchange groups X25519MLKEM768 (TLS ID 0x11ec) and SecP256r1MLKEM768 (0x11ed). Negotiated inside TLS 1.3 key_share extensions (RFC 8446). Panel certificates for admin-pq.gadnet are minted with ML-DSA-65 keys.

LINUX KERNEL ARCHITECTURE

Kernel-level Zero Trust architecture

GADNET applies access policies directly on the router. The nftables firewall enforces configured rules between zones, devices and the internet.

Kernel-enforced default deny

Every ingress packet in forward and input hooks is dropped by default. Transit requires an explicit, cryptographically authenticated rule tied to a verified device profile.

Atomic nftables rule chains

nftables rules are updated transactionally. The administrator changes a household policy or device access, and the system applies the prepared rule set.

Network segmentation and inter-zone traffic control

GADNET controls inter-zone traffic through stateful firewall rules. VLAN mode also separates zones at layer 2. In flat mode, zones share a network bridge, so protection relies on filtering rules and additional isolation mechanisms.

Hardware-bounded micro-segmentation

5 discrete operational zones (Quarantine, IoT, Guests, Trusted LAN, Admin Plane) feature isolated subnets, virtual interfaces, and independent routing tables preventing lateral movement.

>> Technical details: nftables 'inet filter' table architecture & forward drop policy

GADNET firewall architecture centers on the 'inet filter' table. The forward hook enforces: 'type filter hook forward priority filter; policy drop;'. Stateful tracking permits only 'ct state established,related accept'. Any cross-zone transit from IoT to Trusted LAN is logged under '[ZT-DROP-IOT]' and dropped immediately.

HARDWARE IDENTITY & ACCESS CONTROL

Hardware-backed FIDO2 auth and mTLS identity

Administrator sign-in uses passkeys, FIDO2 keys or a supported device certificate and PIN. Verification follows the selected authentication method.

Hardware FIDO2 / Passkey tokens (AAL2)

Administrator authentication engineered to NIST SP 800-63B AAL2 compliance. Hardware FIDO2 authenticators (YubiKey) and platform Passkeys eliminate remote credential harvesting.

Mutual TLS certificate validation

An administrator can sign in with a passkey or FIDO2 key, or use a device certificate and PIN on a supported phone. Network policies and user permissions govern panel access.

Hardware vault via Keystore & DPAPI

Client private keys and session credentials reside in hardware-isolated secure elements (Android Keystore hardware-backed keys, TPM 2.0, and Windows DPAPI-NG enclave protection).

Emergency GPG escrow & BIP-39 phrase

Disaster recovery architecture features a 24-word BIP-39 seed phrase generated during initial bootstrap and an asymmetric GPG key recovery escrow preserving administrative sovereignty.

>> Technical details: WebAuthn authenticator assertion validation & Nginx mTLS directives

WebAuthn checks user presence and verification. Certificate sign-in uses a confirmed device certificate and PIN. TLS configuration and panel policies apply the requirements for the selected method.

DNS LAYER INTEGRITY & ANTI-BYPASS

DNS filtering and limiting bypass attempts

GADNET combines local DNS policies, DNSSEC validation and encrypted DoT queries with firewall controls. DNS enforcement and known-resolver lists help apply your selected filtering rules.

Routing ordinary DNS queries through the router

With DNS enforcement enabled, UDP/TCP port 53 queries from client networks are sent to the local DNS service, even if a device specifies another server. The active policy front applies rules assigned to the device before forwarding queries.

Blocking known DoH and DoT servers

The firewall blocks configured addresses of known public DoH/DoT resolvers. DNS policies can also block their names. Enabled lists and rules define the protection scope.

DNSSEC signature validation

Unbound checks response signatures for domains with a DNSSEC chain of trust. Strict validation returns SERVFAIL for responses that fail validation. Coverage depends on domain DNSSEC support and resolver settings.

CERT Polska lists and RPZ policies

Enabled lists, including CERT Polska, are refreshed on a schedule and applied according to assigned policies. An RPZ rule can return NXDOMAIN for a blocked domain, preventing its address from being obtained through this DNS service. Effectiveness depends on list freshness and configuration.

Technical details: policy front and DNS path

Queries pass through the Unbound policy front, dnsmasq and a separate DNSSEC/DoT resolver. During policy-front recovery, fail-open operation maintains name resolution through dnsmasq. Restoring the policy front reapplies assigned filters.

DATA SOVEREIGNTY & AUDITABILITY

Local data sovereignty and signed LBU snapshots

Configuration, event history and network statistics are stored locally. The administrator manages retention, backups and selected external integrations.

Local control of data and settings

All analytics engines, traffic statistics, and security classifiers execute on local hardware. The node maintains complete protective capability even in air-gapped or fully offline environments.

Signed Alpine LBU apkovl snapshots

Configuration backups utilize the Alpine Local Backup format (LBU apkovl) signed with node cryptographic credentials. Tampered or unauthorized configuration payloads are rejected at boot time.

Local immutable audit logging

Local logs help explain events and review protection settings. The administrator selects retention and manages access to panel data.

Full GDPR compliance & EU data sovereignty

Engineered strictly to privacy-by-design standards and European GDPR regulations (Articles 25 and 32). Includes one-click cryptographic export and irreversible data erasure functions.

>> Technical details: squashfs read-only rootfs & cryptographic LBU verification

The primary root filesystem operates as an immutable squashfs read-only partition, neutralizing persistent malware implants. Persistent configurations reside strictly inside /etc/lbu/apkovl.tar.gz archives. During boot, the kernel validates the apkovl signature before overlayfs mounting.

AUDIT VERIFICATION REPORT (100% PASS)

Technical verification and panel security audit

Official verification and audit report for GADNET node v0.1.67 running Alpine Linux on Raspberry Pi 5 hardware. All 30 administrative control planes verified with a deterministic 100% PASS rating across 3,100+ automated test fixtures.

30 audited administration pages

Every administrative module (nftables firewall, Zero Trust zones, Unbound DNS, CAKE SQM, anti-fraud daemon, LBU backups, mTLS certificate manager) has been verified and certified.

Over 3,100 automated verification tests

Comprehensive regression test suite covering firewall syntax correctness, cryptographic signature validity, DNS resolution isolation, and deterministic queue discipline under full link saturation.

Hardware-verified on Raspberry Pi 5

Full benchmark validation on quad-core ARM Cortex-A76 (2.4 GHz) with native gigabit ethernet interfaces. Leverages ARMv8-A Cryptographic Extensions for low-power high-throughput operations.

Hardened Alpine Linux (musl libc)

Minimalist, hardened operating system built on musl libc and compiled with full exploit mitigations (Stack Smashing Protection SSP, ASLR, Position Independent Executables PIE, and FORTIFY_SOURCE).

// GADNET NODE VERIFICATION AUDIT MATRIX · HARNESS v0.1.67 AUDIT STATUS: 100% PASS (30/30 PAGES)
Admin Module / Page Verified Components & Engine Audit Result
/admin/antifraud STUN/TURN correlation, AnyDesk/TeamViewer killswitch, conntrack PASS (100%)
/admin/firewall Native nftables L3/L4, atomic commit, 5 zones, default deny PASS (100%)
/admin/dns Recursive Unbound, DNSSEC validation, DoT port 853, RPZ CERT PASS (100%)
/admin/pqc Hybrid TLS 1.3 X25519MLKEM768, ML-DSA-65 PKI, SLH-DSA signatures PASS (100%)
/admin/auth FIDO2 WebAuthn AAL2 Passkeys, mTLS certs, BIP-39 seed & GPG escrow PASS (100%)
/admin/sqm sch_cake, diffserv4, ack-filter, latency management under load PASS (100%)
/admin/backup Alpine LBU apkovl, cryptographic signatures, squashfs read-only rootfs PASS (100%)