Just found a new RDP server solution on Github. Has anyone tested this?

lamco-rdp-server

Professional RDP Server for Wayland/Linux Desktop Sharing

Production-ready RDP server that provides secure remote desktop access to Linux systems running Wayland, using the XDG Desktop Portal for screen capture and input injection.

Overview

lamco-rdp-server is a modern, production-tested remote desktop server for Wayland-based Linux desktops. It implements the Remote Desktop Protocol (RDP) with native Wayland support via XDG Desktop Portal and PipeWire, enabling secure remote access without X11 dependencies.

Built in Rust with a focus on security, performance, and compatibility with modern Linux desktop environments (GNOME, KDE Plasma, etc.).

Features

Core Features (Implemented)

RDP Protocol Support: Full RDP 10.x server impleme…

lamco-rdp-server

Professional RDP Server for Wayland/Linux Desktop Sharing

Production-ready RDP server that provides secure remote desktop access to Linux systems running Wayland, using the XDG Desktop Portal for screen capture and input injection.

Overview

Built in Rust with a focus on security, performance, and compatibility with modern Linux desktop environments (GNOME, KDE Plasma, etc.).

Features

Core Features (Implemented)

RDP Protocol Support: Full RDP 10.x server implementation via IronRDP
Wayland Native: Portal mode using XDG Desktop Portal (no X11 required)
PipeWire Screen Capture: Zero-copy DMA-BUF support for efficient streaming
H.264 Video Encoding: EGFX channel with AVC420/AVC444 codec support
Secure Authentication: TLS 1.3 and Network Level Authentication (NLA)
Input Handling: Full keyboard and mouse support with 200+ key mappings
Clipboard Sharing: Bidirectional clipboard sync (text and images)
Multi-Monitor: Layout negotiation and display management
Damage Detection: SIMD-optimized tile-based frame differencing (90%+ bandwidth reduction)

Premium Features (Optional)

Hardware Encoding (VA-API): Intel/AMD GPU acceleration (--features vaapi)
Hardware Encoding (NVENC): NVIDIA GPU acceleration (--features nvenc)
AVC444: Full 4:4:4 chroma with sRGB/full-range VUI signaling for perfect text clarity

wlroots Compositor Support (NEW - 2026-01-16)

Two strategies for wlroots-based compositors (Sway, Hyprland, River, labwc):

Native Deployment (wlr-direct):

Direct Wayland protocol usage (zwp_virtual_keyboard_v1 + zwlr_virtual_pointer_v1)
Zero permission dialogs (direct compositor access)
Sub-millisecond input latency
Build with: --features wayland
Deployment: systemd user service or direct execution
Status: ✅ Production-ready, fully implemented

Flatpak Deployment (libei/EIS):

Portal RemoteDesktop + EIS protocol via reis crate
Flatpak-compatible (Portal provides socket across sandbox)
One-time permission dialog (standard Portal flow)
Build with: --features libei
Deployment: Flatpak bundle
Status: ✅ Fully implemented, requires portal backend with ConnectToEIS support

Supported Compositors:

✅ Sway 1.7+ (native: wlr-direct, Flatpak: libei when portal supports it)
✅ Hyprland (native: wlr-direct, Flatpak: libei when portal supports it)
✅ River (native: wlr-direct)
✅ labwc (native: wlr-direct)
✅ Any wlroots-based compositor

See: docs/WLR-FULL-IMPLEMENTATION.md for complete details

Architecture

lamco-rdp-server
├─> Portal Session (screen capture + input injection permissions)
├─> PipeWire Manager (video frame capture)
├─> EGFX Video Handler (H.264 encoding via OpenH264/VAAPI/NVENC)
├─> Input Handler (keyboard/mouse from RDP clients)
├─> Clipboard Manager (bidirectional clipboard sync)
└─> IronRDP Server (RDP protocol, TLS, channel management)

See docs/architecture/COMPREHENSIVE-ARCHITECTURE-AUDIT-2025-12-27.md for detailed architecture documentation.

Dependency Architecture

