All posts

A single stolen session key can undo years of engineering.

Mosh wasn’t built to play cat and mouse with attackers. It was built to end the game. Unlike traditional SSH, Mosh (Mobile Shell) encrypts every packet with robust cryptography, rotates keys in real time, and resists replay attacks even over unstable or roaming connections. When networks drop, Mosh keeps its state without exposing your session to hijacking. There is no TCP tunnel to poison, no lingering session for an attacker to intercept. The only way in is through the handshake—and that hands

Free White Paper

DPoP (Demonstration of Proof-of-Possession) + Single Sign-On (SSO): The Complete Guide

Architecture patterns, implementation strategies, and security best practices. Delivered to your inbox.

Free. No spam. Unsubscribe anytime.

Mosh wasn’t built to play cat and mouse with attackers. It was built to end the game. Unlike traditional SSH, Mosh (Mobile Shell) encrypts every packet with robust cryptography, rotates keys in real time, and resists replay attacks even over unstable or roaming connections. When networks drop, Mosh keeps its state without exposing your session to hijacking. There is no TCP tunnel to poison, no lingering session for an attacker to intercept. The only way in is through the handshake—and that handshake is locked down.

Security on the Mosh platform comes from several deliberate design choices. Every connection is authenticated using modern public-key cryptography before a single byte of shell data moves. Datagram Transport Layer Security (DTLS) ensures encryption without inheriting TCP’s weaknesses. Because Mosh runs over UDP, it shrugs off packet loss, spoofed reset attacks, and latency spikes that would cripple SSH. And because it uses ephemeral keys, even if a session key were somehow exposed, it would expire almost immediately, rendering it useless to an intruder.

The platform never trusts the network. Session resumption doesn’t re-use keys. It never assumes that a client’s IP address proves identity. It does not forward TCP connections, does not run background daemons anyone can scan, and its server-side footprint is minimal—only the exact code needed to establish and maintain the user shell. This narrow attack surface is intentional.

Continue reading? Get the full guide.

DPoP (Demonstration of Proof-of-Possession) + Single Sign-On (SSO): Architecture Patterns & Best Practices

Free. No spam. Unsubscribe anytime.

Administrators can audit connections, enforce strict client authentication policies, and integrate Mosh into hardened bastion hosts. Developers can test secure deployments without babysitting dying SSH tunnels. Teams working across continents can be confident that transient network drops or switching from Wi-Fi to LTE will not trigger insecure reconnections.

Platform security isn’t about compliance checkboxes. It’s about building the system so attacks fail without drama or alerts. Mosh’s architecture makes compromised single points of failure rare, mitigates the impact if they occur, and values predictable, studied cryptographic behavior over experimental shortcuts.

You can talk about this kind of security, or you can see it. With hoop.dev, you can launch a live, secure Mosh session in minutes—no waiting, no manual setup, just the full platform running where you can try it yourself. Test the resilience. Watch the connection hold steady as you roam. And know that the security you see is the security it’s built on.

Get started

See hoop.dev in action

One gateway for every database, container, and AI agent. Deploy in minutes.

Get a demoMore posts