ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Deno runs TypeScript without a build step and sandboxes every process behind explicit permission flags. Here's how that combination works for a real small service — and where it pushes back.
A decision guide for granting Deno runtime permissions with granular allow‑lists, comparing them to --allow-all, and validating the chosen setup.
Learn how to design a secure, observable GitBook webhook that triggers CI/CD pipelines on documentation updates. Covers requirements, minimal design, trust boundaries, operational checks, failure modes, and when redesign is needed.
PuTTY's key exchange settings decide how your SSH session keys are established. Learn which algorithms to prefer, how to configure them, and how to verify the negotiation.
Learn how Electron’s Context Isolation separates renderer and preload contexts, why enabling it improves security, and how to expose only the APIs you need via contextBridge.
Keep Electron's contextIsolation enabled and expose a minimal, typed API via contextBridge. This converts an implicit total-trust boundary into an explicit, auditable surface—preventing XSS from becoming full system compromise.
Learn how to move from manual data filtering to Row-Level Security (RLS) to enforce per-user data isolation transparently without rewriting application logic.
Learn how to set up SSH public‑key authentication: generate a key pair, copy it to the server, tweak sshd_config, and verify the connection. Avoid common pitfalls and secure your remote access.
Keep SELinux enforcing on Fedora. Fix denials by labeling paths with semanage fcontext, using booleans via setsebool -P, and writing narrow custom policy modules (reviewed, not raw audit2allow). Worked examples for httpd on /srv/webapp, remote DB connections, and a custom module.
gitbook
putty
ssh
electron
microsoftsqlserver
fedora