Cockpit LogoCockpit.run

Server Authentication & Isolated Architecture

An engineering guide to connecting remote Linux infrastructure using IP & Password, SSH Key Pairs, and sandboxed telemetry.

Protocol Pipeline Overview
01 / CLIENT RUNTIME

Browser Enclave

WebCrypto engine handles client-side key parsing and payload framing. Sensitive bytes reside strictly in volatile heap memory.

02 / TRANSPORT PIPELINE

Blind Socket Relay

Low-latency ephemeral proxy streams raw SSH packets. No payload decryption, no telemetry interception, zero packet caching.

03 / REMOTE HOST

OpenSSH Daemon

Your server's standard port 22 daemon. Processes authentication natively via Linux PAM without third-party agents.

AUTH METHODSPassword / Ed25519 / RSA
AGENT DESIGNAgentless / Isolated
SUPPORTED OSAll POSIX Linux
PERSISTENCEZero-Custody (RAM)
Authentication Mode 01

IP & Password Authentication

Direct root or sudo credentials over standard SSH. When bootstrapping a fresh server from Hetzner, DigitalOcean, AWS Lightsail, Linode, or Vultr, cloud providers immediately assign a public IP address and an initial root password.

Cockpit allows you to input these exact parameters directly into the browser. Within 200 milliseconds, an SSH handshake is negotiated directly with your machine's native OpenSSH daemon.

How Password Handshake Works

  • 01Ephemeral Session Initialization: Your password is piped through an encrypted WebSocket channel directly into the OpenSSH RFC 4252 userauth exchange.
  • 02Native Linux PAM Validation: OpenSSH on your server verifies the password against /etc/shadow through standard PAM (Pluggable Authentication Modules).
  • 03Zero-Storage Guarantee: The password is never serialized into a database, Redis cache, log file, or cookies. Closing the browser tab destroys the memory allocation instantly.
Authentication Mode 02

SSH Key Pair Authentication

Ed25519 & RSA encrypted private key authentication. For production hosts where PasswordAuthentication no is enforced in /etc/ssh/sshd_config, Cockpit provides first-class cryptographic key-pair support.

Unlike traditional cloud panels that demand uploading your private key to their remote backend server, Cockpit handles private key signing in client-side WebCrypto RAM:

Client-Side Key Enclave

Ed25519 (Recommended)

High-speed elliptic curve signatures (256-bit). Minimal memory footprint with maximal resistance against side-channel timing attacks.

RSA (2048 - 4096 bit)

Standard legacy format supported across all Linux distributions and enterprise hardware bastion servers.

ssh-keygen -t ed25519 -C "cockpit-session"
Architecture Principle 01

Agentless by Default, Fully Isolated Agent When Needed

Most infrastructure panels force a rigid choice: either an unmonitored SSH script that breaks under load, or a bloated proprietary root daemon that permanently alters your host environment.

Cockpit bridges this with a dual-mode approach: agentless by default for instantaneous zero-install access, and our own purpose-built, fully isolated agent for specialized background tasks.

MODE A / ZERO INSTALL

Agentless Native SSH

Used for ad-hoc terminal work, emergency access, and standard administration. Directly reads /proc and uses standard POSIX utilities over SSH. Zero disk artifacts left behind.

MODE B / SPECIALIZED CASES

Cockpit Isolated Agent

Used when you need persistent background metrics, real-time process monitoring, or automated deployment triggers when your browser window is disconnected.

How Our Agent Maintains Total Isolation

  • 01Sandboxed Container / Scoped Process: Runs in strict isolation (Docker/OIDC container or unprivileged systemd slice). It has zero access to host credentials or foreign directory trees.
  • 02Outbound-Only Encrypted Tunnel: The agent never opens incoming listening ports on your server. It initiates an outbound mutual-TLS/WSS connection to Cockpit, preserving your firewall and security groups.
  • 03Minimal Resource Envelope: Consumes under 15MB of RAM with sub-0.5% CPU utilization. It does not overwrite system binaries, shared libraries, or kernel configurations.
Architecture Principle 02

Any Linux Host: Cloud, VPS, & Bare Metal

Ubuntu, Debian, RHEL, CentOS, Rocky Linux, Arch Linux, Alpine, and cloud VMs. Because Cockpit does not compile kernel modules or bind to specific packaging ecosystems (APT, DNF, Pacman, APK), it runs identically across any distribution with an OpenSSH daemon.

DEBIAN / UBUNTUv18.04 — v24.04+
RHEL / ROCKYv8.x — v9.x+
ARCH LINUXRolling release
ALPINE LINUXv3.16 — v3.20+
Compatible with all cloud providers (AWS EC2, Google Cloud Compute, Hetzner Cloud, DigitalOcean Droplets, OVH, Scaleway) as well as on-premise physical servers behind private jump hosts.

Verifying on your server

Because Cockpit connects purely through OpenSSH, your Linux kernel logs the session through native PAM and systemd journal facilities. You can watch the connection live on your machine:

auth.log live audit
$ tail -f /var/log/auth.log | grep sshd
sshd[12480]: Accepted password for root from <client-ip> port 54102 ssh2
sshd[12480]: pam_unix(sshd:session): session opened for user root by (uid=0)

Experience visual Linux management

Connect any Linux server directly from your browser. Completely free forever, zero tracking, zero installation.