CydandClaude Opus 4.8
b9d8027cf6
Make the Console<->Launcher system source-built and modern now that the console is under our control and the WinXP-era pods are gone. Contract extraction (Contract/Tesla.Contract.csproj): - One multi-targeted (net48;net8.0-windows) source project for the RPC contract, replacing the vendored TeslaConsoleLaunchLib.dll and the hand-synced Tesla.Net replica in Launcher/LaunchModels_Shared.cs. Emits assembly TeslaConsoleLaunchLib. SecureConfig extraction (SecureConfig/Tesla.SecureConfig.csproj): - net48 source of the first-boot provisioning protocol (UDP beacons, OFB crypto, RSA key exchange), replacing the vendored TeslaSecureConfiguration.dll. Remove BinaryFormatter from the wire (RCE sink + the reason net6 was pinned): - Console<->Launcher RPC is now length-prefixed System.Text.Json frames (Contract/PodRpcProtocol.cs) over the unchanged OFB transport; dispatch by method name. Deleted the SerializationBinder / MethodInfoProxy machinery. - Console-local BinaryFormatter (Site config, mission replays) intentionally retained: local net48 file I/O, not the network surface. Runtime modernization: - Launcher Service + Agent: net6 -> net8, win-x86 -> win-x64 (all pods are 64-bit Win10). Kept the SHA1-default PBKDF2 (Console key-derivation compat) with SYSLIB0041 suppressed and documented. Tests: differential suite now 73 green. Added SecureConfigCompatTests (OFB ciphertext byte-identical to the vendored DLL) and PodRpcProtocolTests (JSON round-trip of every request/response shape); removed the now-obsolete BinaryFormatter byte-identity guard. Build hygiene: per-project obj dirs (Launcher/Directory.Build.props) fix a NuGet restore collision between the two Launcher projects sharing one folder. NOT runtime-verified against a live pod. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
24 lines
1.2 KiB
XML
24 lines
1.2 KiB
XML
<Project>
|
|
|
|
<!-- TeslaLauncherService.csproj and TeslaLauncherAgent.csproj share this one
|
|
directory, so by default they also share obj\project.assets.json. NuGet
|
|
restore writes that single file per project, so whichever restores last
|
|
wins and the other compiles against the wrong package set (e.g. the
|
|
Service losing Microsoft.Extensions.Hosting). Give each project its own
|
|
intermediate directory so their restore outputs no longer collide.
|
|
(bin\ is safe to share — the two assemblies have distinct names.) -->
|
|
<PropertyGroup>
|
|
<BaseIntermediateOutputPath>obj\$(MSBuildProjectName)\</BaseIntermediateOutputPath>
|
|
</PropertyGroup>
|
|
|
|
<!-- With per-project obj subdirs, each project would otherwise glob the OTHER
|
|
project's generated sources (AssemblyInfo.cs, etc.) out of the sibling
|
|
obj\ subtree, causing duplicate-attribute errors. The SDK only excludes a
|
|
project's own BaseIntermediateOutputPath by default, so exclude the whole
|
|
obj\ and bin\ trees here. The SDK appends its own defaults to this. -->
|
|
<PropertyGroup>
|
|
<DefaultItemExcludes>$(DefaultItemExcludes);$(MSBuildProjectDirectory)\obj\**;$(MSBuildProjectDirectory)\bin\**</DefaultItemExcludes>
|
|
</PropertyGroup>
|
|
|
|
</Project>
|