lijx122

dsh-plugin-auth-guard

Name: dsh-plugin-auth-guard
Author: lijx122

Enterprise-grade Zero-Trust Authentication, LAN/Public Access Control & Security Gate Plugin for DeepSeek Harness (DSH)

Stars: 0
Language: JavaScript
Created: Aug 15, 2026
Updated: Aug 15, 2026

Auth

GitHub repo

Introduction

dsh-plugin-auth-guard

DeepSeek Fish Logo

Enterprise-Grade Zero-Trust Authentication, LAN/Public Access Control & Security Gate Plugin for DeepSeek Harness (DSH)

English Documentation | 简体中文文档 (README_CN.md)

📖 Background & Problem Statement

DeepSeek Harness (DSH) is a powerful AI coding agent runtime designed natively for local desktop workflows (127.0.0.1). When developers attempt to expose DSH across local area networks (LAN) to mobile devices (iOS/Android) or host it on remote cloud servers, they encounter critical barriers:

Privileged Interface 403 Blocking: DSH natively enforces hardcoded loopback fences. Any non-localhost request calling settings.describe or llm.providers is blocked with 403 Forbidden, making remote model switching impossible.
Mobile RPC Crashes: Mobile browsers (iOS Safari / Chrome Android) lack Secure Context over plain HTTP, rendering crypto.randomUUID undefined and breaking all RPCs.
Severe Remote Code Execution (RCE) Risks: DSH lacks built-in authentication. Opening port 3080 to LAN or WAN allows anyone on the network to create sessions and execute arbitrary shell commands via the coding agent.
Third-Party Plugin Escapes: Sidebar plugins (dsh-better-sidebar) and package managers expose PTY terminal sockets (/sidebar/ws/terminal) and arbitrary file access without authentication.

dsh-plugin-auth-guard is the zero-intrusion, production-ready solution. It unblocks remote access, injects mobile polyfills dynamically, and establishes a full-stack Default-Deny Zero-Trust Security Gateway with cryptographic credential lifecycle management.

🏗️ Architecture Overview

flowchart TD
    Client[Client Device Phone/Tablet/PC] -->|HTTP / WebSocket| Ingress[Node.js http.Server: 3080]
    Ingress --> L1[L1: Physical Socket Origin Check isPhysicalLoopback]
    L1 --> L2[L2: Enterprise Security Headers nosniff / SAMEORIGIN / Referrer / no-store]
    L2 --> L3[L3: 64KB Payload OOM Protection]
    L3 --> L4[L4: CSRF & CSWSH Strict Hostname Comparison]
    L4 --> L5{L5: Public Whitelist Strict Regex Matching}
    
    L5 -->|Whitelisted: Static Files / Login API| PassPublic[Serve Static Resource]
    L5 -->|Non-Whitelisted: Core RPC / Plugin Routes / Terminal WS| L6{L6: Password-Fingerprinted HMAC-SHA256 Verification}
    
    L6 -->|Authenticated / Physical Loopback| Router[Forward to Core App / Proxy Privileged RPC]
    L6 -->|Unauthenticated / Revoked Token| Block[Block with HTTP 401 / Destroy WebSocket]

🌟 Highlights & Technical Specifications

1. 🌐 Adaptive Network Exposure & Privileged RPC Bridge

0.0.0.0 Automatic Binding: Binds Web GUI to 0.0.0.0:3080 and dynamically enumerates all active LAN IPv4 interfaces.
Privileged RPC Proxying: Securely proxies settings.describe, llm.providers, credentials.* for authenticated clients, completely eliminating 403 Forbidden errors.
Dynamic Mobile Polyfill Injection: Injects cryptographic UUID polyfills into <head> on the fly via tapIndex, ensuring smooth mobile operation over HTTP.

2. 🛡️ Default-Deny Zero-Trust Gateway

