Managing Network Access in CentOS with Firewalld Zones
Learn how to manage network traffic in CentOS using Firewalld zones, including the critical difference between runtime and permanent rules to prevent configuration loss.
Loading…
ReadMeFeed / Community knowledge
#network-security
Real questions. Useful conversations. Find the people who know your stack.
centosChoosing the Right Transfer Protocol in FileZilla: FTP, FTPS, and SFTP
A technical guide to choosing between FTP, FTPS, and SFTP in FileZilla, focusing on security trade-offs, firewall traversal, and verification of encrypted connections.
filezillaHardening TLS: Using OpenSSL to Implement Public Key Pinning
Learn how to use OpenSSL to extract public key fingerprints for TLS pinning, mitigating MitM attacks by bypassing the system trust store.
openssl
Private Link for Azure Storage: when to isolate and how to avoid DNS failures
Security teams want storage traffic off the public internet. Private Link can deliver isolation, but DNS misconfiguration is the common failure. Here is a practical decision framework and a worked example for locking down Azure Storage with a Private Endpoint.
PuTTY SSH Proxy (Jump Host) Architecture Note
An architecture note on PuTTY's SSH proxy (jump host) implementation, covering nested SSH transport, trust boundaries, and operational failure modes.
puttyUnderstanding the Architecture of Opera's Integrated VPN
Opera's VPN is technically a secure HTTPS proxy. Learn how it differs from a system-wide VPN and how to verify its scope using simple network tests.
operaTaming Firewall Chaos: Using pfSense Aliases for Scalable Rule Management
Stop managing dozens of identical firewall rules. Learn how to use pfSense Aliases to group IPs, ports, and networks into scalable, easy-to-audit configurations.
Securing FTP Transfers: Implementing Explicit FTPS in FileZilla
Stop sending passwords in plain text. Learn how to configure Explicit FTPS in FileZilla to secure your control and data channels while avoiding common firewall timeouts.
Restricting NW.js DevTools remote debugging listener to localhost
Goal: Configure the NW.js DevTools remote debugging interface so that it listens only on the localhost loopback address (127.0.0.1) to prevent unintended network exposure. Constraint: By default, when DevTools are enabled the builder binds the debugging listener to all interfaces (0.0.0.0) and the NW.js manifest or command‑line interface does not expose a bu
nodewebkit