PortGuard: Keep Your Services Invisible to Scanners
PortGuard combines a modified fwknop-based server with a cross-platform client that supports the fwknop SPA protocol. Ports stay closed by default and open temporarily only after a valid AES/GPG-signed packet is verified.
Quick Server Install
Installs the latest open-source package built by GitHub Actions from the PortGuard server repository.
curl -fsSL https://portguard.net/install.sh | sudo bash
Traditional Exposure Mode (Risk)
- ✕Ports remain open all day and are continuously probed by global scanners.
- ✕Exposed services face brute-force attempts and exploit attacks directly.
- ✕Firewall allowlists become complex to maintain and lack dynamic flexibility.
PortGuard Mode (Solution)
- ✓Default Deny: Ports are completely invisible before authorization (stealth).
- ✓SPA Auth: Only specially formatted encrypted single packets can trigger access.
- ✓Dynamic Access: Temporarily allow only the source IP, then close automatically.
Core Features
Core Security Features
Strong defaults for teams that want SSH, admin panels, and private services to disappear until authorization is intentional.
Efficient SPA Communication
Send fwknop-compatible single-packet authorization without TCP handshake overhead, with strong stealth.
AES/GPG + HMAC
Integrated SHA256 integrity checks ensure commands are authentic and untampered.
Full Port Stealth
Default DROP behavior makes services appear unreachable to scanners.
Replay Attack Resistance
Time-window validation plus integrity checks quickly invalidates old packets.
پورٹ گارڈ ٹیوٹوریل
A cleaner fwknop-compatible client for every device.
PortGuard Client supports the fwknop SPA protocol. Profiles, one-tap SPA, QR import, encrypted export, and activation stay compatible with fwknopd and PortGuard Server workflows.
How It Works
Security Workflow
PortGuard runs at the firewall edge of protected servers. It continuously inspects network traffic for authorization packets without exposing service handshakes externally.
Generate Authorization Packet
The client uses keys and a timestamp to generate an encrypted single packet.
Handshake-less Delivery
The packet is sent via UDP and similar methods, making handshake-based probing ineffective.
Dynamic Open
After validation, the server temporarily allows the source IP and then automatically removes the rule.
Use Cases
SSH Remote Operations
Protect port 22 and make it visible only briefly after an admin sends SPA.
Multi-Cloud Security
Unified access control across AWS/Azure and more to reduce exposure.
IoT Device Management
Protect IoT control interfaces and avoid direct public exposure.
ACL Automation
Combine scripts and rule cycles to automate temporary authorization.
Downloads and Installation
Supports multi-platform clients and server-side packages
Server Packages
Install PortGuard Server on Debian, Ubuntu, Rocky, CentOS, and OpenWrt
Use the quick installer for supported Linux servers, or download the latest package generated from the open-source GitHub Actions release pipeline.
Quick Install
One command server setup
curl -fsSL https://portguard.net/install.sh | sudo bash
The script detects the operating system, selects the matching package from the GitHub release manifest, verifies SHA256, installs dependencies, and leaves fwknopd ready for configuration export to PortGuard Client.
Open Source Release
Packages synced from GitHub
These packages are built automatically by GitHub Actions from the public PortGuard server source code.
| System | Version | Architecture | Package | ڈاؤن لوڈ کریں۔ |
|---|---|---|---|---|
| Loading packages from GitHub release... | ||||
Related Products
Product
OpenAT
Secure, time-locked data storage powered by drand's mathematical certainty. Encrypt your future today without a central authority.
Visit website
Product
Lockmem
End-to-end encrypted personal media vault for your NAS. Privacy-first management for your self-hosted infrastructure.
Visit websiteअक्सर पूछे जाने वाले प्रश्न और उपयोग परिदृश्य
अंतिम अपडेट:
What is the relationship between PortGuard and fwknop?
PortGuard is built around the fwknop SPA protocol. PortGuard Client is a cross-platform client that sends fwknop-compatible SPA packets, while PortGuard Server is a modified server based on the upstream fwknop project. Compared with traditional sequence-based port knocking, this single encrypted packet model is faster, stealthier, and resistant to replay attacks.
کیا میں ایک پروفائل بنا سکتا ہوں اور کسی مخصوص IP کو ہر سروس پورٹ تک رسائی کی اجازت دینے کے لیے ایک دستک استعمال کر سکتا ہوں؟
جی ہاں OPEN_PORTS ANY کے ساتھ سرور تک رسائی کے بند کو ترتیب دیں اور ACCESS ANY کے ساتھ کلائنٹ پروفائل استعمال کریں۔ پروفائل کو ایک بار بنایا اور درآمد کیا جا سکتا ہے، پھر دوبارہ استعمال کیا جا سکتا ہے۔ ہر درست دستک ایک عارضی سورس-IP اصول بناتا ہے جو ALLOW_IP کے ذریعے منتخب کردہ IP کو FW_TIMEOUT کی میعاد ختم ہونے تک تمام TCP اور UDP سروس پورٹس تک پہنچنے کی اجازت دیتا ہے۔ میعاد ختم ہونے کے بعد، ایک نیا دستک بھیجیں۔ یہ ایک اعلیٰ استحقاق والا موڈ ہے: ایک مختصر ٹائم آؤٹ استعمال کریں، پروفائل اور کیز کی حفاظت کریں، اور یاد رکھیں کہ اپ اسٹریم کلاؤڈ فائر والز، روٹر کے قواعد، اور سروس کی توثیق اب بھی لاگو ہوتی ہے۔
fwknop की तुलना tnock से कैसे होती है?
दोनों का लक्ष्य नेटवर्क पोर्ट छिपाना है, लेकिन fwknop अधिक उन्नत SPA समाधान है। tnock और समान sequence-based daemon कई बंद पोर्ट्स पर कनेक्शन पैटर्न पहचानते हैं, जो धीमा और replay के प्रति संवेदनशील है। fwknop एक ही cryptographically signed और timestamped payload भेजकर इसे हल करता है। फायदे: काफी अधिक सुरक्षा, replay प्रतिरोध, और आधुनिक फ़ायरवॉल के साथ सहज एकीकरण।
मैं अपनी वेबसाइट या निजी सेवा को केवल कुछ लोगों के लिए ही कैसे उपलब्ध करूँ?
By default, PortGuard Server, modified from fwknop, configures your server's firewall to block all inbound traffic to your service port. The service appears completely offline to the public. When an authorized user needs access, they use PortGuard Client with their unique cryptographic key to send a fwknop-compatible Single Packet Authorization (SPA) packet. Once verified, the server dynamically whitelists their current IP address for a brief period.
पब्लिक नेटवर्क पर एक्सपोज़ NAS की सुरक्षा और गोपनीयता बिना डेटा लीक के कैसे सुनिश्चित करें?
NAS को सीधे इंटरनेट पर एक्सपोज़ करना लगातार botnet और scanner probes के कारण बहुत जोखिमभरा है। आम तौर पर दो सुरक्षित विकल्प हैं:
- योजना 1: Cloudflare Zero Trust (Tunnels) यह बिना इनबाउंड पोर्ट खोले NAS ट्रैफ़िक को Cloudflare नेटवर्क से रूट करता है। लाभ: सेटअप आसान, पब्लिक IP की जरूरत नहीं, अतिरिक्त WAF लेयर। हानि: ट्रैफ़िक थर्ड-पार्टी सर्वर से गुजरता है, यानी Cloudflare की प्राइवेसी नीति पर निर्भरता; फ्री-टियर रूटिंग में स्पीड सीमित हो सकती है, जो बड़े मीडिया स्ट्रीमिंग के लिए आदर्श नहीं।
- योजना 2: स्वयं होस्टेड Public IP + fwknop Port Knocking आप राउटर पर पोर्ट खोलते हैं लेकिन उसे fwknop (SPA) से सुरक्षित रखते हैं। पोर्ट पब्लिक इंटरनेट पर अदृश्य रहता है और केवल वैध cryptographically-signed एक्सेस पैकेट पर खुलता है। लाभ: थर्ड-पार्टी से गुजरे बिना बेहतर डेटा प्राइवेसी, और direct कनेक्शन से अधिकतम हार्डवेयर स्पीड (वीडियो स्ट्रीमिंग के लिए अच्छा)। हानि: वास्तविक public IP और थोड़ा अधिक तकनीकी शुरुआती सेटअप चाहिए।
क्या पोर्ट खुलने के बाद fwknop PortGuard मेरी कनेक्शन स्पीड कम करता है?
No. The fwknop-compatible PortGuard Server only handles the initial authorization packet. Once the firewall rule is dynamically created and your IP is authorized, your connection via SSH, WireGuard, or directly to your NAS operates directly between your client and the server at full line speed.
Trusted by DevOps and Security Experts Worldwide
Official Contact
Need help with PortGuard?
For purchase recovery, activation issues, deployment questions, or security reports, contact the official PortGuard support mailbox.
[email protected]