Socket-Level Interception: Intercepts HTTP request and WebSocket upgrade events at the lowest TCP server level.
Strict Whitelist Verification: Blocks unauthenticated access to all core RPCs (/api/*), plugin managers (/api2/*), and sidebar routes (/sidebar/*).

3. 🔑 Cryptographic Security & Credential Lifecycle

Salted Scrypt Password Hashing: 32-byte Scrypt hash with random salt. Config fields declared with .role('secret') to prevent wire leakage.
Constant-Time Verification: crypto.timingSafeEqual prevents timing side-channel attacks.
Password Fingerprint Binding: HMAC-SHA256 tokens embed current password fingerprints. Changing the password instantly revokes all tokens globally in milliseconds.
Active WebSocket Purge: Automatically terminates all active remote terminal/event WebSockets upon password change or logout.

4. 🚫 Anti-Spoofing & DoS Protection

Physical Socket Validation: Validates req.socket.remoteAddress to prevent Host: 127.0.0.1 spoofing and proxy loopback inversion.
IP Sliding Window Rate-Limiting: Blocks IPs for 15 minutes after 5 consecutive failed attempts (HTTP 429) with auto-garbage collection (GC).
Global Burst Throttling: Restricts total login frequency to 40 req/min across all IPs to defeat distributed botnets.
64KB Request Body Cutoff: Aborts payloads exceeding 64KB to prevent stream-based OOM denial-of-service attacks.
CSRF & CSWSH Protection: Strict hostname matching blocks Cross-Origin Request Forgery and Cross-Site WebSocket Hijacking.

5. 🎨 Native DSH UI Design & Multi-Tab Synchronization

DeepSeek Design System: Follows DSH CSS tokens (--dsw-*), fish logo, and standard typography.
Top-Level Body Portal Lock: Mounts lock screen at document.body level (z-index: 2147483647) with background blur to prevent click-through.
Multi-Tab Sync: Leverages BroadcastChannel for instant cross-tab state updates.

📦 Installation & Setup

Option 1: Via DSH CLI (Recommended)

dsh plugin --profile web add github:lijx122/dsh-plugin-auth-guard

Option 2: Via DSH Web Marketplace

In DSH Web GUI, go to Settings $ ightarrow$ Plugins $ ightarrow$ Marketplace.
Search for auth-guard and click Install.

Option 3: Local Linking (Developer Mode)

Clone this repository to ~/.dsh/plugins/dsh-plugin-auth-guard.

In ~/.dsh/profiles/web/package.json, add:

{
  "dependencies": {
    "dsh-plugin-auth-guard": "link:../../plugins/dsh-plugin-auth-guard"
  }
}

Append "dsh-plugin-auth-guard" to dsh.profile.bundles and restart DSH.

⚙️ Configuration Guide

Navigate to Settings $ ightarrow$ Security & Access (安全与访问):

Setting	Description	Default
Require password for LAN/Remote access	Requires password authentication when accessed from non-localhost IPs	Enabled
Enforce authentication globally	Enforces password authentication even on `127.0.0.1` localhost	Optional
Administrator Credentials	Set or change admin username and password ($\ge 6$ characters)	Customizable
Active LAN IP Directory	Real-time overview of all listening LAN addresses with 1-click copy	Auto-detected

🚀 5 Essential Reverse Proxy Settings (Nginx / Caddy / Cloudflare)

When deploying behind a reverse proxy, configure the following 5 settings to ensure smooth large file uploads, unbuffered streaming responses, and accurate zero-trust perimeter defense:

1. Increase Max Body Size (Required to avoid 413)

Nginx default client_max_body_size is 1MB, which rejects image and file uploads.

Setting: client_max_body_size 160M; (aligned with DSH 160MB upload capacity).

2. Forward Real Client IP and Protocol (Critical for Security)

auth-guard relies on these headers to distinguish local from proxied traffic and apply accurate rate-limiting:

Setting:

proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;

3. Enable WebSocket Protocol Upgrades (Required)

DSH real-time conversation streams and sidebar PTY terminals require WebSocket support.

Setting:

proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";

4. Extend Request Timeouts (For Long AI Inferences)

Prevents Nginx from dropping connections during long-running agent tool runs.

Setting:

proxy_read_timeout 3600s;
proxy_send_timeout 3600s;

5. Disable Response Buffering (For Real-Time Token Streaming)

Ensures tokens stream to the browser character-by-character without proxy-level buffering delays.

Setting: proxy_buffering off;

📑 Production-Ready Nginx Configuration Template

# 1. HTTP -> HTTPS Redirect
server {
    listen 80;
    server_name dsh.yourdomain.com;
    return 301 https://$host$request_uri;
}

# 2. HTTPS Proxy Core
server {
    listen 443 ssl http2;
    server_name dsh.yourdomain.com;

    # SSL Certificates
    ssl_certificate     /etc/nginx/ssl/dsh.yourdomain.com.crt;
    ssl_certificate_key /etc/nginx/ssl/dsh.yourdomain.com.key;
    ssl_protocols       TLSv1.2 TLSv1.3;
    ssl_ciphers         HIGH:!aNULL:!MD5;

    # [Key 1] Allow up to 160MB file uploads
    client_max_body_size 160M;

    location / {
        proxy_pass http://127.0.0.1:3080;
        proxy_http_version 1.1;

        # [Key 2] WebSocket Upgrade Support
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";

        # [Key 3] Real IP and Scheme Forwarding
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;

        # [Key 4 & 5] Timeout & Unbuffered Real-time Token Streaming
        proxy_read_timeout 3600s;
        proxy_send_timeout 3600s;
        proxy_buffering off;
    }
}

❓ FAQ & Troubleshooting

Q1: What should I do if I forget the administrator password?

Open ~/.dsh/settings.yaml on the host machine.
Under auth-guard:, clear passwordHash and salt (set to "").
Restart DSH and open http://127.0.0.1:3080 locally to initialize a new password.

Q2: Why are other devices logged out when the password is changed?

This is by design. Changing the password updates the password fingerprint in tokens and triggers the active WebSocket purge to ensure compromised credentials cannot be reused.

Q3: Why does mobile Safari work over plain HTTP without HTTPS certificates?

The plugin injects a crypto.randomUUID polyfill dynamically on the fly during HTML serving, allowing seamless mobile operation without local SSL setup.

📄 License

Distributed under the MIT License.