Problem When using mosh with a FIDO2-backed SSH key (sk-ed25519 / sk-ecdsa, e.g. YubiKey), the touch prompt is never shown. The YubiKey blinks — meaning it received the signing request — but the terminal hangs silently until timeout. This affects any tool that invokes SSH as a subprocess without a proper controlling TTY, including mosh and ansible. Root Cause Mosh calls SSH internally with the -n flag: ssh -n -tt -S none -o ProxyCommand=... <host> -- mosh-server new ... The -n flag redirects SSH’s stdin from /dev/null. libfido2 needs a real /dev/tty to print the touch prompt. With -n in effect, the signing request reaches the YubiKey hardware (hence the blinking) but the prompt is swallowed and there is no way to respond. ...

If you’ve ever had an SSH session freeze mid-command because you switched from Wi-Fi to mobile, or lost your work because a hotel network dropped for three seconds, Mosh is the tool that fixes all of that. What is Mosh? Mosh (Mobile Shell) is a remote terminal application that replaces SSH for interactive sessions. It uses SSH only for the initial authentication handshake, then hands off to its own UDP-based protocol (SSP — State Synchronization Protocol) for the actual terminal session. ...

uv + direnv A manual, lightweight approach to Python virtual environment management that auto-activates when you cd into a project and deactivates when you leave — without ever running source .venv/bin/activate again. Why This Approach? Traditional Python workflows require manually activating and deactivating virtual environments. Forget to activate? You install packages globally. Forget to deactivate? You pollute one project with another’s dependencies. This setup eliminates that entire class of mistakes. ...

Features Smart Update Logic: Intelligently handles dual-stack environments. It preserves existing IPv4 records when adding IPv6 (and vice versa), eliminating race conditions. Automatic PTR Generation: Automatically generates reverse DNS (Pointer) records in both standard and in-addr.arpa formats. Persistence & Repair: Includes rc.syshook.d scripts to ensure patches survive OPNsense firmware updates and system reboots. Dedicated Logging: Writes detailed, timestamped activity logs to /var/log/kea-unbound.log with automatic rotation via newsyslog. Smart Hostnames: Automatically generates hostnames from MAC addresses or DUIDs if the client device does not provide one. Non-Destructive: Uses OPNsense’s native hook system to inject configuration safely without modifying core system files. Prerequisites Before installing, ensure the following services are enabled in OPNsense: ...

If you’ve ever had your internet go down in the middle of a video call, you know the pain. I decided to fix that by adding LTE failover to my OPNsense router using a Ubiquiti U5G Max. The U5G Max exposes its cellular WAN through a GRE tunnel, which means you don’t need a UniFi gateway to use it — any router that supports GRE can take advantage of it. This wasn’t entirely straightforward. OPNsense refuses to assign an IP to a GRE tunnel interface through the GUI, there are MTU issues that silently break web browsing, and there’s a system setting that’s disabled by default without which failover simply won’t trigger. This guide covers everything I learned getting it working — the final, tested configuration with all the gotchas addressed. ...

System Overview | OS | Ubuntu 24.04 (Proxmox VM with GPU passthrough) | | GPU | NVIDIA RTX 2000 Pro Blackwell (16GB VRAM) | | Frigate | 0.16.4 (stable-tensorrt Docker image) | | Detector | ONNX (GPU-accelerated via TensorRT) | | Models | YOLOv9-c-640 and/or D-FINE-L-640 | | MQTT | Eclipse Mosquitto 2 | | Cameras | RTSP via UniFi Protect (192.168.1.10:7447) | 1. Prerequisites Docker and Docker Compose must be installed. NVIDIA drivers must be working (nvidia-smi should show your GPU). ...

Key Features Perfect Prompt Character: The author searched through the entire Unicode range to find the ideal prompt character (❯) Git Integration: Shows the current branch and indicates dirty state with an asterisk (*) Asynchronous Git Checks: Displays up/down arrows for unpushed/unpulled commits (checked asynchronously for better performance) Smart Feedback: Prompt character turns red when the last command fails (exits with non-zero status) Execution Time: Displays command execution time when it exceeds a configurable threshold Context-Aware Display: Username and host only appear when in an SSH session or container Title Bar Integration: Shows current path in the title and current folder & command when a process is running VI-Mode Support: Indicates VI-mode status with a reverse prompt symbol (requires ZSH 5.3+) Customizable: Serves as an excellent starting point for your own custom prompt Requirements Git: Version 2.15.2 or higher ZSH: Version 5.2 or higher (older versions may work but are not recommended) Note: Cannot be installed with yarn, must use npm or manual installation Installation Methods Method 1: npm (Recommended) The quickest way to install Pure is via npm: ...

Magic Wormhole: A Deep Dive into Secure, Simple File Transfer Core Architecture The Protocol Stack Magic Wormhole operates on a multi-layered architecture: 1. The Mailbox Server (Rendezvous Server) A WebSocket-based relay that facilitates initial connection establishment Default public server: ws://relay.magic-wormhole.io:4000/v1 Stores encrypted messages temporarily Never sees plaintext data Can be self-hosted for increased reliability 2. The Transit Relay Handles actual data transfer when direct peer-to-peer connections fail Used when both peers are behind NAT Default server: tcp:transit.magic-wormhole.io:4001 All data passing through is end-to-end encrypted 3. Connection Negotiation The tool attempts multiple connection strategies in parallel: ...