CydandClaude Opus 4.8
1e2ec12f11
Converts the Launcher Service + Agent from net8/win-x64 self-contained to net48 framework-dependent, and makes Tesla.Contract net48-only (drops multi-targeting). Both consumers (Console + Launcher) are now a single TFM. Code changes for net48 (the only net8/netstandard2.1 APIs in use): - RandomNumberGenerator.Fill -> RandomNumberGenerator.Create().GetBytes (3x) - TcpListener.AcceptTcpClientAsync(ct) -> AcceptTcpClientAsync() + stop-on-cancel - byte[].AsSpan().SequenceEqual -> Linq SequenceEqual (no System.Memory) (2x) - PipeStream.Write(byte[]) / WriteAsync(byte[],ct) -> explicit (buf,0,len[,ct]) - Math.Clamp -> Math.Max/Min The generic host (Microsoft.Extensions.Hosting 8.x + UseWindowsService) runs on net48 unchanged. build.bat/install.bat updated for the folder-of-DLLs deploy; solution platform reverted x64 -> AnyCPU. RESULT — package size: ~3.7 MB on disk / 1.58 MB zipped, vs ~213 MB / 91 MB for the net8 self-contained build (~50-58x smaller). net48 ships in Win10/11 so no runtime prerequisite. 73 tests green; NOT re-validated on a live pod. Spike branch for evaluation — do not merge without a pod re-test. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
TeslaLauncher
.NET 8 (win-x64, self-contained) rewrite of the original Elsewhen Studios LLC software (Windows 2000 / .NET Framework 2.0).
Architecture
TeslaLauncher has three components that work together:
TeslaLauncherService (Windows Service, Session 0)
- Runs at boot before any user logs in
- Listens on TCP 53290 for OFB-encrypted framed-JSON RPC from TeslaConsole
- Forwards commands to the Agent via Named Pipe (
TeslaLauncherIPC) - Handles first-boot network configuration (SecureConfig)
- Handles game file transfers from the Console (InstallProduct)
TeslaLauncherAgent (WinForms tray app, user session)
- Runs in the logged-in user's desktop session
- Executes commands that require desktop access: launching/killing apps, volume control
- Manages
LaunchApps.xml(installed games registry) - On first boot, displays SecureConfig Request ID and Passphrase
SecureConfig (first-boot protocol)
- Assigns a temporary IP and broadcasts a UDP beacon so the Console can discover the pod
- Operator reads the Passphrase off the pod screen and enters it into the Console
- Console sends AES-encrypted network configuration (IP, mask, gateway, DNS, hostname)
- TCP handshake establishes an OFB-encrypted session with RSA key exchange
- Session key is saved for all subsequent Console connections
Communication Flow
TeslaConsole ──TCP 53290 (OFB + framed JSON)──> TeslaLauncherService
│
Named Pipe (JSON)
│
v
TeslaLauncherAgent
Files
| File | Description |
|---|---|
TeslaLauncherService.cs |
Windows Service implementation |
TeslaLauncherService.csproj |
Service project (net8.0-windows, x64, self-contained) |
TeslaLauncherAgent.cs |
Userspace Agent implementation |
TeslaLauncherAgent.csproj |
Agent project (WinForms, net8.0-windows, x64) |
LaunchModels_Shared.cs |
Service↔Agent IPC types (Tesla.Launcher.Shared). Wire types (Tesla.Net) now come from ../Contract/Tesla.Contract.csproj |
SecureConfig.cs |
First-boot secure configuration protocol |
build.bat |
Builds both components |
install.bat |
Installs on a cockpit PC (run as Administrator) |
Building
Requirements:
- .NET 8 SDK
- Internet access for NuGet restore (first build only)
build.bat :: build both components + assemble the package
build.bat /service :: build Service only
build.bat /agent :: build Agent only
Output goes to TeslaLauncher\ with Service\ and Agent\ subdirectories plus
install.bat. The projects are published in place (self-contained, single-file,
win-x64) — they reference ../Contract, so they cannot be staged into a temp
folder. No .NET runtime is required on the target pod.
Installation
- Copy the
TeslaLauncher\folder to each cockpit PC - Run
TeslaLauncher\install.batas Administrator
The installer:
- Registers the Service (delayed auto-start)
- Configures the Agent for auto-login startup
- Installs OpenAL and DirectX runtimes
- Enables SMB1 file sharing
- Creates
C:\Gameswith appropriate permissions - Resets network adapters to DHCP for SecureConfig
First Boot
- Cockpit boots with DHCP (unconfigured state)
- Service runs SecureConfig: broadcasts beacon, displays codes on screen
- Console operator sees the pod's Request ID and enters the Passphrase
- Console sends encrypted network configuration
- Pod applies the configuration and is ready for normal operation
Normal Operation
The Console connects to each configured pod on TCP 53290 and can:
- Install/uninstall simulation games
- Launch/kill applications
- Get/set volume level
- Query pod status (FullUpdate)
- Shutdown or reboot the pod
Key Paths
| Path | Purpose |
|---|---|
C:\ProgramData\TeslaLauncher\TeslaKeyStore.key |
Session key (32 bytes) |
C:\ProgramData\TeslaLauncher\LaunchApps.xml |
Installed games registry |
C:\ProgramData\TeslaLauncher\configuring.json |
Transient: SecureConfig codes for Agent display |
C:\Games\ |
Game installation directory |
Wire Protocol
The Console talks to the Service with length-prefixed System.Text.Json frames
over the OFB-encrypted TCP stream (dispatch by method name) — see
../Contract/PodRpcProtocol.cs, shared by both ends. This replaced the original
BinaryFormatter + serialized-MethodBase scheme. The Tesla.Net wire types now
live in ../Contract/Tesla.Contract.csproj, the single source of truth shared with
the Console.
The Service-to-Agent IPC uses length-prefixed JSON over a Named Pipe, with flat types that avoid the nested struct layout of the wire format.