﻿GuruDesk - Windows client
Commit 9afa81f
Built 2026-08-06 09:23 local

CONNECTION DEFAULTS ARE BAKED IN
  homebase: 41.218.79.80:4719
  spki:     b3f18a0637163fde88bbb02049f8ff1f296c3acfc1be61bc72392db5141c9d3c

  This exe connects with no settings.json and no environment variables. To point
  it somewhere else, either set GD_HOMEBASE / GD_HOMEBASE_SPKI, or edit
  %APPDATA%\GuruDesk\settings.json. Both override the baked values.

  A mismatched SPKI means the client refuses to connect. That is deliberate: the
  pin is the entire trust anchor, there is no CA behind it.

ENROLMENT IS SEPARATE
  Config tells the client where the server is; it does not enrol the device.
  A machine that has never enrolled will reach homebase and still not be able to
  host or connect.

RUN
  gurudesk.exe

  With diagnostics (host side, for latency work):
    set RUST_LOG=gd_client_core=debug
    gurudesk.exe