lamco-rdp-server uses a layered dependency strategy:

Published Lamco Crates (crates.io)

Stable, reusable components published independently:

lamco-wayland (0.2.3) - Wayland protocol bindings
lamco-rdp (0.5.0) - Core RDP utilities
lamco-portal (0.3.0) - XDG Desktop Portal integration
lamco-pipewire (0.1.4) - PipeWire screen capture
lamco-video (0.1.2) - Video frame processing
lamco-rdp-input (0.1.1) - Input event translation

Bundled Crates (Local Path Dependencies)

These crates are bundled locally (not referenced from crates.io):

lamco-clipboard-core (0.5.0) - Clipboard protocol core (bundled-crates/)
lamco-rdp-clipboard (0.2.2) - IronRDP clipboard backend (bundled-crates/)

Why bundled? These crates implement CliprdrBackend trait from ironrdp-cliprdr. Since we use a forked version of IronRDP (with pending upstream features), these crates must compile against the same fork version to avoid trait conflicts. They’re published to crates.io for other users but bundled here for version compatibility.

Forked Dependencies

IronRDP Fork: https://github.com/lamco-admin/IronRDP (master branch)

Currently includes features awaiting upstream merge:

MS-RDPEGFX Graphics Pipeline Extension (PR #1057 - pending)
Clipboard file transfer methods (PRs #1063-1066 - MERGED ✅)

All IronRDP crates are patched via [patch.crates-io] in Cargo.toml for consistency.

Session Persistence & Unattended Operation

lamco-rdp-server implements multi-strategy session management enabling unattended operation across different Linux environments.

Available Strategies

The server automatically selects the best strategy based on detected compositor and deployment context:

Mutter Direct API (GNOME-specific)

Zero permission dialogs (even first connection)
Uses org.gnome.Mutter.ScreenCast and RemoteDesktop D-Bus APIs directly
GNOME 42+ required
Provides best user experience on GNOME desktops

wlr-direct (wlroots native)

Zero permission dialogs
Uses native Wayland protocols (zwp_virtual_keyboard_v1, zwlr_virtual_pointer_v1)
Build with --features wayland
Works on Sway, Hyprland, River, labwc
Sub-millisecond input latency

Portal + libei/EIS (Flatpak-compatible wlroots)

One-time permission dialog, then automatic
Uses Portal RemoteDesktop + EIS protocol bridge
Build with --features libei
Works in Flatpak sandbox
Compatible with wlroots compositors supporting ConnectToEIS

Portal + Restore Tokens (Universal)

One-time permission dialog, automatic reconnect
Works on all desktops (GNOME, KDE, wlroots)
Portal v4+ required for token support
Credentials stored securely (Secret Service, TPM 2.0, or encrypted file)

Basic Portal (Fallback)

Permission dialog on every restart
Works on all Portal-supported desktops
Graceful degradation when persistence unavailable

Note: GNOME’s portal backend currently rejects session persistence for RemoteDesktop sessions (deliberate policy), so even with Portal v4+ you’ll see a dialog on each restart. Mutter Direct API strategy bypasses this limitation.

See docs/architecture/SESSION-PERSISTENCE-ARCHITECTURE.md for complete technical details.

Service Registry

The Service Registry system translates compositor capabilities into 18 advertised services with 4-level guarantees (Guaranteed, BestEffort, Degraded, Unavailable).

Services include:

Display: DamageTracking, DmaBufZeroCopy, ExplicitSync, FractionalScaling, MetadataCursor, MultiMonitor, WindowCapture, HdrColorSpace
I/O: Clipboard, RemoteInput, VideoCapture
Session Persistence: SessionPersistence, DirectCompositorAPI, CredentialStorage, UnattendedAccess, WlrScreencopy, WlrDirectInput, LibeiInput

The registry enables runtime decisions (codec selection, FPS tuning, cursor mode) based on actual compositor capabilities.

See docs/SERVICE-REGISTRY-TECHNICAL.md for implementation details.

Building

Prerequisites

Rust 1.77 or later
OpenSSL development libraries
PipeWire development libraries
For H.264: nasm (3x speedup for OpenH264)

Build Instructions

# Default build (software H.264 encoding)
cargo build --release

# With VA-API hardware encoding (Intel/AMD)
cargo build --release --features vaapi

# With NVENC hardware encoding (NVIDIA)
cargo build --release --features nvenc

# With all hardware backends
cargo build --release --features hardware-encoding

Hardware Encoding Requirements

VA-API (Intel/AMD):

libva-dev >= 1.20.0
Intel iHD driver (modern Intel) or i965 (older Intel)
AMD radeonsi driver

NVENC (NVIDIA):

NVIDIA driver with libnvidia-encode.so
CUDA toolkit
NVENC-capable GPU (GTX 6xx+, any RTX)

Flatpak vs Native Builds

Different deployment methods support different features:

Flatpak Build

cargo --offline build --release --no-default-features --features "h264,libei"

Enabled Features:

✅ h264 - OpenH264 video encoding (essential)
✅ libei - Portal + EIS/libei input (wlroots support in Flatpak)

Disabled Features:

❌ pam-auth - Not sandboxable in Flatpak
❌ vaapi - Limited in sandbox environment
❌ wayland - wlr-direct protocols blocked by sandbox
❌ nvenc - CUDA not available in Flatpak

Strategy Availability:

Portal + Token (universal)
libei (wlroots via Portal + EIS)

Native Build

cargo build --release  # Uses default features
# Or with hardware encoding:
cargo build --release --features "hardware-encoding"

Enabled Features:

✅ pam-auth - PAM authentication
✅ h264 - OpenH264 encoding
✅ vaapi - Intel/AMD GPU encoding (optional)
✅ nvenc - NVIDIA GPU encoding (optional)
✅ wayland - wlr-direct protocols (build with --features wayland)
✅ libei - Portal + EIS (build with --features libei)

Strategy Availability:

All 5 strategies (Mutter Direct, wlr-direct, libei, Portal + Token, Basic Portal)

Summary: Flatpak prioritizes portability and sandboxing. Native builds support all features including hardware encoding and zero-dialog strategies.

Quick Start

Prerequisites for Running

TLS Certificates in certs/ directory:

# Generate test certificates
./scripts/generate-certs.sh
# Or copy existing test certs
cp certs/test-cert.pem certs/cert.pem
cp certs/test-key.pem certs/key.pem

D-Bus Session (required for portal access via SSH):

export DBUS_SESSION_BUS_ADDRESS="unix:path=/run/user/$(id -u)/bus"

PipeWire running for screen capture

Running

# Run with local configuration
./target/release/lamco-rdp-server -c config.toml

# With verbose logging
./target/release/lamco-rdp-server -c config.toml -vv

# With log file
./target/release/lamco-rdp-server -c config.toml -vv --log-file server.log

Connecting

Use any RDP client:

Windows: mstsc.exe (Remote Desktop Connection)
Linux: xfreerdp, remmina
macOS: Microsoft Remote Desktop

# FreeRDP example
xfreerdp /v:hostname:3389 /u:username /p:password /gfx:AVC444

Configuration

Configuration can be provided via:

TOML file (default: /etc/wrd-server/config.toml)
Environment variables (prefixed with WRD_)
Command-line arguments (highest priority)

Command-Line Options

Options:
-c, --config <CONFIG>          Configuration file path [default: /etc/wrd-server/config.toml]
-l, --listen <LISTEN>          Listen address [env: WRD_LISTEN_ADDR=]
-p, --port <PORT>              Listen port [env: WRD_PORT=] [default: 3389]
-v, --verbose...               Verbose logging (can be specified multiple times)
--log-format <LOG_FORMAT>  Log format (json|pretty|compact) [default: pretty]
--log-file <PATH>          Log to file
-h, --help                     Print help
-V, --version                  Print version

See config.toml for a complete example configuration.

Project Structure

lamco-rdp-server/
├── src/
│   ├── lib.rs          # Library root, module exports
│   ├── main.rs         # Binary entry point
│   ├── config/         # Configuration management
│   ├── server/         # Main server implementation
│   ├── rdp/            # RDP channel management
│   ├── egfx/           # EGFX video pipeline
│   │   ├── encoder.rs        # OpenH264 AVC420 encoder
│   │   ├── avc444_encoder.rs # Dual-stream AVC444 encoder
│   │   ├── color_space.rs    # VUI parameters, color presets
│   │   ├── color_convert.rs  # BGRA→YUV444 with SIMD
│   │   ├── yuv444_packing.rs # AVC444 dual-stream packing
│   │   └── hardware/         # Hardware encoders
│   │       ├── vaapi/        # VA-API (Intel/AMD)
│   │       └── nvenc/        # NVENC (NVIDIA)
│   ├── clipboard/      # Clipboard orchestration
│   ├── damage/         # Damage region detection
│   ├── multimon/       # Multi-monitor support
│   ├── security/       # Authentication and TLS
│   ├── protocol/       # Protocol utilities
│   └── utils/          # Common utilities
├── docs/               # Documentation
│   ├── architecture/   # Architecture docs
│   ├── specs/          # Specifications
│   └── guides/         # User guides
├── certs/              # TLS certificates
├── scripts/            # Build and setup scripts
└── benches/            # Performance benchmarks

Documentation

Architecture: docs/architecture/COMPREHENSIVE-ARCHITECTURE-AUDIT-2025-12-27.md
Color Infrastructure: docs/architecture/NVENC-AND-COLOR-INFRASTRUCTURE.md
IronRDP Integration: docs/ironrdp/IRONRDP-INTEGRATION-GUIDE.md
Testing Setup: docs/guides/TESTING-ENVIRONMENT-RECOMMENDATIONS.md

Development

Running Tests

cargo test
cargo test -- --nocapture  # With output

Benchmarks

cargo bench --bench video_encoding
cargo bench --bench color_conversion
cargo bench --bench damage_detection

Code Quality

cargo fmt
cargo clippy

License

lamco-rdp-server is licensed under the Business Source License 1.1 (BSL).

Free Use

You may use lamco-rdp-server for free if you meet ALL of the following conditions:

You are a non-profit organization, OR
You are a for-profit organization with:

3 or fewer employees, AND
Less than $1,000,000 USD in annual revenue, AND

Your use does not include creating a competitive or derivative RDP server product or VDI solution

Commercial License Required

Larger organizations or commercial deployments require a commercial license:

Annual License: $49.99/year per server
Perpetual License: $99.00 one-time per server

Contact: office@lamco.io

Future Open Source

This software will automatically convert to the Apache License 2.0 three years after each version’s release (first release: December 2025 → converts December 31, 2028).

See the LICENSE file for complete terms.

Contributing

Contributions are welcome! Please open an issue before starting significant work.

See CONTRIBUTING.md for guidelines.

Acknowledgments

Built with:

IronRDP - RDP protocol implementation
tokio - Async runtime
OpenH264 - H.264 codec
PipeWire - Screen capture
ashpd - XDG Portal bindings

lamco-rdp-server

Overview

Features

Core Features (Implemented)

lamco-rdp-server

Overview

Features

Core Features (Implemented)

Premium Features (Optional)

wlroots Compositor Support (NEW - 2026-01-16)

Architecture

Dependency Architecture

Published Lamco Crates (crates.io)

Bundled Crates (Local Path Dependencies)

Forked Dependencies

Session Persistence & Unattended Operation

Available Strategies

Service Registry

Building

Prerequisites

Build Instructions

Hardware Encoding Requirements

Flatpak vs Native Builds

Flatpak Build

Native Build

Quick Start

Prerequisites for Running

Running

Connecting

Configuration

Command-Line Options

Project Structure

Documentation

Development

Running Tests

Benchmarks

Code Quality

License

Free Use

Commercial License Required

Future Open Source

Contributing

Acknowledgments

Similar Posts